Skip to content

Resources

Resources

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

35 hits

EvidenceConfirmed4 Nov 2003 00:00 UTC

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.

ClaimConfirmed

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.

TimelineConfirmed4 Nov 2003 00:00 UTC

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.

EvidenceOpen20 Sep 2026

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.

EvidenceConfirmed19 Feb 2003 00:00 UTC

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.

HypothesisUnverified

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.

TimelineConfirmed19 Feb 2003 00:00 UTC

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.

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.

ClaimUnverified18 Sep 2026

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.

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.

Open questionOpen

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.

EvidenceConfirmed19 Sep 2013

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.

TimelineConfirmed15 Dec 2014 00:00 UTC

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.

EvidenceConfirmed10 Apr 2013

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.

HypothesisOpen

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.

DocumentUnverified1 Mar 2019 00:00 UTC

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.

DocumentOfficial finding18 Sep 2026 00:00 UTC

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.

OrganisationConfirmed24 Aug 2013 00:00 UTC

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.

OrganisationConfirmed15 Oct 2014

Lockheed Martin Compact Fusion Reactor

Public Skunk Works programme · Thomas McGuire · not an MH370 finding

Confirmed as a public Lockheed Skunk Works fusion project, discussed openly around 2014, with patents including US9947420 (magnetic-field plasma confinement; filing family 2 April 2014). Quiet Exodus treats it as the power core of a clandestine spacetime platform. That leap is the thesis, not the patent.

DocumentOfficial finding20 Sep 2026 00:00 UTC

MH370 Research Master Log

Investigation chronology · 18–20 September 2026

Running chronology of findings: cargo, 2011–2013 ISR programmes, radar disclosure on the westbound track, MAGIC budget exhibits, and the alleged-video file.

TimelineConfirmed24 Mar 2014

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.

TimelineConfirmed24 Aug 2013 00:00 UTC

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.

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.

PersonUnverified

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.

OrganisationConfirmed

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.

DocumentOfficial finding1 Jan 2016 00:00 UTC

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.

TimelineOfficial finding30 Jul 2018 00:00 UTC

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.

DocumentConfirmed18 Sep 2026 22:50 UTC

MH370 Daily Research — working papers

18 September 2026

Working ISR report, source ledger and master chronology gathered the same day, with a cited-URL set pointing at contemporary MAGIC, Orion and Gorgon Stare reporting.

LocationConfirmed

NAWS China Lake

Orion first flight · 24 August 2013

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

ClaimConfirmed

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.

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.

DocumentConfirmed1 Sep 2013

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.

ClaimOpen

Third-party intervention cannot be excluded

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

EvidenceOpen9 Mar 2014

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.

Open questionOpen

Which of the ten theatre dossiers can actually be pulled?

The forensic board’s bottom row: 4 March Boeing statement of work; P-8/P-3 7–8 March sortie logs; Global Hawk records; Pinckney/Kidd pre-search tracks; JORN operating/tasking logs; SBIRS retrospective; Five Eyes MH370 correspondence; Boeing performance datasets; 9M-MRO avionics/mod configuration; early US intel reporting.

273 records in the file.