BUSINESS IMPACT

An Aircraft on Ground event does not begin with a failed box. It begins with a write-up that wasn't trended, a reset that closed the job card without closing the fault, and a spare that wasn't in the right station. By the time the AOG call goes out, the airline has already lost control of the commercial outcome.

The numbers are unambiguous. IATA's FY2024 maintenance cost benchmarking across 28 airlines and 2,703 aircraft shows average maintenance expenditure of $1,522 per flight hour and $5.05 million per aircraft per year. Industry research consistently places avionics at up to 30% of total aircraft maintenance cost. That is not a minor line item. It is one of the largest controllable variables on a carrier's P&L.

And the pain does not stop at direct cost. Maintenance problems sit inside the airline's controllable delay bucket, classified by the Bureau of Transportation Statistics as "air carrier delay." Every repeat avionics write-up that turns into a departure delay or a cancellation is a recovery cost, a customer service cost, and a schedule resilience cost rolled into one.

What makes avionics events particularly expensive is that they compound. A reset that dispatches the aircraft today creates a second write-up in three rotations. A spare that isn't pooled correctly turns a manageable technical defect into a multi-day AOG at an outstation. A troubleshooting process that stops at the first replaceable item guarantees the same fault returns.

This article is not about cataloguing component failures. It is about understanding why avionics events repeat — and why the industry's default response consistently underestimates the problem.

INDUSTRY REALITY CHECK

Every conference presentation and vendor white paper eventually produces a "top five avionics failures" list. Most of them are wrong — not because the failures are fabricated, but because the framing is.

There is no universal, normalized, cross-fleet frequency table for avionics failures at the ATA subsystem level. Airlines classify events differently. Dispatch reliability metrics are not directly comparable across operators. The most granular and actionable reliability data sits inside individual operator programs, OEM dashboards, and maintenance information systems — not in public databases.

What does emerge consistently across FAA Service Difficulty Reports, EASA Safety Information Bulletins, IATA operational guidance, and OEM maintenance materials is a set of failure families — patterns of system-level dysfunction that appear repeatedly regardless of aircraft type, route structure, or fleet age. The exact ranking within any given carrier's reliability review will depend on fleet composition, maintenance maturity, and route profile.

That is the more useful question. And it requires a different kind of answer.

CENTRAL THESIS

Avionics failures are misunderstood at their foundation. The industry treats them as component events. The evidence shows they are system-of-systems events — failures that sit at the intersection of sensing, power, wiring, software configuration, environmental exposure, troubleshooting discipline, spare availability, and repair turnaround time.

A pitot-static disagreement is not just an airspeed probe issue. It can be contamination after maintenance, heater degradation, tubing routing, or automation knock-on effects. A radio altimeter fault is not just a bad LRU. It can be a coaxial cable, an antenna seal, a susceptibility profile, or an RF environment. An ADS-B non-performance event is often not a dead transponder. It is a data-integrity problem sitting in software version, ICAO address configuration, or altitude-source mismatch.

› The failed component is a symptom. The system condition is the cause.

This distinction changes everything: how you troubleshoot, how you trend, how you spend on spares, and how you design your repair and rotable strategy. Organizations that understand this produce structurally lower repeat defect rates. Organizations that don't spend the same maintenance dollar on the same fault, repeatedly.

OPERATIONAL ANALYSIS

The following five families consistently generate disproportionate operational pain across commercial fleets. Each is examined from the operator's experience outward — what appears on the line, what actually causes it, and why it keeps coming back.

A. What Operators Experience

Airspeed disagree alerts. ADC miscompare. Automation cascade — autothrottle disengagement, yaw damper alerts, elevator trim warnings — appearing seconds apart in a high-workload phase of flight. Crew workload spikes before the aircraft is even level. The fault message says "airspeed" but the operational effect is far wider.

B. What Actually Causes It

Pitot blockage from contamination after waxing, painting, or line maintenance. Probe heater degradation reducing ice protection effectiveness at altitude. Tubing routing with low-point water traps. Probe model susceptibility under adverse weather conditions — a documented regulatory concern leading to fleet-wide replacements on Airbus widebody types. The ADC itself is the least likely root cause, yet it is the first thing that gets swapped.

