Skip to content

Resources

Resources

Official papers, films, Wikipedia and its citations, programmes, claims and open questions.

52 hits

ClaimOfficial finding

The 18:25 log-on follows a SATCOM power interruption

Official: aircraft-initiated log-on three minutes after last radar is most likely SDU power restore. Why power was lost is unknown.

EvidenceConfirmed7 Mar 2014 16:00 UTC

Inmarsat signalling-unit log for 9M-MRO

Perth Ground Earth Station · 7–8 March 2014

The table of channel, BTO, BFO and message type that underpins every arc on every search map. Released by Malaysia with Inmarsat notes.

DocumentConfirmed1 May 2014 00:00 UTC

Inmarsat signalling-unit logs for 9M-MRO

Perth Ground Earth Station · 7–8 March 2014

The raw-ish tables of channel, BTO, BFO and message type that underpin every arc on every search map. Released by Malaysia with Inmarsat explanatory notes.

DocumentOfficial finding1 Dec 2016 00:00 UTC

DSTG Bayesian flight-path analysis

Defence Science and Technology Group, Australia

A probabilistic reconstruction of MH370’s path from SATCOM metadata. Output is a distribution along the 7th arc, not a pin in the map.

TimelineConfirmed7 Mar 2014 18:25 UTC

Satellite data unit logs back on

18:25:27 UTC · Handshake 1

Three minutes after the last radar paint, the aircraft SDU sends a log-on request to Inmarsat. Investigators treat this as a power restoration to the SATCOM avionics.

TimelineConfirmed7 Mar 2014 20:41 UTC

Handshake 3

20:41:02 UTC

Third SATCOM handshake. Hourly keep-alive continues.

TimelineConfirmed7 Mar 2014 21:41 UTC

Handshake 4

21:41:24 UTC

Fourth SATCOM handshake, still on the southern corridor in BFO reconstructions.

TimelineConfirmed7 Mar 2014 22:41 UTC

Handshake 5

22:41:19 UTC

Fifth SATCOM handshake.

TimelineConfirmed8 Mar 2014 01:15 UTC

Failed handshake — terminal silent

01:15:56 UTC

The ground station interrogates 9M-MRO and receives no response. The aircraft is no longer a live terminal.

DocumentConfirmed13 Mar 2014

Is Flight 370 still sending signals?

CNN · 13 March 2014 · 2:09

Week-one report, before the 15 March Inmarsat southern-arc briefing. Captures the live confusion over whether the aircraft was still electrically alive.

Open questionOpen

Is the public ACARS log missing a block of messages?

Jericho 2019 attributes a ~26-minute exclusion in the released ACARS traffic log and an ACARS-unavailable window of roughly 22–78 minutes. Needs a line-by-line check against the MOT 2015 Factual Information ACARS appendix.

TimelineConfirmed7 Mar 2014 17:07 UTC

Last ACARS transmission

17:07:29 UTC

The final Aircraft Communications Addressing and Reporting System message leaves 9M-MRO. Expected reports at 17:37 and 18:07 never arrive.

LocationOfficial finding

7th arc (schematic locus)

00:19 UTC range ring from Inmarsat I-3

Search geometry, not a wreck coordinate. Official and Ocean Infinity boxes are arguments about a segment of this arc.

EvidenceOfficial finding15 Mar 2014 00:00 UTC

BTO range rings and BFO Doppler residuals

Inmarsat / Ashton et al. · Journal of Navigation

Burst Timing Offset describes distance from the satellite (an arc on the Earth). Burst Frequency Offset encodes relative motion and is why official analysis went south, not north.

Open questionOpen

Could the Inmarsat BFO have been spoofed?

Wise’s northern path stands or falls on this. Inmarsat and ATSB treat BFO as a physical Doppler residual. No public demonstration has shown a 2014-era 777 SDU emitting a false BFO while keeping a consistent BTO.

TimelineConfirmed7 Mar 2014 19:41 UTC

Handshake 2

19:41:00 UTC

Ground-initiated hourly handshake. The aircraft remains a live Inmarsat terminal, southbound on the Indian Ocean corridor in later reconstructions.

TimelineConfirmed8 Mar 2014 00:10 UTC

Handshake 6 — last successful hourly ping

00:10:58 UTC 8 March

The last completed ground-initiated handshake. Eight minutes later the aircraft sends a log-on associated with fuel exhaustion.

TimelineOfficial finding8 Mar 2014 00:19 UTC

Handshake 7 — aircraft-initiated log-on

00:19:29 UTC · probable fuel exhaustion

The SDU sends a log-on request, then a log-on acknowledge eight seconds later. The investigation treats this as power-up after dual engine flame-out.

OrganisationConfirmed

Inmarsat

Classic Aero I-3 · Perth Ground Earth Station

The communications company that became the principal witness to MH370’s last six hours.

TimelineConfirmed7 Mar 2014 23:13 UTC

Second unanswered sat-phone call

23:13:58 UTC

