Resources

Remote-control claims versus evidence gaps

Patent, QF-16, Teso FMS proof-of-concept · installation on 9M-MRO still open

Working chart: unmanned flight of a fighter-class jet was demonstrated in 2013; Boeing’s uninterruptible-autopilot patent exists; Hugo Teso showed an FMS proof-of-concept the same year. Boeing told Malaysian investigators there was no commercial implementation on the 2002 delivery. Radar proves a turn at IGARI, not who commanded it. Ten data requests remain.

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.

Boeing US7142971B2 — uninterruptible automatic control

Remote engagement · disconnected onboard controls

Confirmed patent disclosure. Claims include remote initiation, dedicated comms distinct from other aircraft communications, disabled onboard override, and automatic landing at a predetermined (including military) site.

External / uninterruptible autopilot on 9M-MRO

Engineering precedent exists. Installation on this airframe is not established.

Boeing US7142971B2 and Cubic US6641087B1 describe remote engagement, disconnected cockpit controls, dedicated links. No maintenance/mod/certification record currently in this archive places that architecture on 9M-MRO.

Cubic US6641087B1 — anti-hijack remote pilot

Commercial retrofit · satellite relay · cockpit exclusion

Confirmed patent. Activation onboard or by remote override; deactivate normal pilot control; uplink airspeed/altitude/fuel; optional disable of ordinary communications; CVR/FDR upload. USPTO: 4-year fee 4 May 2007, 8-year fee 4 May 2011, expired 4 Nov 2015 for later non-payment. In force on 8 March 2014. No installation evidence in this archive.

Cubic Defense anti-hijack remote-pilot patent granted

US6641087B1 · filed 9 Oct 2001 · granted 4 Nov 2003

Commercial-aircraft retrofit module: deactivate cockpit controls, satellite-relayed remote guidance, optional comms disable, FDR/CVR uplink. Confirmed IP. No evidence of airline installation.

Fuel exhaustion, then uncontrolled descent at the 7th arc

Prevailing official end-of-flight model

After a long southern cruise the aircraft flames out near 00:19 UTC, the SDU logs on from APU/emergency power, and the aeroplane leaves controlled flight. Wreckage should lie on or near the 7th arc.

What was actually fitted on 9M-MRO — SDU, FMS, data buses, 2012 Shanghai repair?

The remote-control board’s forensic finding: need the MAS engineering record, service bulletins, SDU upgrades, avionics and data-bus software versions, and a breakdown of the 2012 Boeing wing-tip repair at Shanghai, before anyone can say a control path physically existed on this tail.

Cubic remote-pilot patent was maintained through March 2014

US6641087B1: 4-year fee 4 May 2007, 8-year fee 4 May 2011, expired 4 Nov 2015 for later non-payment. Continuation US10/684,316 abandoned 18 Jan 2007. IP interest retained; prototype/certification still OPEN.

Boeing / USAF QF-16 unmanned full-scale demonstration, 2013

Pilotless fighter-class jet · not a 777 and not 9M-MRO

Confirmed capability. A QF-16 flew unmanned, including supersonic flight and landing, as a full-scale aerial target. That kills the slogan ‘nothing that size could be flown remotely in 2014.’ It does not place a remote architecture on a commercial 777.

Hugo Teso, 2013 — FMS proof-of-concept

Hack in the Box · research demonstration, not a 9M-MRO finding

Confirmed as a public research talk: Teso showed that flight-management logic could be reached and manipulated in a lab/simulation setting. FAA disputed operational risk. No record in this file places that path on 9M-MRO.

Orion 80-hour remotely controlled flight

December 2014 · 1,000 lb ballast · fuel for ~37 more hours

Contractor-confirmed endurance after MH370. This was flight 18 and carried 1,000 lb of ballast. Shows the air vehicle matured; does not rewind payload status to March.

Boeing files uninterruptible-autopilot priority

19 February 2003 · later US7142971B2

Patent architecture: remote or automatic engagement; onboard controls may be disconnected; dedicated communications; inaccessible power path. Precedent, not an MH370 installation.

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.

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.