C. Why It Repeats in Fleets

Because troubleshooting stops at the first replaceable item. Probe replacement is actioned; contamination discipline, heater trend monitoring, and tubing inspection are not. The failure chain — probe condition, heater performance, installation integrity, post-maintenance verification — is never managed as a single reliability loop. Each element lives in a different task card, a different shop, a different conversation.

› Air data reliability is as much a process-control problem as a component problem.

D. What the Industry Gets Wrong

Treating a repeat airspeed write-up as a single-component event. The moment the fault touches automation — autothrottle, yaw damper, flight envelope protection — it has already crossed system boundaries. Troubleshooting at the component level will not catch that.

E. What Effective Prevention Looks Like

Pairing routine pitot-static checks with a documented contamination-prevention protocol covering washing, waxing, painting, storage, and overnight line exposure. Tracking heater performance as a separate reliability metric. Treating repeat air data messages as automation-system signals, not instrument nuisances. For older fleets, applying the same reliability scrutiny to probe condition and tubing routing as to the ADC itself.

A. What Operators Experience

Erroneous or fluctuating height indications. Dispatch restrictions below certain weather minima. Landing-related limitations and flare mode anomalies. And the less obvious consequence: cross-system suppression. A radio altimeter anomaly can inhibit fault messages in other systems, reducing crew awareness of separate conditions. The RA fault is rarely just about landing.

B. What Actually Causes It

The LRU is often the last item to blame. Coaxial cable damage from age and vibration. Antenna seal degradation allowing moisture ingress. Connector bonding degradation. Susceptibility profiles — specific part-number and software combinations that are measurably more vulnerable to external interference. EASA's 2026 Safety Information Bulletin is explicit: certain Honeywell radio altimeter configurations showed a higher susceptibility profile, with manufacturer service bulletins available to reduce it through filter installation.

C. Why It Repeats in Fleets

Because maintenance organizations manage the LRU, not the installed chain. Antenna condition, coax routing, sealing integrity, filter currency, and susceptibility-by-configuration are managed in separate maintenance tasks — if managed at all. The unit gets removed and returned NFF. The underlying installation condition that caused the fault remains in service.

› A radio altimeter event can live in a cable, a filter, a susceptibility profile, or an RF environment. Treating it as a single-box issue is how repeat defects survive.

D. What the Industry Gets Wrong

Equating RA reliability with LRU swap rate. The failure chain is installed-system-wide. The maintenance response needs to match.

E. What Effective Prevention Looks Like

Inspection-led maintenance: antenna and cable condition, waterproofing, connectors, bonding, and coax routing reviewed systematically, not only on unscheduled removal. Filter retrofit incorporation where service bulletins are applicable. Configuration control by part number and software version. Trend monitoring of repetitive RA indications as an installation-integrity signal, not a random equipment quirk.

A. What Operators Experience

FMS position disagree. Route divergence. Loss of RNP approach capability. False TAWS or GPWS alerts triggered by corrupted position data. ADS-B surveillance anomalies. Time and date inconsistencies. In some cases, simultaneous GPS, FMC, and transponder malfunctions — all traceable to a single compromised position source. The failure appears systemic. Often it is environmental.

B. What Actually Causes It

GNSS jamming and spoofing are now live operational threats. EASA data shows that since early 2022, these events have been increasing in severity, intensity, and geographic scope. The important operational reality: the avionics hardware can pass every bench test and still deliver an operationally failed system when flying through a degraded RF environment. The equipment is functioning. The environment has changed the rules.

C. Why It Repeats in Fleets

GNSS is deeply integrated. The same degraded position source affects navigation, surveillance, terrain warning, and time-dependent functions simultaneously. Replacing a receiver does not address route-geography exposure. Spoofing is harder to recognize than jamming, which means events are frequently logged as "random system glitches" rather than as a known, repeatable threat pattern with geographic and fleet dimensions.

› GNSS disruption is now an avionics reliability problem even when the hardware passes bench test.

D. What the Industry Gets Wrong

