Resources

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.

Raytheon MTS-B as Orion payload lead

Reported option · 2012–13 USAF UAV MTS bookings in the $200m class

MTS-B is EO/IR FMV/targeting. Aviation Week 2010 attributed a planned pair of MTS-B turrets on Orion — planned, not fitted on the maiden article. Flight 18 (Dec 2014) carried 1,000 lb ballast. Raytheon 10-K totals do not identify Orion as the customer.

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.

What sensors were actually on Orion by March 2014?

Orion was selected as MAGIC’s multi-day, multi-sensor ISR aircraft. First flight had no mission system; flight 18 (Dec 2014) carried ballast. Those two points do not empty the aircraft. Sorties 2–17, including March 2014, are the hole. Gorgon Stare / MTS-B / VADER remain live leads, not closed fits.

Orion flight 18 — 80-hour record with 1,000 lb ballast

December 2014 · not an ISR-payload demonstration

Aurora’s endurance attempt was flight 18 and carried 1,000 lb of ballast. Maiden flight (no mission system) and this record flight both fail as evidence of an operational ISR stack. Payload on flights 2–17 remains open.

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.

What was on Orion flights 2–17 between August 2013 and March 2014?

First flight: no mission system. Flight 18 (Dec 2014): ballast. The MH370-relevant interval is the unlisted sorties in between, plus whether the ‘second flight series’ PB2015 said was being scheduled had begun by 8 March.

Blue Devil II stopped; hardware to Greenville

Payload stop 4 Jan 2012 · pack-out May 2012 · storage Q4 FY2012

Airship programme killed. Equipment packed and transferred to a BIG SAFARI-managed facility in Greenville, Texas. Components were available for other projects. Residual parts were later absorbed into other Air Force programmes.

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.

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.

Raytheon Space and Airborne Systems

ISIS radar · MTS for USAF UAVs · large classified SAS bookings

Radar on ISIS; MTS-B is an Orion payload lead. 2013 SAS booked $210m MTS for USAF UAVs and $862m classified. Those totals do not establish an MH370/MAGIC contract.

Business Case Analysis of MAGIC UAV System

Naval Postgraduate School thesis · public PDF

Academic model of MAGIC as long-range ISR, not a named communications-relay payload. The $510m RDT&E figure in the thesis is an academic model, not an official acquisition estimate.

DODIG-2013-128 — Blue Devil Block 2

DoD Inspector General · 19 September 2013 · 54 pages · Drive source copy

Primary. FA8620-11-C-4024, ~$149m spent, payload stop 4 Jan 2012, residual components absorbed into other Air Force programmes.

Gorgon Stare’s podded architecture was designed for more than MQ-9

HASC 113-102: open/podded architecture permitted integration on multiple aircraft types. Aviation Week 2010 named it as a potential MAGIC payload. An Orion installation by 8 March 2014 is not shown.

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.

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.

Boeing–NAVAIR delivery order signed 4 March 2014

$955,853.54 · N0001914D0012 · engineering/technical support · St Louis

Confirmed public contracting record, four days before MH370. Department of the Navy, Naval Air Systems Command, NAICS aircraft manufacturing, PSC R425 professional engineering/technical support. Subject of the order is not in the public header. Chronology is not a collection event.

Gorgon Stare

BIG SAFARI wide-area surveillance · podded, not MQ-9-only

Developed through BIG SAFARI. Increment 2 is ARGUS-derived EO plus Exelis IR. Congress treated the podded/open architecture as integrable on more than one aircraft type. MQ-9 is the documented host; an Orion fit by 8 March 2014 is open. 2013 OSD figure: 2 fps, not 6.

Handshake 3

20:41:02 UTC

Third SATCOM handshake. Hourly keep-alive continues.

MAGIC

Medium Altitude Global ISR and Communications

USAF endurance-ISR programme. Air vehicle: Aurora Orion. Office: 645 AESG / BIG SAFARI — the same rapid-acquisition group that ran Gorgon Stare and took Blue Devil residuals. Confirmed as a multi-day ISR platform in that family. A specific MH370 operation is not established and is not ruled out.

What was actually taken on 9 March — and did it include radar?

CSM said minutes of crisis meetings and classified documents, some related to MH370. The working chart asks whether radar information or discussions of the turn-back were in that set. No public loot list answers it. A negative would also be a finding.