Two waves of MH370-themed cyberattacks

9 March official-network intrusion · March–April public malware lures

Working chart of two separate campaigns. Attack one: 9 March spear-phish of officials at the Department of Civil Aviation, National Security Council and Malaysia Airlines — CyberSecurity Malaysia’s public account, disclosed in August. Attack two: MyCERT alerts on 24 March and 18 April about MH370-themed backdoors and a fake investigation-transcript phish aimed more widely. Destination IP in China is not the same as a finding that Beijing ran the operation.

MyCERT: MH370-themed backdoor and fake-transcript spear-phish

MA-381 · 24 March 2014 · MA-386 · 18 April 2014

Confirmed public advisories, a different campaign from the 9 March official-network intrusion. 24 March: a Facebook-app lure dropping a backdoor with remote-control (C2) capability. 18 April: emails posing as an investigation team / ICAO portal item, password-protected archive, fake MH370 transcript, command-and-control. Aimed at organisations and the public, not shown to be the DCA/NSC/MAS breach.

Aurora Orion RPA

Twin-diesel MALE UAS · China Lake first flight 24 Aug 2013

Selected air vehicle for MAGIC: a multi-day, medium-altitude remotely piloted ISR platform designed to carry multiple sensors. First flight (24 Aug 2013) had no mission system; the December 2014 endurance record carried ballast. Those two flights do not decide what was fitted on sorties 2–17, including March 2014.

MAGIC, Aurora and Boeing/NRL patents drop from the paper trail in 2014

Follow-up briefing: Aurora’s remote-operation work for the US military from about 2010; MAGIC and several Boeing and NRL patents then become hard to find in open documents in 2014. Redacted Blue Devil letters are shown with matching date cut-offs.

MH370 / US Military ISR Working Research Report v1

Working paper · 18 September 2026

Working paper on US military ISR programmes in the MH370 window: MAGIC, Orion, Gorgon Stare, Blue Devil and remote-control patents, read as one overlapping family under BIG SAFARI. The family is documented. A specific MH370 collection is not established and is not ruled out.

Third-party intervention

Official report: cannot be excluded

The Annex 13 team wrote that intervention by a third party cannot be excluded. Remote hijack as implemented technology on commercial 777s was ruled out.

Aurora Flight Sciences

HALE/MALE autonomy house · Orion prime

Founded 1989. Chiron optionally piloted aircraft 1996. Global Hawk structures since 1995. Centaur optionally piloted DA42 from 2010. AACUS autonomous helicopter demo February 2014. ALIAS is later drop-in copilot work.

Îlot Bernache, Mauritius

Confirmed left outboard aft flap · 10 May 2016

Second serial-confirmed major flight-control surface.

Orion first flight, China Lake

24 August 2013 · ~3.5 hours · 8,000 ft · no mission payload

Remote launch from GCS. Air vehicle and command link demonstrated. ISR stack not yet fitted.

Orion’s first flight carried no mission system

Confirmed by contemporary September 2013 reporting and consistent with PB2015’s FY2014 “best of breed” sensor-selection language. December 2014 endurance attempt was flight 18 with 1,000 lb ballast — also not an ISR-payload demonstration. Those two flights do not decide what Orion was, and they do not decide March 2014.

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.

Thinking About the U.S. Military’s Next-Generation UAS Force

OSD Office of Net Assessment · September 2013 · 112 pp. · HQ0034-09-D-3007-0013

Pre-MH370 OSD-commissioned report. Gorgon Stare / ARGUS-IS / ARGUS-IR: multi-lens arrays, lower frame rate and resolution than HD FMV, areas up to ~40 km². Comparison figure labels conventional FMV 30 fps and Gorgon Stare 2 fps.

Who was flying after IGARI?

Official report: cannot establish if anyone other than the two pilots was at the controls. Manual inputs likely; actor unknown.

Ashton Forbes

Independent researcher · alleged thermal and wide-area video