Treating GNSS anomalies as isolated write-ups rather than fleet-exposure events with route geography. The incident is not one aircraft at one moment. It is a threat environment that affects all aircraft on that routing.

E. What Effective Prevention Looks Like

Route-risk intelligence: classifying disruption events by route segment, phase of flight, and system side-effects, then feeding that data into reliability and dispatch decision-making. Crew and MCC recognition standards for jamming versus spoofing behavior. Post-event engineering review that captures the systemic exposure, not just the individual write-up. Procedural downgrade paths for RNP loss that are trained, not improvised.

A. What Operators Experience

ADS-B FAIL indications. Non-performance events that only become visible through ATC feedback or Post-Flight Performance Reports. Poor target correlation. Traffic conflict alert anomalies. Access restrictions in ADS-B rule airspace. The aircraft appears healthy on the ramp. The transmitted data are not what they should be.

B. What Actually Causes It

Surveillance failures are frequently configuration failures wearing the mask of hardware faults. Software versions that don't meet airspace requirements. ICAO address errors from maintenance entry. Altitude-source mismatches between the transponder input and the ADS-B transmission. Antenna performance degradation from location, bonding, or physical condition. FAA guidance specifically identifies software currency, altitude-source consistency, and ICAO address accuracy as the leading ADS-B integrity risks.

C. Why It Repeats in Fleets

Transponders, GPS sources, and altitude encoders are routinely managed as separate ATA line items by separate shops. The operational failure — incorrect or incomplete surveillance data — is in the integrated output, not in any individual box. Nobody owns the output. Everybody owns their box.

› ADS-B failures are often data-integrity failures, not dead-transponder failures. That is why post-maintenance validation matters more than box condition.

D. What the Industry Gets Wrong

Closing a surveillance maintenance task when the hardware powers up. The hardware check is not the output check. Many non-performing emitters are technically operational at the LRU level.

E. What Effective Prevention Looks Like

A mandatory post-maintenance validation loop: configuration control audit, software currency check, altitude-source integrity verification, and Public ADS-B Performance Report review before the aircraft re-enters service after any maintenance affecting the surveillance chain. This is the gap between "maintenance completed" and "surveillance actually compliant."

A. What Operators Experience

Screens that blank for one flight and not the next. ECAM or EICAS messages that cannot be reproduced at the gate. Computer resets that clear the indication without resolving the fault. One-flight-only warnings that the shift cannot confirm. Troubleshooting that consumes labor without resolution. And the constant temptation to close the job card with "fault not reproduced" and move on.

B. What Actually Causes It

Intermittent wiring degradation. Backed-out connector pins. Solder joint weakness at connectors subject to vibration. Corrosion in high-humidity or coastal environments — which the FAA identifies as responsible for approximately 20% of avionics equipment failures. Insufficient equipment cooling creating thermal-triggered faults. The BITE message says display or computer. The actual fault is in the harness, the connector, the rack, or the thermal environment — none of which the BITE was designed to expose.

C. Why It Repeats in Fleets

Because conventional test setups find permanent faults reliably. Intermittent faults that only appear under flight-environment conditions — specific temperatures, humidity levels, vibration profiles, or phase-of-flight pressure — routinely escape bench testing. The unit ships back as NFF. It re-enters service with the latent condition intact. Airbus specifically warns about "rogue units" that cycle repeatedly through this pattern, accumulating short mean-time-between-removals without ever being resolved.

› No-fault-found is not a shop inconvenience. It is a fleet-availability tax that compounds with each NFF cycle.

D. What the Industry Gets Wrong

Accepting NFF as a resolution. A reset that clears the indication while leaving the failure latent does not fix the aircraft. It postpones the failure — and creates an additional risk that the latent condition will combine with a separate independent failure to produce a more serious operational consequence.

E. What Effective Prevention Looks Like

Daily monitoring of logbook entries, maintenance actions, resets, and repetitive messages — across both short and long time horizons. Fault isolation that continues even when the fault has not been confirmed on the ground, following OEM repeat-failure escalation procedures. Serial-number-level tracking of suspected rogue units. Cooling performance audits as a common-mode failure check. And the engineering authority to stop recycling the same suspect unit back into the network.

