Inquiry probes BA A320’s air-data reference incident and degraded flight law - FlightGlobal

The article as published is a paywalled FlightGlobal subscription page rather than the underlying incident report, but the headline itself flags a serious technical event worth unpacking for operators of the Airbus A320 family: a British Airways A320 experienced an air-data reference fault that led the aircraft to enter a degraded flight control law, prompting a formal safety inquiry. On Airbus fly-by-wire aircraft, the flight control computers rely on redundant air-data and inertial reference units (ADIRUs) to determine airspeed, altitude, and attitude, which in turn feed the normal law protections that keep the aircraft within its flight envelope. When the system detects unreliable or disagreeing air-data inputs, it automatically reverts to alternate law or, in more severe cases, direct law, stripping away some or all of the automatic envelope protections and shifting more direct authority—and responsibility—to the pilots. An inquiry into such an event typically examines whether the fault stemmed from a sensor failure (pitot-static blockage, icing, or a probe malfunction), a software/logic issue in the air-data reference unit, or an external factor such as heavy precipitation or a bird strike affecting the probes.

For working airline and corporate pilots, this type of event is a pointed reminder of why recurrent training continues to emphasize unreliable airspeed and law-degradation scenarios, a lesson reinforced industry-wide since the Air France 447 accident in 2009, which was precipitated by pitot tube icing and a cascading loss of normal law protections. Even on modern, highly automated aircraft, crews must remain proficient at recognizing ECAM/EICAS caution messages tied to air-data disagreement, cross-checking standby instruments, and manually flying the aircraft with reduced protections—skills that can atrophy in an era of heavy reliance on autoflight and autothrust. A degraded law event also has operational consequences beyond the immediate flight: it typically triggers a maintenance and engineering review of the affected air-data components, potential fleet-wide inspections or bulletins if a systemic cause is suspected, and scrutiny from the airline's flight safety department and the relevant regulator (in this case, the UK Air Accidents Investigation Branch or CAA) to determine whether wider corrective action is warranted.

More broadly, this incident sits within a recurring pattern of air-data-related safety investigations across the fly-by-wire fleet, from AF447 to various documented ADIRU faults on Airbus and Boeing aircraft over the past two decades, including sporadic reports of erroneous angle-of-attack or airspeed data triggering unexpected control law reversions or, in Boeing's case, MCAS-related consequences. Regulators and manufacturers have progressively hardened redundancy architectures and voting logic between multiple air-data sources, but no system is entirely immune to sensor-level anomalies, environmental contamination, or software edge cases. For fleet operators and training departments, each new inquiry of this kind reinforces the value of scenario-based simulator training that goes beyond rote procedure-following to build genuine manual-handling competence under degraded automation—an area regulators such as EASA and the FAA have pushed airlines to strengthen through revised evidence-based training frameworks. Pilots should watch for the eventual findings from this BA inquiry, as any identified root cause—whether hardware, software, or procedural—could inform fleet-wide bulletins, revised QRH procedures, or updated air-data monitoring requirements affecting the broader A320 operator community.