A single AOG at a remote station can cost $30,000 to well over $100,000. For a narrowbody stranded at a spoke on Friday evening, the bill may include a replacement aircraft or passenger ground transport, premium parts if the required component is unavailable, overtime for the dispatch team recovering the schedule, and possibly a hotel for a crew that misses its connection. Duration and the airline's exposure determine the final direct and indirect cost.
The more useful question is which AOGs could have been prevented, and when the available data first exposed them.
The maintenance record pattern before an AOG
A retrospective review of AOGs usually finds the same structure: deferred defects, components nearing interval limits, and maintenance visits that passed their target dates. None is unusual alone. Fleets carry open deferrals, near-limit components are normal, and schedules slip.
Risk rises when those conditions converge on one aircraft at one time. A tail with three open CDL items, a hydraulic actuator at 94% of its TBO, and an A-check delayed 10 days by a hangar conflict presents a different risk from that same tail after a clean recent check with one open item. Most MRO systems contain these data points. Few setups proactively expose their combination.
Where planning systems fall short
Typical MRO software records discrete events: a work order opened, a component replaced, or an AD complied with. Mature MRO systems generally handle this essential record-keeping well. They are not built to continuously assess fleet-wide risk, match maintenance status to the future flight schedule, and tell a planner when a particular tail's factor combination needs attention this week.
The flight schedule sits in flight operations systems, while maintenance state sits in maintenance systems. The former lacks component history and compliance records; the latter lacks the flight schedule. Preventable AOGs often emerge in that disconnect. A planner may know a check is due without seeing that next week's rotation leaves the aircraft at a remote station, without hangar access, for 11 days before the compliance window closes.
The issue is not a need for a more powerful tool. It is integration: the information exists, but resides in two systems that do not automatically communicate.
What acting early looks like
Consider a common growing regional operation: an 18-aircraft turboprop fleet serving hub-spoke and point-to-point routes, with maintenance based at two locations. One aircraft has 11 calendar days left on a deferral. Its schedule keeps it away from both bases for the first 8 days. A planner tracking 900 line items in a spreadsheet may miss the conflict until the aircraft is away and the window is nearly closed.
A system that combines maintenance records with flight rotations can flag this at the first visible point, eight weeks out while the schedule is set. The planner sees the conflict during review and has two choices: resolve the deferral before departure, or modify the rotation to stop at a maintenance base. The decision happens while there is time to act, not merely react.
Tracking AOG reduction
The clearest improvement measure is the share of planned versus unplanned maintenance groundings. A fleet with 85% of groundings planned on the maintenance schedule has a substantially different risk profile from one with only 55% planned, even if maintenance volume is similar. Cost and schedule disruption cluster in the unplanned share.
Other useful measures include AOG parts purchases, expedited and premium-priced, compared with standard planned procurement; mean time between unplanned groundings per aircraft; and the share of visits whose work package was complete and parts confirmed before hangar entry. Each points to a different breakdown between planning and execution.
Better scheduling does not eliminate AOGs. In-service failures, bird strikes, and ground damage occur regardless of schedule quality. Planning can affect events that were moving toward an AOG for weeks but remained unnoticed until the deadline was immediate. Close review of unplanned grounding history often shows this group is larger than operators expect.
The data integration issue operators face
Operators we have worked with that report the lowest unplanned AOG rates share one structural trait: planners can see maintenance state and flight schedule together. Some built custom tooling over years; others use disciplined weekly reconciliation meetings. The shared factor is not the tool, but linking the two data sources.
An operator assessing its current process should ask whether it would catch this case: a tail nearing the end of a deferral window scheduled away from maintenance bases for most of that period. If detection depends on manually comparing the MRO system with a flight schedule spreadsheet, it depends on the planner remembering. That works when conditions are calm. During a busy week, this is where items are missed.
Scheduling tools serve a larger purpose: making high-risk combinations appear automatically, not when the window closes.