Software bug could make Boeing 787s lose all electrical power if planes' power control unit left on for 248 days
F.A.A. Orders Fix for Possible Power Loss in Boeing 787 — Federal regulators will order operators of Boeing 787 Dreamliners to shut down the plane's electrical power periodically …
Context & Ripple Effects
The F.A.A.'s directive lands weeks after a smaller but telling episode in the same news cycle: American Airlines grounded flights over a software fault on its crew iPads. Both stories mark 2015 as the moment software defects became a first-class airworthiness concern, treated like mechanical wear rather than a one-time certification question.
Boeing is the recurring subject here. The same regulator-driven software-remediation playbook returns four years later when the company promises an update to 737 Max flight control software after two crashes, per the related coverage, and resurfaces again in 2025 when Airbus orders 6,000 A320-series jets back to older software after solar radiation corrupted flight control data. The 787 order is an early, low-fatality data point in that arc.
First-order effects
- 787 operators must now schedule periodic full electrical shutdowns of the power control unit before it runs 248 days continuously, adding a maintenance constraint to fleet utilization planning.
- Boeing faces the cost and reputational exposure of an airworthiness directive against its flagship widebody while the jet is still early in its service life.
Second-order effects
- Regulators and manufacturers converge on mandated software rollbacks and re-certification as routine practice — Airbus's later order reverting thousands of A320-family planes to old software shows competitors absorbing the same operational disruption Boeing absorbs here.
- Airlines absorb a growing share of the burden: between this shutdown requirement, battery-goods restrictions the F.A.A. reiterated in 2019, and outages like the contractor file deletion behind the F.A.A. pilot-alert system failure, carrier operations teams are becoming de facto software risk managers.
Third-order effects
- If the pattern holds, type certification stops being a gate at entry into service and becomes a continuous obligation, with airworthiness directives functioning as software patch cycles — a structure the 737 Max crisis, where Boeing committed to updating flight control software after the Max 8 groundings, pushed from inconvenience toward existential scrutiny.
- The longer-term shift points toward regulators demanding formal software lifecycle management — versioning, rollback plans, uptime limits — from every manufacturer, making sustained engineering investment a condition of keeping fleets airborne.
The trend: Aviation regulation is shifting from certifying aircraft software once to managing it continuously, with airworthiness directives increasingly functioning as forced patch cycles across Boeing, Airbus, and their suppliers.