Aircraft are not interchangeable units, even within the same type certificate. A 12-year-old ATR 72-500 and a 4-year-old ATR 72-600 share a type designation but differ in avionics architecture, component generations, and accumulated fatigue exposure. Running them through the same demand model produces a blended forecast that is systematically wrong for both.
Fleet age distribution and variant mix are two of the most commonly underweighted variables in MRO parts planning. Planners tend to recognize the problem intuitively, but the systems they use often make it difficult to act on that intuition without significant manual segmentation work.
Why Age Distribution Matters for Removal Rates
Component removal rates are not constant across an aircraft's service life. Most failure-mode curves follow a pattern that reliability engineers know as the bathtub curve: an elevated removal rate early in service as components are broken in and infant defects surface, a relatively stable mid-life period, and a rising removal rate in older aircraft as wear-related failures accumulate.
For some components this curve is clear and well-documented in the manufacturer's reliability data. For others, especially avionics line replaceable units, the pattern is flatter and harder to separate from random in-service failures. The point is that a fleet with a mix of 3-year-old and 14-year-old aircraft will not have uniform removal rates across those aircraft, and the demand forecast needs to reflect that difference.
If your forecast engine is using a fleet-average removal rate, it is implicitly assuming that old and new aircraft fail components at the same frequency. That assumption gets more expensive as the age gap between fleet segments widens. Operators who have been adding young aircraft while keeping older ones in service for high-utilization routes face exactly this widening gap.
Variant Differences Go Beyond Part Numbers
When an operator runs two variants of the same aircraft type, the obvious difference is that some parts are not interchangeable. The less obvious difference is that removal patterns for shared parts can also diverge significantly.
Consider hydraulic system components on an aircraft type that went through a hydraulic architecture change between variants. Both variants might use the same hydraulic pump part number, but the pump on the newer variant may be running at different system pressures, cycling at different frequencies due to updated flight management logic, or benefiting from a revised ground cooling procedure that reduces thermal stress. The result can be meaningfully different removal rates for the same part across variants, even though the part number is identical.
A demand model that does not segment by variant will pool these removal events and produce an average that may not match either variant's actual failure rate. In practice, the planner ends up stocking for the average, running short on the variant that fails more often, and accumulating excess on the other.
A Concrete Example: Mixed-Vintage Regional Fleet
Consider a mid-continent regional carrier operating 22 aircraft: 8 Bombardier Q400 aircraft in the 10 to 14-year age range and 14 in the 3 to 7-year range. The older aircraft are on thinner routes with lower daily utilization. The younger aircraft are on the densest network segments, flying two to three additional block hours per day.
For a particular air data system component, the older aircraft group was generating unscheduled removals at roughly twice the rate of the younger group, per flight hour. But because the older aircraft were flying fewer hours per month, their absolute removal count was lower. A simple fleet-level MTBR calculation weighted by removals rather than hours gave the impression that the component was healthier in older aircraft than it actually was, per flight hour flown.
The planning system was underestimating future demand from the older segment because it could not see the per-hour rate difference, only the count. When the carrier planned to redeploy the older aircraft to higher-utilization routes during a summer capacity push, the demand spike was larger than the forecast predicted. That is the kind of miscalculation that produces AOG events.
Segmenting Demand by Age Cohort and Variant
Addressing this requires the planning system to maintain removal history at the tail-number level and to carry metadata about each aircraft's age cohort and variant line. Most MRO systems do carry this information, but the demand model sitting on top of those records often aggregates it away before the forecast is generated.
When we build demand models from an operator's removal history, we segment by variant first, then by age cohort within each variant. For each segment, we compute separate removal rates, separate confidence intervals, and separate reorder parameters. The fleet-level number we report is an aggregation of those segmented forecasts, not a starting average.
This approach requires more data quality discipline. Tail-number records need to be clean. Age fields need to be populated consistently. Variant classifications need to be applied uniformly rather than using informal shorthand that varies between maintenance departments. None of that is dramatic data engineering, but it does require a deliberate setup step.
The Forecasting Cost of Assuming Homogeneity
We should be direct about the trade-off. Fleet-level forecasting with uniform assumptions is faster to build and simpler to explain to a CFO. Segmented forecasting requires more setup time, more data governance, and more explanation when the forecast for one segment diverges sharply from another.
The cost of the simpler approach is paid in parts. Excess stock in the young, healthy aircraft segments covers for the shortfalls in the older, higher-removal segments. At fleet sizes below roughly 15 aircraft this sometimes works as an accidental buffer. At larger fleets, or fleets with wider age and variant spread, the cross-subsidization breaks down and you end up with both excess and shortage simultaneously, which is the worst outcome from a capital efficiency perspective.
Forecasting a heterogeneous fleet as if it were homogeneous is not a conservative planning choice. It is a choice to be wrong in a predictable direction, and to discover the error after the AOG, not before it.
See Aerotrax on your own fleet data
30-day pilot on your removal history. CSV upload, no integration project required.
Request a pilot