Source of widely circulated alleged thermal/WAMI videos and platform identifications. Those identifications are hypotheses, not findings. Plasma-orb claims are treated as unsubstantiated. A third-party extract of 824 of his videos is a claim list, not proof. Edward C. Lin FOIA does not name MH370.

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.

Blelly & Marchand: last log-on is not necessarily a straight dive

Independent paper used by Mentour: right-engine flame-out, APU start, cross-feed, possible eastward or gliding end. BFO steep-descent figures can be read as a manoeuvre, not only as a wreck on the arc.

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.

CTBTO HA08 North at Diego Garcia went dark in March 2014

Cable break ~189 km offshore · South array kept listening

Confirmed by CTBTO. The northern hydroacoustic segment of HA08, off Diego Garcia, suffered a trunk-cable fault in March 2014 about 189–190 km from shore, more than a kilometre and a half down. HA08 South continued. North stayed silent for twelve years. A conventional splash in the southern Indian Ocean is not thereby erased — Cape Leeuwin (HA01) and HA08 South remained in the network.

Flight MH370 — 17 Fascinating Facts

J. Jericho / The Free School · March 2019 · Drive backup PDF

Independent compilation of official-file facts with annexes (simulator pages, passenger list, cargo docs, Boeing patent, ACARS log). Not an official report. Several numbered “facts” still need MOT/ATSB cross-check.

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.

ICAO GADSS tracking standards

Global Aeronautical Distress and Safety System · post-MH370

The regulatory aftershock: aircraft must report position at least every 15 minutes in normal flight, and more often in distress, so a 777 cannot again fly dark for six hours unnoticed.

Jeff Wise: northern hijack to Kazakhstan, BFO spoofed

2015 New York Magazine thesis, restated in Netflix episode 2 and in Finding MH370 “Landing MH370.” Keep BTO, discard or spoof BFO, fly borders, land on a long Central Asian runway. Requires the African debris field to be explained away.

Landing MH370

Jeff Wise · Finding MH370 S1E27 · 28 November 2024 · 45:12

The northern-landing telling: discard or spoof BFO, keep BTO, fly borders, land at a long Central Asian runway (Wise’s 2015 candidate was Yubileyniy / Baikonur). Requires the African debris field to be explained away.

Last voice contact

17:19:30 UTC · “Good night Malaysian three seven zero”

Lumpur Radar transfers MH370 to Ho Chi Minh. The reply — attributed to the captain — is the last recorded voice transmission from the flight.

Malaysia releases the safety investigation report

30 July 2018

The ICAO Annex 13 team, led by Kok Soo Chon, publishes hundreds of pages and cannot determine the cause. Diversion is judged likely from manual inputs. Third-party intervention is not excluded.

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.

NAWS China Lake

Orion first flight · 24 August 2013

US Navy air weapons station in California. Orion and GCS shipped here July 2013.

Raytheon MTS award for HC/MC-130J — one day before MH370

$10.072556m · 10 systems · 7 March 2014

Chronology fact only. No evidence these turrets or aircraft observed MH370. HD-capable MTS-B was entering USAF inventory through 2013–14.

Right flaperon — Réunion

Found 29 July 2015 · confirmed 3 September 2015 as 9M-MRO

First physical evidence. Internal part numbers traced through EADS CASA to 9M-MRO. A 777 flaperon does not drift from Kazakhstan or the South China Sea to Réunion.

Right flaperon found on Réunion

29 July 2015

A Boeing 777 right flaperon washes ashore at Saint-Denis, Réunion. French authorities later confirm it is from 9M-MRO — the first physical evidence.

Third-party intervention cannot be excluded

Quoted residual from the 2018 report. Not a finding that it happened.

Turn back across the Malay Peninsula

17:21–17:52 UTC

Primary radar shows a left turn off the Beijing airway, a crossing of Malaysia, and a track toward the Andaman Sea. The official report calls this diversion likely the result of manual inputs.

Waypoint IGARI

17:20:31 UTC

MH370 passes IGARI, the FIR boundary between Kuala Lumpur and Ho Chi Minh, seconds before disappearing from secondary radar.