Another ground-to-air telephone call is acknowledged by the SDU and unanswered in the cockpit.

ClaimOfficial finding

The 00:19 log-on is probable fuel exhaustion

Official finding: aircraft-initiated log-on most likely a power restore after dual flame-out and APU/bus bring-up.

EvidenceOfficial finding8 Mar 2014 00:19 UTC

The 7th arc

00:19:29 UTC aircraft-initiated log-on

BTO range ring at the last transmission. Official and Ocean Infinity boxes are arguments about a segment of this arc plus a stand-off. It is not a crash pin.

DocumentOfficial finding7 Oct 2014 00:00 UTC

The Search for MH370 — Journal of Navigation

Ashton, Dickinson, Hall, Roberts, Smith · Inmarsat · 2014/15

The paper that showed how BTO and BFO from routine signalling units can reconstruct a long flight the airline did not know it still had.

TimelineConfirmed7 Mar 2014 18:39 UTC

Unanswered ground-to-air telephone call

18:39:52 UTC

Malaysia Airlines operations places a sat-phone call to the aircraft. The SDU acknowledges the incoming call; nobody in the cockpit answers.

EvidenceOpen20 Sep 2026

Forensic evidence board — facts, capabilities, missing dossiers

Working chart of intersections · ten target records still outstanding

Cork-board reconstruction: Malaysian military radar and MH370 data on one side; QF-16 2013, UAV/UAS patents, JORN, Kadena P-8A/P-3C, Inmarsat SATCOM and Boeing range models on the other. The bottom row is the live request list — Boeing’s 4 March statement of work, sortie logs, Global Hawk, Pinckney/Kidd tracks, JORN tasking, SBIRS, Five Eyes correspondence, 9M-MRO avionics configuration.

LocationConfirmed

Andaman Sea / last primary radar

18:22:12 UTC

Final military primary return, northwest of Malaysia. After this, only SATCOM.

Open questionOpen

Did 9M-MRO have any path for external flight-control commands?

Patents prove the concept. The test is hardware/software, SATCOM/data-link, power architecture, and maintenance/modification records on this tail.

DocumentOfficial finding8 Mar 2015 00:00 UTC

Factual Information — MH370

Malaysian investigation team · interim releases 2014–2015

Early factual compilations: aircraft history, crew, cargo, ATC transcripts, radar, SATCOM. Released before debris and before the 2018 analysis chapters. The 8 March 2015 issue (updated 15 April 2015) is held here as a downloadable original.

OrganisationConfirmed

Joint Agency Coordination Centre

Australia · southern Indian Ocean search coordination

Stood up to run the multinational southern search after the SATCOM pivot.

HypothesisDisputed

Mechanical / cargo-fire failure

Official report: no identified failure mode fits

A running systems failure that also produces a coherent reverse course and six more hours of SATCOM is a poor fit. Lithium-battery cargo was reviewed and not adopted as cause.

PersonConfirmed

Petter Hörnfeldt

Mentour Pilot

56-minute 2024 reconstruction from the official report and independent SATCOM papers. Sequential transponder-off, seven handshakes, Blelly–Marchand end-of-flight, WSPR as a possible extra trace. Stated aim: restart the search.

ClaimConfirmed

The aircraft ended in the southern Indian Ocean

Supported by SATCOM southern BFO, 7th-arc geometry, and serial-confirmed debris on western Indian Ocean coasts. Main wreckage still unfound.

Open questionOpen

Why did SAR start in the wrong ocean for days?

Military primary radar and live SATCOM existed while the public search flew the South China Sea. Minister ~10:30 MYT; KL ARCC 22:30; Thai Surat Thani 18–19 March. GADSS is the policy answer; the night-of organisational failure is still a research subject.

DocumentProbable16 Mar 2024

A NEW Trace! The FULL MH370 Story, so Far

Mentour Pilot · Petter Hörnfeldt · 16 March 2024 · 56:06

Type-rated 737 captain’s reconstruction from the 2018 report, Inmarsat BTO/BFO, and the Blelly–Marchand end-of-flight paper. Argues the transponder was selected off in two steps, not failed as a unit. Closes with a WSPR lead and a request to restart the search.

HypothesisUnverified

Asset denial of the Freescale team

Quiet Exodus thesis · not adopted as a finding

Hypothesis: the United States removed twenty Freescale employees from China’s reach, using a clandestine compact-fusion platform, because they were the programme’s irreplaceable integration unit. Headcount is confirmed. The programme-link, the intercept, and the 18:22 structural kill are not.

LocationConfirmed

ATSB underwater search box 2014–2017

~120,000 km² · suspended 17 January 2017

High-resolution seabed search along a refined 7th-arc corridor. No wreckage.

OrganisationConfirmed

Australian Transport Safety Bureau

Lead of the 2014–2017 southern Indian Ocean search

Drew and exhausted the 120,000 km² underwater box. Operational-search report is the engineering baseline for later Ocean Infinity boxes.

OrganisationConfirmed14 Mar 2011 00:00 UTC

