Resources
Resources
Official papers, films, Wikipedia and its citations, programmes, claims and open questions.
12 hits
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.
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.
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.
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.
MAGIC was designed for multi-INT payload modularity, not only endurance
OSD PB2012 lists EO/IR, SIGINT, GMTI, wide-area surveillance, communications relay and strike as modular payload classes, plus reduced-manning / open-architecture avionics. That is the documented architecture. It is not an installed-GFE list for March 2014.
Twenty Freescale employees on MH370
Company-confirmed 8 March 2014
Confirmed passenger fact. Project assignments, especially defence/avionics/inertial work, are unresolved. FXAS21000 gyro sampling in July 2013 is an adjacent product date only.
What were the 20 Freescale passengers working on?
Presence on the flight is confirmed. Defence/avionics/inertial/radar assignment is unresolved. FXAS21000 gyro timing is an adjacent product fact, not a link.
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.
MAGIC JCTD initiated
FY2010 Q3 · OSD/DDR&E
Competition among five defence-industry partners. $5m initial to AFRL. CENTCOM persistent-ISR sponsorship in Aurora’s 2010 release.
OSD PB2012 — MAGIC JCTD primary record
PE 0603648D8Z · pp. 32–33 · USCENTCOM sponsor
Primary OSD budget exhibit: MAGIC is a USCENTCOM-sponsored JCTD. 120-hour sortie, nominal 1,000 lb / maximum 2,600 lb at 15,000 ft. Modular payload classes: EO/IR, SIGINT, GMTI, wide-area surveillance, communications relay, strike. Transition named to USAF 303rd AESW.
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.
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.
273 records in the file.