At 13:20 UTC on 17 July 2014, a Boeing 777 in Malaysia Airlines colours was cruising at 33,000 feet over the wheat fields of the Donetsk region, a little under three hours out of Amsterdam. The cockpit voice recorder was running. The crew had no warning of any kind. Then the recording simply stops.
A surface-to-air missile had detonated just above and to the left of the cockpit. Flight MH17 broke apart in the air, and wreckage came down across a wide stretch of countryside near the village of Hrabove. All 298 people on board were killed: 283 passengers and 15 crew, about two-thirds of them Dutch, travelling to Kuala Lumpur for holidays, for work, for family.
It took fifteen months for the Dutch Safety Board to prove what had destroyed the aircraft, four more years for an international criminal team to trace the launcher to a Russian army brigade, and more than a decade for courts and the United Nations’ aviation body to assign responsibility. This is what the investigators found about the MH17 Buk missile, and what the disaster changed for every airliner that flies near a war.
Informazioni rapide
Data: 17 July 2014, contact lost at 13:20 UTC (16:20 local time)
Aeromobili: Boeing 777-200ER, registration 9M-MRD, Malaysia Airlines
Itinerario: Amsterdam Schiphol to Kuala Lumpur, at flight level 330 (33,000 ft)
Ucciso: 298: 283 passengers and 15 crew. There were no survivors
Arma: Buk surface-to-air missile system, 9M38-series missile with a 9N314M warhead (Dutch Safety Board, 13 October 2015)
Launcher: A Buk TELAR of the Russian 53rd Anti-Aircraft Missile Brigade from Kursk (Joint Investigation Team, 24 May 2018)
Spazio aereo: 61 operators from 32 countries routed flights over eastern Ukraine between 14 and 17 July; 160 airliners crossed it on the day of the crash before it was closed
Verdicts: Three men convicted of murder in absentia by The Hague District Court (17 November 2022); Russia held responsible by the ICAO Council (12 May 2025)
A normal flight on a normal airway
Nothing about the route was unusual. MH17, also sold as KLM flight 4103, departed Schiphol at 12:31 local time. Its flight plan took it across Ukraine along a busy east-west airway used by carriers from all over Europe and Asia.
Below it, eastern Ukraine had been at war since the spring. Russian-backed separatists held much of the Donetsk and Luhansk regions, and Ukrainian military aircraft had been shot down over the area in the preceding weeks. Kyiv’s response, on military grounds, had been to restrict the lower airspace. Airliners at cruising altitude were still permitted to fly over the fighting, and MH17 was at flight level 330, just above the restricted band.
It was far from alone. The Dutch Safety Board later counted 61 operators from 32 countries routing flights through that airspace between 14 and 17 July, and 160 airliners crossing it on 17 July alone before it was closed. MH17 was one aircraft in a steady stream.
The Dutch Safety Board’s own English-language presentation of its final report, including the reconstruction of the forward fuselage. It contains no images of victims.
What the wreckage proved
The Dutch Safety Board, the Onderzoeksraad voor Veiligheid, led the technical investigation on Ukraine’s behalf. Its investigators could not work freely at the crash site, which lay in separatist-held territory, so the debris that could be recovered was brought to the Netherlands. At Gilze-Rijen air base, investigators rebuilt the forward fuselage around a frame so that every hole could be measured.
The damage told its own story. The cockpit and the front of the cabin were peppered with hundreds of high-energy impacts, the pattern of a warhead bursting outside the aircraft, above and to the left of the flight deck. The three crew members in the cockpit were killed instantly. The forward section separated, and the rest of the airliner broke up in the air.
Then came the fragments themselves. Among the metal fragments the investigators recovered were pieces shaped like a bow tie. That shape is not an accident: it is characteristic of the preformed fragments packed into a particular type of Buk warhead, and the Board matched the debris to it. Its conclusion was precise. The aircraft had been destroyed by a 9N314M warhead carried on a 9M38-series missile, fired by a Buk surface-to-air missile system.
The cockpit voice recorder added a final, cold piece of evidence. In the final moment of recording, a sound peak registered on the four cockpit microphones at slightly different moments, and the timing differences let investigators calculate the direction from which the blast arrived. It came from above and to the left.

