The phrase "predictive MRO" gets used loosely enough that it has started to mean anything from "we look at the maintenance schedule a week out" to "our system generates 90-day demand forecasts from removal history." The gap between those two things is larger than it sounds, and the gap between having a forecast and actually running a predictive operation is larger still.
Over the past several months, we have worked closely with planners at a handful of early-access operators as they move from running purely reactive parts planning to working with a demand model. What we observed was not a smooth technology adoption curve. It was a series of workflow collisions, recalibrations, and gradual trust-building between the planner and the output. This article describes what that transition actually looks like.
What Reactive Planning Really Means
Reactive planning is the default state for most regional MRO operations, and it is not entirely unreasonable. The planner responds to work orders as they come in, raises purchase orders when stock drops to reorder points, and handles AOG events with emergency procurement. This approach is responsive by design: it does not commit budget until demand is certain.
The cost is that certainty in MRO comes late. By the time an unscheduled removal is generating a work order, the part needs to be there now, not in six weeks. If it is not in stock, the reactive system responds with expedite freight, AOG pool calls, and sometimes cannibalization from another tail. All of those responses are expensive and some create secondary disruptions.
The reactive planner is not bad at their job. They are working with the information available to them, which is backward-looking, and optimizing against the constraint that parts cost money to hold and demand is uncertain. The problem is not the planner's judgment; it is the information set they are operating on.
The First Thing Planners Told Us: They Did Not Trust the Output Immediately
Every planner we worked with went through a period of skepticism about the demand model output. This is healthy and expected. A planner who has been doing this job for six years has a mental model of which parts tend to fail on which tails, which vendors are reliable, and which component types are likely to cause problems after a heavy maintenance event. When a model tells them that a specific part has a 68% probability of removal in the next 60 days and they have never seen that part fail on their fleet in three years, their first instinct is not to believe the number.
In most of these cases, the model was drawing on cross-fleet patterns that the planner had not been exposed to. The part in question had a known failure mode on older variants of the same aircraft type that the planner's fleet had not yet reached in terms of age or cycles. The model was correct to flag it. But the planner had no way to verify that without either waiting to see if the removal happened or trusting the model's reasoning, which it did not explain clearly enough in early versions of the output.
What helped was making the model's inputs visible. When the planner could see that the demand flag was based on cross-fleet removal data from 30 similar fleets over four years, not just a formula applied to their own history, the flag became credible. Not automatically trusted, but worth acting on cautiously.
The Workflow Changes That Were Actually Hard
The part of the transition that no one fully anticipates is the change to how planners spend their time. In a reactive operation, the planner's day is driven by work order queue and AOG events. The agenda sets itself. In a predictive operation, the planner needs to make time for a forward-looking demand review that is not triggered by an immediate event. Nobody hands them a work order for it.
This sounds minor. In practice, it is one of the stickiest friction points. In one early-access pilot with a growing regional carrier in southern Europe operating nine aircraft, the planner we worked with found that the demand review was being consistently deferred because the day was full of reactive queue management. The forecast output sat unreviewed for two weeks before we agreed to build a Monday morning review step into their weekly procurement meeting. That scheduling change, not the technology, was what made the predictive model actually inform purchasing decisions.
The second hard change is the renegotiation of purchasing authority with management. Reactive procurement has a natural approval logic: something broke, we need the part, approve the purchase. Predictive procurement requires a planner to go to their manager and say: the model indicates there is a 72% chance we need this $3,400 LRU in the next 60 days and we do not have it in stock. Can I buy it now?
That conversation is harder. The part has not failed. There is no work order. The planner is asking to commit budget against a probability, not a certainty. Operations that have made this transition successfully have had to establish explicit policies for what probability threshold justifies a proactive purchase at what dollar level, and who approves it. Without that policy, the planner's judgment is correct but they have no authorization structure to act on it.
What Changes in the First 90 Days
Based on the early-access pilots, the first visible change in the first 90 days is not typically a reduction in AOG events. That takes longer. The first change is that planners start identifying parts that should not be in stock at current levels, and they can act on those identifications with confidence. The overstock review is faster and more defensible with a demand model backing it than with a planner's intuition alone. Budget freed from slow-moving inventory can be reallocated to parts the model is flagging as elevated risk.
By month two or three, planners typically start acting on a subset of the model's forward-demand flags, usually for parts they already had some personal intuition about. These early confirmations, where the model flags a risk, the planner acts on it, and the removal happens within the forecast window, build the trust that eventually extends to acting on flags for parts the planner had not independently suspected.
We are not going to claim that this transition is fast or frictionless. The operations that have gotten the most from the shift to predictive planning are the ones that treated it as a workflow project, not a software deployment. The model is a better information source than historical purchase records. What it cannot do is make purchasing decisions, build management trust in forward-based procurement, or carve out time in a planner's already full day for a demand review. Those are organizational questions that the technology does not answer by itself.
What Stays the Same
It is worth saying clearly: predictive planning does not replace the experienced planner's judgment. It supplements it. The planner who knows that tail N7 has been running hard since its last C-check, that a specific engine on the fleet has been on a watch list for combustion section findings, or that a vendor's lead time just increased by three weeks, is carrying information that the demand model does not have. That contextual judgment needs to be layered on top of the model output, not replaced by it.
The goal is not a planner who follows the model's recommendations automatically. It is a planner who has a better baseline demand signal and can apply their contextual knowledge to that signal rather than applying it to a static reorder point table that was last updated in 2022. Those are meaningfully different problems, and the second one is worth solving.
See Aerotrax on your own fleet data
30-day pilot on your removal history. CSV upload, no integration project required.
Request a pilot