BELIEF VS. REALITY

The most persistent problems in avionics reliability management are not technical. They are conceptual. The following beliefs are common. None of them hold up under operational scrutiny.

ADVANCED RELIABILITY ENGINEERING

Generic maintenance tips do not reduce repeat avionics events. The operators that produce structurally better reliability outcomes apply a different set of governing principles — ones that treat avionics reliability as a system, operations, and supply chain problem simultaneously.

THE OFTEN-IGNORED MULTIPLIER

Engineering decisions and supply chain reality are not separate conversations in avionics reliability. They are the same conversation, and the industry is consistently late to recognize that.

IATA supply chain data shows the commercial aviation industry carrying approximately $3.1 billion in additional maintenance cost and $1.4 billion in incremental spare-parts inventory as a direct consequence of parts availability pressure and extended repair lead times. These are not macroeconomic abstractions. They show up as AOG events at outstations, extended ground times at line stations, and cancelled rotations when a dispatch-critical avionics LRU cannot be sourced in time.

For avionics specifically, three supply chain variables directly shape reliability outcomes. First, repair turnaround time: a unit that normally dispatches in 72 hours but takes 21 days because of shop queue depth converts a nuisance removal into a multi-week rotable gap. Second, pool access: exchange coverage on high-removal items means the difference between a same-day swap and an outstation AOG. Third, rotable lifecycle management: units aged out of cost-effective repair without replacement planning silently degrade pool availability before the shortage becomes visible.

Serious aftermarket strategy integrates these three variables into the reliability engineering process, not the procurement process. The question is not "do we have a spare?" The question is: "does our pool depth match the removal rate of our highest-risk items, and is our repair TAT fast enough that a removal event doesn't become a commercial event?"

The strongest operators answer that question proactively, using removal trend data to right-size exchange coverage and repair capacity before dispatch reliability is affected — not after.

PARTNER PERSPECTIVE

The five failure families described above share a common thread: they are each partially a supply chain problem. Resolution requires not just engineering competence but access to the right parts, the right repair capability, and the right turnaround performance — at the right moment in the operational cycle.

GFA operates at precisely this intersection. As an aviation aftermarket specialist, GFA's role is not to replace the airline's engineering program or the OEM's technical guidance. It is to ensure that when the engineering analysis points to a required LRU exchange, a rotable swap, or a repair escalation, the supply chain response matches the operational need.

That means maintaining exchange pools on high-removal avionics items with removal rates that justify the inventory investment. It means managing repair vendor relationships to protect TAT commitments on units in high-demand rotation. And it means providing the configuration traceability — part number, modification standard, software version — that ensures the replacement unit doesn't create a new problem when it enters service.

In practice, GFA operates as an enabler of reliability continuity: the component between the reliability engineer's analysis and the aircraft's return to service. Not a seller of parts. A partner in dispatch performance.

STRATEGIC PERSPECTIVE

The aviation industry has sophisticated tools for identifying avionics failures. What it consistently underinvests in is understanding them.

A reset that dispatches the aircraft today is not a reliability win. A spare that arrives 48 hours after the AOG call is not a supply chain success. An NFF return from the shop that re-enters service with the latent condition intact is not a maintenance closure. These are deferred failures with predictable futures.

The operators who produce structurally lower avionics-driven AOG rates and dispatch delay rates are not doing something exotic. They are managing repeat failure governance with the same discipline they apply to structural inspections. They are treating installation integrity as a reliability metric, not just a compliance requirement. They are connecting reliability data to rotable strategy before the shortage becomes an outstation crisis. And they are refusing to accept "fault not reproduced" as an engineering conclusion.

The industry will continue to generate expensive, repeat avionics events as long as it troubleshoots at the component level, trends at the event level, and procures at the transaction level. The shift that changes outcomes is treating reliability as a connected discipline — where the engineer's write-up, the shop's repair, and the supply chain's response are parts of one loop, not three separate processes.

That is what separates operators who manage avionics reliability from those who react to it.