A National Order Inside a Common Baseline
Australian funds, Boeing’s integration and United States configuration authority meet in an $11.381 million flight-control software order.
On 31 July 2026 the United States Department of War announced that The Boeing Company had received a cost-plus-fixed-fee order, N0001926F1107, valued at $11,381,402, for the development, testing and delivery of aircraft-loadable flight-control software correcting six disclosed deficiencies in the P-8A autopilot system. Royal Australian Air Force funds cover the whole of it, and none were due to expire at the end of the United States fiscal year. Against the other P-8A actions disclosed under the same basic ordering agreement, the figure is small: an order of 22 June 2026 for nine Increment Three Block Two retrofit A-kits was valued at $121,195,041, and a training-systems contract announced on 18 June 2026 was awarded at $880,000,000. It is smaller still against the $63,720,841 that the Defense Security Cooperation Agency set in 2016 as the United States non-recurring-cost recoupment charge for a single P-8A. The structural constraint is that in a cooperative programme the party that funds a correction is not thereby the party that controls its code, its configuration, its release or its use: financial contribution, contractual administration, industrial design authority, configuration authority and airworthiness approval are separate functions held by separate bodies. What the award notice does not answer is whether the software, the evidence and the configuration decision it generates become reusable programme assets across the P-8A fleets, or remain tied to an Australian requirement and a national release.
The report proceeds in seven sections. The first reads the award notice against Federal Acquisition Regulation 16.703 and 16.306, separating the ordering vehicle from the funded work and the announced value from the Government’s financial exposure. The second sets the order inside the Australian record: the completion of the fourteen-aircraft fleet on 27 May 2026, the AIR 7000 figures reported in the Portfolio Budget Statements 2026–27, and the audit history of the project in the Australian National Audit Office’s Major Projects Report, including the caveats Defence declared on the Operational Capability 2 milestone in February 2019. The third examines what the six published deficiencies do and do not establish, against Department of Defense Instruction 5000.98, MIL-STD-882E and MIL-HDBK-516D. The fourth compares the order with the other 2026 actions issued under basic ordering agreement N0001926G1002. The fifth traces the chain from software development to fleet release, using the Naval Air Systems Command record for Increment Three Block Two. The sixth sets United States airworthiness policy under Department of Defense Instruction 5030.61 against the Defence Aviation Safety Regulations and the Military Type Certificate held by the Surveillance and Response Systems Program Office. The seventh reads the rights position through DFARS 252.227-7013, 252.227-7014, 252.227-7017 and 227.7203-16. The report does not value Boeing, does not assess the order as an investment event, does not identify the unnamed Foreign Military Sales customer of the July 2026 reconfiguration action, and does not predict which configuration outcome will occur.