Blue Devil I / II

Operational Block 1 WAAS + SIGINT · Block 2 residuals to BIG SAFARI

Block 1 was operational: manned aircraft carrying Angel Fire-derived wide-area imagery integrated with SIGINT. Block 2, the airship, was terminated — but its equipment, including GFE, was packed and sent to a BIG SAFARI facility in Greenville, Texas, available for other programmes. The technology did not vanish with the airship.

EvidenceDisputed15 Mar 2014 00:00 UTC

Captain’s home flight-simulator files

Imaged by RMP · restored coordinates mapped by commentators

Files exist. A restored route into the southern Indian Ocean has been published. The 2018 report did not treat this as a reconstructed plan.

EvidenceOfficial finding7 Mar 2014 16:00 UTC

Cargo, including lithium-ion batteries

Manifest reviewed; fire hypothesis not supported

The aircraft carried cargo including lithium-ion batteries. The investigation found they were packed to regulation and did not support a cargo-fire cause.

HypothesisOpen

Controlled descent / ditching

Someone still flying at the end

A pilot or system flies a glide after flame-out, so the wreck lies tens of kilometres from the 7th arc. Flaperon damage is read by some independent engineers as consistent with a ditching sequence.

DocumentProbable8 Mar 2024

Flight MH370 Vanished 10 Years Ago. What’s Happened Since?

CNA Insider · Insight · 8 March 2024 · 47:24

Tenth-anniversary Singapore broadcast: Inmarsat handshake rings, the 120,000 km² ATSB box, family pressure, and the state of independent debris work. Does not adopt a cockpit perpetrator.

HypothesisOpen

Flight-crew diversion

Manual inputs from the cockpit — who, and why, unproven

The 2018 report says the turn-back likely resulted from manual inputs. It does not identify a crew member as perpetrator and did not treat the home simulator as a plan.

TimelineConfirmed7 Mar 2014 16:42 UTC

MH370 departs Kuala Lumpur

16:42 UTC · 00:42 MYT 8 March 2014

Malaysia Airlines Flight 370, a Boeing 777-2H6ER registered 9M-MRO, takes off from KLIA runway 32R bound for Beijing Capital International Airport with 227 passengers and 12 crew.

DocumentProbable13 Jun 2026

MH370: The Forensic Evidence

Capt. John Cox · Sit Down With Sid · 13 June 2026 · 37:10

US accident investigator. Reads the transponder drop at the FIR boundary, the southwest run to MEKAR, the northwest turn, and the 300-mile ocean leg as too many coincidences for a random failure. Preponderance, in his view: a deliberate act, high likelihood the captain.

DocumentUnverified8 Mar 2023

MH370: The Plane That Disappeared

Netflix · three episodes · March 2023

Louise Malkinson’s three-part series gives one episode to each of three tellings: the pilot, a Russian hijack (Jeff Wise), and a US intercept (Florence de Changy). Families and Malaysia Airlines crisis staff are interviewed. It is a survey of hypotheses, not a finding.

PersonConfirmed

Najib Razak

Prime Minister of Malaysia, 2014

On 24 March 2014 announced that MH370 ended in the southern Indian Ocean with no survivors, based on Inmarsat’s then-new analysis.

DocumentUnverified1 Jan 2026

Project Quiet Exodus — Part 1

SecretMilitaryTechnology.com thesis · asset denial of the Freescale team

A long-form thesis that MH370 was a US operation to stop twenty Freescale employees reaching China, protecting a compact-fusion / spacetime platform. Public facts inside it (headcount, Carlyle, Lockheed CFR patents, HA08 outage, UCT-2 at Diego Garcia) are filed separately. The operation itself is not established.

DocumentOfficial finding30 Jul 2018 00:00 UTC

Safety Investigation Report — MH370

Malaysian ICAO Annex 13 Team · 30 July 2018

The official accident report. Cause undetermined. Diversion likely from manual inputs; third-party intervention not excluded; 00:19 log-on treated as fuel exhaustion. No wreckage, no recorders.

DocumentUnverified17 Jun 2025

The MH370 Mystery — Parts 1 and 2

Easy Documentary · June 2025

Two-part compilation: Part 1 the public crash/disappearance narrative; Part 2 “inside the investigation’s biggest failures.” Secondary retelling of already-filed records.

DocumentOfficial finding3 Oct 2017 00:00 UTC

The Operational Search for MH370

ATSB AE-2014-054 · final search report 2017

Australia’s account of how the southern Indian Ocean search box was drawn, refined, and exhausted over 120,000 km². Primary technical home of the 7th-arc argument used in the field.

DocumentProbable18 Sep 2026

Wikipedia — Malaysia Airlines Flight 370

en.wikipedia.org · living page · read 18 September 2026

Crowd-maintained digest of the public case: 239 dead, 9M-MRO, 8 March 2014, KUL–PEK, cause undetermined. Useful as a citation map into ATSB, MOT, Inmarsat and Ocean Infinity. Not a primary source.

273 records in the file.