Malaysia Airlines Flight MH370
Malaysia Airlines Flight 370 left Kuala Lumpur for Beijing at 00:42 local time on 8 March 2014 with 227 passengers and 12 crew[1]. At 01:19 the captain acknowledged a handover to Ho Chi Minh control with "Good night, Malaysian three seven zero." Two minutes later, as the aircraft crossed waypoint IGARI at the edge of Malaysian airspace, its transponder stopped, and it never contacted Vietnamese control[1]. Malaysian military radar showed it turning back to the south-west, crossing the peninsula near Penang and flying north-west up the Strait of Malacca until 02:22, when it left radar coverage[1].
It did not disappear entirely. Its satellite communications unit logged back on to an Inmarsat satellite at 02:25 and answered hourly handshakes until a final, incomplete log-on request at 08:19, by which time the aircraft would have exhausted its fuel[2]. Each exchange recorded a timing offset, which gives the aircraft's distance from the satellite, and a frequency offset, which gives its speed along the line of sight. Together they show that the aircraft flew for six hours, almost certainly south, and ended somewhere along an arc in the southern Indian Ocean about 1,800 km west of Perth[2][3]. No distress call, no cockpit voice recorder, no reason.
Australia led a seabed search of 120,000 km² along the arc from 2014 to January 2017 and found nothing[4]. A flaperon washed up on Réunion in July 2015, a right outboard flap on Pemba Island off Tanzania in June 2016, and some thirty other pieces on African shores; three carry part numbers that identify the aircraft[5]. Drift modelling of those finds, and a review of the handshake analysis, pointed to an unsearched stretch of the arc near 35°S, which Ocean Infinity searched in 2018 without result[6][4]. The Malaysian safety investigation reported in 2018 that it could not determine the cause, that the turn-back was flown manually, and that interference by a third party could not be excluded[1]. In 2025 Malaysia contracted Ocean Infinity again, on the same no-find, no-fee terms, for a 15,000 km² target; the search ran for a few days in March 2025 and from 31 December 2025 to 23 January 2026, covered about half the target, and found nothing[7][8]. Of the 4 questions on this site, 0 are answered. The most likely answer to “Where is the wreckage?”, not yet confirmed: close to the seventh arc (within about 25 nautical miles) in an unsearched stretch north of about 33°S.
Key questionsset by the editors
What is known
The first hour is documented by air traffic control recordings, the aircraft's ACARS reports (the last at 01:07), and civil and military radar[1]. The turn-back began within two minutes of the transponder stopping and took the aircraft through a sequence of turns and a route along airway waypoints that the investigators judged was flown by hand or with the autopilot deliberately directed, not by a system failure[1]. The investigation found no fault in the aircraft or its maintenance, nothing in the cargo, nothing in the passengers' backgrounds, and no evidence that resolved the crew's state of mind; the captain's home flight simulator held a deleted route into the southern Indian Ocean, which the report noted without drawing a conclusion[1].
The six hours after radar are documented only by the Inmarsat log. The satellite data unit's handshakes at 02:25, 03:41, 04:41, 05:41, 06:41, 08:11 and 08:19 each carry a burst timing offset (BTO) and a burst frequency offset (BFO). The BTO fixes a ring of positions on the Earth for each handshake; the BFO, corrected for the satellite's own motion, constrains the aircraft's velocity component toward the satellite and distinguishes a northern from a southern route[2]. Inmarsat's engineers validated the method against other aircraft flying known routes that night[2]. Malaysia released the log, 47 pages, on 27 May 2014[9]. The last two signals, 08:11 and 08:19, are read as the aircraft running out of fuel on one engine and then the other, the auxiliary power unit starting and the SATCOM rebooting, which places the end of flight within a few tens of kilometres of the seventh arc[4][3].
The debris is the physical record. The flaperon found on Réunion on 29 July 2015 was identified by French investigators from its internal serial plates; the outboard flap from Pemba carried a part number and Malaysia Airlines' stencilling; a third piece was likewise matched[5]. Examination of the flap and flaperon found that the flaps were not extended at the time of separation, which argues against a controlled ditching with flaps down[5]. Marine growth on the flaperon and the timing of the finds, compared with drifting buoys and with replica flaperons tracked by CSIRO, were used to back-calculate where the pieces entered the water[6].
Timeline
The search
The surface search in March and April 2014 began in the South China Sea, moved to the Strait of Malacca when the radar track was understood, and then, once the Inmarsat analysis was accepted, to the southern Indian Ocean, where it found nothing attributable to the aircraft[1]. The underwater search was led by the Australian Transport Safety Bureau on Malaysia's behalf with Chinese participation. The search zone was set by a Bayesian analysis of the satellite data by Australia's Defence Science and Technology Group, which produced a probability distribution along the arc and a 120,000 km² priority area centred near 38°S[3]. Towed and autonomous sonar surveyed it from October 2014 until the search was suspended on 17 January 2017; the area was cleared to a high standard of confidence, and the ATSB's final report concluded that the aircraft was not in it[4].
Two lines of evidence then moved the estimate north. CSIRO's drift modelling of the debris finds, using actual flaperon replicas at sea, found that an origin near 35°S was most consistent with the arrival dates and with the absence of debris on Australian shores[6]. A review of the final handshakes and of the aircraft's likely flight dynamics at fuel exhaustion suggested the aircraft came down close to the arc and that the unsearched stretch between about 32.5°S and 36°S, some 25,000 km², was the most likely remaining area[4]. Ocean Infinity's vessel Seabed Constructor searched that stretch and more, about 112,000 km², with a fleet of autonomous vehicles from January to June 2018, on no-find, no-fee terms, and found nothing[1][7].
Between 2018 and 2024 independent analysts proposed narrower targets from refinements of the satellite analysis, from drift studies, and from amateur radio (WSPR) propagation records whose use for aircraft tracking is disputed. Ocean Infinity proposed a new search in 2024; the Malaysian cabinet approved it in December 2024 and agreed terms in March 2025: $70 million payable only on finding the wreckage, for a 15,000 km² area[7]. The vessel worked the site from 25 to 28 March 2025 before withdrawing, and again from 31 December 2025 to 23 January 2026, surveying 7,571 km² before weather and a reassignment ended the campaign. In March 2026 Malaysia's Air Accident Investigation Bureau stated that the search "has not yielded any findings that confirm the location of the aircraft wreckage" and gave no date for resumption; the contract runs to June 2026[8].
The explanations
Deliberate diversion by someone on the flight deck is the reading most analysts hold. It accounts for the timing of the transponder loss at the handover between control centres, the hand-flown turn, the route along the Malaysia–Thailand border that avoided both countries' attention, the silence of every communication system except the one nobody thought to turn off, and the long southern leg[1]. The Malaysian investigation did not name a perpetrator and said it could not exclude third-party interference; it found nothing in the crew's records that showed intent, and the captain's simulator route is suggestive and no more[1]. The reading divides on the end of flight: an unpiloted descent at fuel exhaustion, which the final BFO values and the flap evidence support, or a controlled glide, which would put the wreckage farther from the arc than any search has looked[4][5].
Accident readings propose a fire, depressurisation or electrical failure that incapacitated the crew after a turn toward a diversion airport, with the aircraft flying on autopilot until the fuel ran out. Against them: the turn-back was hand-flown through several headings, the loss of the transponder and ACARS preceded any sign of trouble, and no system failure explains why the SATCOM came back after an hour[1]. Hijacking by a passenger is not excluded by evidence but is unsupported by any claim, background or trace[1]. Readings that place the aircraft elsewhere than the southern arc, including a northern route, Diego Garcia, or a shoot-down over the South China Sea, are contradicted by the Inmarsat data, the debris and the drift analysis[2][6].
Published claims
| Year | Who | Claimed | Status | Reason |
|---|---|---|---|---|
| 2015 | Chris Ashton and colleagues (Inmarsat)[2] | The satellite handshakes show that the aircraft flew south for six hours and ended near the seventh arc in the southern Indian Ocean. | Accepted | The method was validated on other aircraft flying known routes that night, and debris confirmed from 9M-MRO later washed up on western Indian Ocean shores[2][5]. |
| 2016 | Samuel Davey and colleagues (Defence Science and Technology Group)[3] | A Bayesian model of the satellite data puts the most probable end of flight in a priority area along the arc centred near 38°S. | Disputed | The 120,000 km² search built on it found nothing, and the ATSB concluded the aircraft was not there[4]. |
| 2017 | Australian Transport Safety Bureau[4] | The aircraft is not in the 120,000 km² searched area, and the most likely remaining place is a 25,000 km² stretch of the arc between about 32.5°S and 36°S. | Disputed | Ocean Infinity searched that stretch and more in 2018 and found nothing[1][7]. |
| 2017 | Australian Transport Safety Bureau[5] | The recovered flap and flaperon were not extended when they separated, which argues against a controlled ditching. | Accepted | It rests on the ATSB's and French investigators' examinations of the parts; the contrary reading of the same damage has not been accepted by any investigating body[1]. |
| 2017 | David Griffin and colleagues (CSIRO)[6] | Drift modelling with replica flaperons puts the most likely end of flight near 35.6°S 92.8°E on the arc. | Disputed | The 2018 search covered that latitude near the arc without result, so either the wreckage lies farther from the arc there or the latitude is different[1]. |
| 2018 | Larry Vance[10] | The captain flew the aircraft to the end and made a controlled ditching with the flaps extended, so the wreckage lies beyond the searched band. | Disputed | The official examinations found the flaps retracted, and the final handshakes imply a rapid descent, though the glide zone has never been searched[5][4]. |
| 2018 | Malaysian ICAO Annex 13 Safety Investigation Team[1] | The turn-back was flown manually, the cause of the disappearance cannot be determined, and interference by a third party cannot be excluded. | Accepted | The official finding; nothing found since, including two further seabed searches, has changed it[8]. |
| 2019 | Jeff Wise[11] | Russian operatives took the aircraft north to Kazakhstan, and the satellite data were spoofed to send searchers south. | Ruled out | Wreckage confirmed from 9M-MRO by part numbers washed up on western Indian Ocean shores, consistent with drift from the southern arc and not with a northern route[5][6]. |
| 2019 | William Langewiesche[12] | Captain Zaharie Ahmad Shah took the aircraft in a deliberate murder-suicide, and Malaysian authorities failed to pursue the evidence. | Still possible | The manual turn-back and the simulator route fit it, but the official investigation found nothing in the crew's records showing intent and did not conclude[1]. |
| 2021 | Florence de Changy[13] | The aircraft was intercepted and destroyed near the South China Sea in an operation involving the United States, and the southern search was a cover. | Ruled out | Wreckage confirmed from the aircraft drifted to African and Indian Ocean shores, as the validated satellite analysis predicts for an end on the southern arc[5][2]. |
| 2023 | Richard Godfrey, Hannes Coetzee and Simon Maskell[15] | Disturbances in amateur radio (WSPR) links track the aircraft to an end about 1,560 km west of Perth, near 29°S 99.5°E. | Still possible | Whether WSPR can detect aircraft at all was still being tested in 2024, and other analysts are sceptical[14]. |
| 2024 | Usama Kadri[16] | Hydrophones can detect an aircraft hitting the sea at long range, and the records of March 2014 hold one possible signal at a single station. | Still possible | The candidate signal appears at only one of two stations, and the calibration explosions the paper proposes have not been carried out[16]. |
What would settle it
Finding the wreckage. The flight data and cockpit voice recorders, if recoverable after a decade at depth, would show who did what; the wreckage pattern would show whether the aircraft came down fast or was ditched. The remaining question is where to look. The 2025–2026 campaign covered half its target; the rest of that area, the stretches of the arc beyond 25 nautical miles that a glide could reach, and the latitudes north of 33°S are the candidates[4][8]. Short of the wreckage, a re-examination of the satellite data with the methods and the drift knowledge now available, published with the raw log, would narrow the field; and any further debris with a recorded find date and location tightens the drift back-calculation[6].
Questions
0 of 4 questions are answered.
Evidence 24 findings
Artifacts
The films, photos, papers and objects this mystery rests on, each with its own key and its distance from the original.
See also
References
- 1.The Malaysian ICAO Annex 13 Safety Investigation Team for MH370 2018. Safety Investigation Report: Malaysia Airlines Boeing B777-200ER (9M-MRO), 08 March 2014. Ministry of Transport Malaysia.cited 24 times hereSRC0CWY6VPT0VHS
- 2.Ashton, C., Shuster Bruce, A., Colledge, G. et al. 2015. The Search for MH370. Journal of Navigation.doicited 9 times hereSRC0CWY6VYM12BH
- 3.Davey, S., Gordon, N., Holland, I. et al. 2016. Bayesian Methods in the Search for MH370. SpringerBriefs in Electrical and Computer Engineering (Springer Open).doicited 2 times hereSRC0CWY6W6E0M24
- 4.Australian Transport Safety Bureau 2017. The Operational Search for MH370. ATSB Transport Safety Report AE-2014-054.cited 17 times hereSRC0CWY6WE84KX8
- 5.Australian Transport Safety Bureau 2017. MH370: Search and debris examination update. ATSB, AE-2014-054.cited 13 times hereSRC0CWY6WP203TC
- 6.Griffin, D., Oke, P., Jones, E. 2017. The search for MH370 and ocean surface drift (Parts I–IV). CSIRO Oceans and Atmosphere, for the ATSB.cited 10 times hereSRC0CWY6WXW471K
- 7.Associated Press / NPR 2025. Malaysia approves a new search for MH370 wreckage in the Indian Ocean. NPR.cited 4 times hereSRC0CWY6XDG5P5A
- 8.Associated Press / NPR 2026. 12 years on, renewed hunt for missing Malaysia Airlines flight comes up empty. NPR.cited 2 times hereSRC0CWY6XNA1B2C
- 9.Department of Civil Aviation Malaysia, Inmarsat 2014. MH370 Data Communication Logs (Inmarsat satellite communications log). Released by the Malaysian government, 27 May 2014.cited 6 times hereSRC0CWY6X5P6CRM
- 10.Vance, L. 2018. MH370: Mystery Solved.cited 1 time hereSRC0CWY6ZVM1ZTV
- 11.Wise, J. 2019. The Taking of MH370. The Yellow Cabin Press.cited 1 time hereSRC0CWY703E6RK6
- 12.Langewiesche, W. 2019. What Really Happened to Malaysia's Missing Airplane. The Atlantic, July 2019 (online 17 June 2019).cited 1 time hereSRC0CWY70B82FSH
- 13.de Changy, F. 2021. The Disappearing Act: The Impossible Case of MH370. HarperCollins.cited 1 time hereSRC0CWY70K24K95
- 14.University of Liverpool 2024. Researchers provide statistical expertise to help locate missing flight MH370. University of Liverpool news, 6 March 2024.cited 1 time hereSRC0CWY712P7QWR
- 15.Thomas, G. 2023. MH370: Ground-Breaking Report Reveals Location. Airline Ratings, 31 August 2023.cited 1 time hereSRC0CWY70TW4V7P
- 16.Kadri, U. 2024. Underwater acoustic analysis reveals unique pressure signals associated with aircraft crashes in the sea: revisiting MH370. Scientific Reports 14, 10102.doicited 1 time hereSRC0CWY71AG4CZF