Why a Buk can reach an airliner at 33,000 feet
The Buk, known to NATO as the SA-11 Gadfly in its original form, is a mobile, medium-range air-defence system designed in the Soviet Union to shoot down aircraft. Its key component is the TELAR, short for transporter, erector, launcher and radar: a tracked vehicle that carries ready-to-fire missiles and its own engagement radar on a single chassis.
That matters for MH17. Because the radar travels with the launcher, a single TELAR can be driven to a field, switched on and fire, without the wider network of search radars and command vehicles that a full battery normally brings. That is how the investigators later concluded the MH17 Buk missile was launched: by one vehicle, brought in and taken out again. A large airliner flying straight and level at 33,000 feet sits comfortably within the system’s reach.
The 9N314M warhead does not need a direct hit. A proximity fuze detonates it close to the target, outside the aircraft, and the blast drives thousands of preformed metal fragments outward. The Board’s chairman spelled out the effect when he presented the final report.
The Board placed the launch within a 320-square-kilometre area of eastern Ukraine. It did not say who fired the missile; that was never its job. Attributing blame was left to the criminal investigators.
The airspace that should have been closed
The Board’s second report was, in some ways, the more uncomfortable one. It asked why a civil airliner was flying over an armed conflict in which military aircraft were being shot down at all.
Its answer was that Ukraine had sufficient reason to close the airspace over the conflict area as a precaution, and did not. The authorities restricted only the lower altitudes, a measure aimed at military flying. Russia, managing the adjacent airspace, issued its own notices. Airlines, for their part, read the same notices, saw that the restriction ended just below their cruising levels, and kept flying. In the Board’s view the whole system of responsibility for flying over conflict zones was inadequate.
This is the part of the MH17 story that matters most to anyone who flies. A weapon able to reach cruising altitude had been brought into a conflict where aircraft were already being shot down, and the risk to the airliners overhead was assessed by nobody in particular. Ukraine closed the airspace over the east within hours of the crash.
Following the launcher back to Kursk
The criminal investigation was run by a Joint Investigation Team led by the Netherlands with Australia, Belgium, Malaysia and Ukraine. It worked from intercepted telephone calls, witness statements, telecom data and an enormous volume of photographs and video posted online in July 2014.
In September 2016 the JIT presented its first conclusions. The missile had been fired from a field near Pervomaiskyi, south of the town of Snizhne, in territory held by the separatists. The Buk had been brought in from Russia on the morning of 17 July and taken back across the border afterwards, with one missile fewer than it arrived with.
The Joint Investigation Team’s animation of the Buk’s transport route from the Russian border to the launch field, published by the Dutch Public Prosecution Service (Openbaar Ministerie).
On 24 May 2018 the team went further. Investigators had catalogued the launcher’s unique features in images from 17 and 18 July 2014, building what they called a fingerprint of the vehicle, and compared it with images of a Buk TELAR on the move on 23, 24 and 25 June 2014. It matched.
The 53rd Brigade is a unit of the Russian armed forces. Moscow has consistently denied any involvement. Almaz-Antey, the Buk’s Russian manufacturer, argued at the time of the Safety Board report for a different launch site and an older missile model. The investigators’ evidence pointed elsewhere.
The verdict, and the state
On 17 November 2022 The Hague District Court convicted three men in absentia of murdering the 298 people on board and of intentionally causing the aircraft to crash: Igor Girkin and Sergey Dubinsky, both former Russian intelligence officers, and Leonid Kharchenko, a Ukrainian separatist commander. All three were sentenced to life imprisonment. A fourth defendant, Russian national Oleg Pulatov, was acquitted. The court also found that Russia had overall control of the separatist forces at the time.
None of the three has been handed over. In early 2023 the JIT said it had found strong indications that the decision to supply the Buk had been taken at the highest level of the Russian state, but that the evidence was not complete enough to prosecute anyone further, and the investigation was suspended.
The question of state responsibility went to the international institutions instead. On 12 May 2025 the Council of the International Civil Aviation Organization, acting on a complaint the Netherlands and Australia filed in 2022, found the Russian Federation responsible for the downing of MH17 and in breach of the Chicago Convention, the founding treaty of international civil aviation. In July 2025 the European Court of Human Rights reached the same conclusion about Russia’s responsibility.

What changed for airliners over conflict zones
The most lasting legacy of MH17 is not a verdict. It is the machinery now built around a question that, in July 2014, nobody owned: who decides whether it is safe to fly over a war?
The Dutch Safety Board’s recommendations aimed squarely at that gap. States, ICAO, IATA and airlines should share far more information about conflict areas and threats to civil aviation. Risk assessments should pay attention to how a conflict is developing, including increased military activity and aircraft being shot at. States fighting a war over their own territory should get more support and incentives to protect or close their airspace. Airlines should account publicly for the routes they choose.
In Europe, the response took concrete form. Following MH17, the EU developed the EU Conflict Zone Alerting System, active since early 2016, which brings together intelligence from member states in a common risk assessment chaired by the European Commission. Its public output is the Conflict Zone Information Bulletin, or CZIB, issued by the European Union Aviation Safety Agency: a formal advisory telling airlines which airspace to avoid and at what altitudes. When EASA warned operators off part of Saudi Arabia’s Jeddah flight information region last month, as Afterburner reported, it was that system at work.
Airlines changed too. Many now run their own security departments that assess routes independently of what the overflown state publishes, and avoid airspace that remains technically open. Pilots have pushed to go further still: their unions have demanded a formal right to refuse routes over conflict zones, a campaign covered in Final and Non-Negotiable.
The New York Times’ short explainer on how the Buk system detects, tracks and engages a target, published after the disaster.
The lesson of 17 July
MH17 was not the first airliner destroyed by a missile, and it was not the last. What set it apart was the investigation. Every major question, from which weapon to which launcher to which state, was answered with physical evidence that has stood up in a criminal court and before two international bodies.
Its lesson is uncomfortable in its simplicity. The MH17 Buk missile did not find a careless crew or a faulty aircraft. It found a fully legal flight on an open airway, flown exactly as planned, over a war that everyone could see on the evening news. The airspace was open because nobody had decided it should be closed.
Since 2014, closing it has become somebody’s job.
Sources: Dutch Safety Board (Onderzoeksraad voor Veiligheid), press release and final report Crash of Malaysia Airlines Flight MH17, 13 October 2015; Dutch Public Prosecution Service, speakers’ text of the JIT MH17 press meeting, 24 May 2018; Government of the Netherlands, ICAO Council: Russian Federation responsible for downing of flight MH17, 12 May 2025; EASA, Information on Conflict Zones; Wikipedia, Malaysia Airlines Flight 17; RFE/RL, 13 October 2015; DutchNews.nl, 13 October 2015; The Interpreter, 13 October 2015; Al Jazeera, 17 November 2022; Ukrinform and The Times of Israel, 17 November 2022; Stars and Stripes, 13 May 2025; CBC News and Council of Europe (PACE), 9 July 2025; Jalopnik and GlobalSecurity.org, 17 July 2014.




0 Comments