Boeing 787 Core Software Updates Must Go Through Manufacturer and FAA Approval

The Boeing 787 Dreamliner employs a revolutionary software architecture that significantly differs from previous commercial jetliners, embedding a complex software ecosystem integral to the aircraft’s certification. Unlike earlier models with discrete avionics boxes each running standalone software, the 787 operates largely on a shared computing platform known as the Common Core System (CCS). This system consolidates critical aircraft functions into approximately 300 software components distributed across the airframe, making the software inseparable from the aircraft's FAA type certificate.

This integrated architecture means the 787 software cannot be independently updated by airlines. Any modification to the core software, including flight control laws and critical safety functions, is classified as a type design change that legally must be routed through Boeing's engineering department and undergo FAA scrutiny and approval before being deployed on in-service aircraft. This contrasts sharply with older aircraft like the 767 or 777, where updating an individual avionics system was a modular and isolated task.

On traditional aircraft, avionics functions such as flight management, weather radar, engine instruments, and autopilot run on separate dedicated hardware units. Each unit is certified independently, allowing airlines or third parties to update software components in isolation without affecting others. The 787's CCS replaces this with a smaller number of shared processors hosting multiple interdependent software applications, raising system complexity and tight coupling of functions.

Because these software applications share processing resources and data networks on the CCS, a change in one can impact others, necessitating broader testing and regulatory certification. The FAA thus certifies the entire software package as part of the 787’s aircraft type design rather than discrete software products. This ensures safety and reliability but restricts airlines from applying patches or fixes without Boeing’s direct involvement and regulatory approval.

While airlines are limited in direct software development, Boeing provides a controlled configuration framework called Airplane Software Options. Through this, operators can select configurable settings within a pre-approved scope—such as cabin management features, crew alerting parameters, and display preferences—that tailor software behavior to their needs. Even these adjustments, however, require regulatory acceptance before implementation to ensure compliance with the certified envelope.

The software’s certification as part of the airframe carries practical implications, highlighted by the 2020 FAA airworthiness directive requiring 787 operators to power the aircraft down every 51 days. This mandate arose because laboratory testing showed that a stale data monitoring function within the CCS ceases to operate after 51 days of continuous power, potentially causing incorrect flight instrument displays and loss of certain warning systems. Fixing such issues is beyond airline maintenance scope and depends on Boeing-led design changes approved by regulators.

The 787's software model reflects evolving aviation technology trends favoring integrated digital systems that enhance efficiency and capability but increase certification complexity. For airlines, this approach demands closer collaboration with manufacturers and regulators when updating core systems. The result is an aircraft whose sophisticated software-driven architecture is inseparably tied to its certified design, fundamentally altering how airline operators manage software updates and maintenance.