Maintenance Trends & Industry Insights
Overhaul or Repair? The Records Decide, Not the Price
Overhaul is not a better grade of component repair. It is a defined records term with its own test requirement. Here is what changes, and when each applies.
.png){kind=logo}
Overhaul is not a better grade of component repair. It is a defined records term with its own test requirement. Here is what changes, and when each applies.
An overhaul is not a better repair. In component maintenance it is a specific claim about what was done to a unit and how it was tested, and a claim anyone is only allowed to make in the maintenance record once six things have happened, using methods acceptable to the Administrator: the unit was disassembled, cleaned, inspected, repaired as necessary and reassembled, and then tested against approved technical data. A repair is not a smaller version of that. It is a different scope, with a different entry, a different cost and a different lead time, and choosing between them is a scoping decision made against the condition of the unit in front of you, not a decision about how much quality you are willing to buy.
That distinction gets lost constantly, because "overhauled" reads like a grade. Procurement hears premium. Planning hears slow. Neither is what the word means, and the gap between what it sounds like and what it obliges is where operators overspend on scope they did not need and undersell assets they actually restored.
The condition of the unit and the work scope the approved data supports. If the finding is discrete and the data covers a repair for it, a repair returns the component to an airworthy condition without touching what is still within limits. If the unit is at or near its published intervals, or if the findings are distributed rather than local, the scope becomes an overhaul, because only the full sequence ending in an approved test lets anyone write that word in the record. Whether the interval clock resets is a separate question, answered by the applicable maintenance program rather than by the recording rule.
Cost and turnaround follow that decision. They do not drive it.
This is the part that rarely makes it into the conversation, and it is the part that settles it. Under the rule on records of overhaul and rebuilding,no person may describe a component part as overhauled in a required maintenance entry unless, using methods, techniques and practices acceptable to the Administrator, it has been disassembled, cleaned, inspected, repaired as necessary and reassembled, and it has been tested in accordance with approved standards and technical data, or with current standards and technical data acceptable to the Administrator, developed and documented by the holder of the type certificate, a supplemental type certificate, or a part approval.
Two things follow from that.
First, overhaul is a records term with a test requirement attached. A shop does not arrive at it by doing more work. It arrives there by completing that sequence and testing to approved data.
Second, the same rule defines a third term that is almost never used correctly. A component may only be described as rebuilt when it has been through the same sequence and tested to the same tolerances and limits as a new item, using new parts or used parts that conform to new-part tolerances or to approved oversized or undersized dimensions. Rebuilt is the "as new" claim. Overhaul is not.
The right-hand column is the one buyers underweight. Two shops can do comparable physical work and produce different entries, and the entry is what travels with the unit for the rest of its life.
Treating overhaul as the premium tier produces a predictable and expensive habit: the default overhaul, where a unit is stripped and repopulated regardless of what the inspection actually found. It feels like risk reduction. What it buys is material spend on parts that were serviceable, plus the turnaround time to remove and replace them.
The opposite habit costs just as much. Repairing a unit that is already at its interval, or scoping narrowly around a finding that is a symptom of something distributed, puts the component back on the aircraft with a clock that was never reset and a condition that was never fully characterized. It comes off again.
Neither error is a quality failure. Both are scoping failures, and scoping is an engineering judgement made at induction against the findings, the maintenance program and what the approved data allows. Where that data does not cover the repair an operator needs, the route runs through approved repair data developed by a designated engineering representative, which is a separate question and worth understanding on its own terms.
Every scope ends in paperwork, and the paperwork is the asset. Whoever performs the work must make an entry in the maintenance record, and the rule on the content and form of maintenance records sets out what that entry has to contain: a description of the work performed and the date it was completed, among other items. Alongside that entry, a component released by an approved organization is normally accompanied by an authorized release certificate, such as FAA Form 8130-3 or EASA Form 1, depending on the approvals involved.
That entry is what the next operator, the next lessor and the next appraiser will read. A repair entry and an overhaul entry describe different things about the same part number, and they carry different weight at redelivery, at lease return and at sale. This is the argument for deciding scope deliberately rather than by default: the decision is not only about this shop visit, it is about what the component's documented history (https://www.apas1.com/blog-posts/mro-components-lifecycle-induction-testing-release)says about it for the rest of its service life.
Three things decide the answer, and all three are knowable before the unit ships.
Where it sits against its intervals. If the unit is close, an overhaul that resets the clock may cost less over the next two years than a repair followed by an unscheduled removal.
What the findings look like. A discrete, local finding is a repair candidate. Distributed wear is not.
What the record needs to say. If the asset is approaching lease return or sale, the entry matters as much as the work.
Those are the three questions worth putting to a shop at induction, and they are the reason component-level work is scoped in conversation rather than ordered from a menu. On a landing gear, where intervals are long and the record is scrutinized closely, the same logic plays out with more money attached: the reasoning behind a landing gear overhaul is this decision at a larger scale.
Is an overhaul the same as a repair? No. A repair addresses a documented finding. An overhaul is a complete disassembly, cleaning, inspection, repair as necessary, reassembly and test against approved technical data, and only then may the unit be described as overhauled in the maintenance record.
Does an overhaul make a component as good as new? Not by definition. The term for restoration to new tolerances and limits is rebuilt, and it carries its own requirement: testing to the same tolerances and limits as a new item, using new parts or parts conforming to new-part or approved oversized and undersized dimensions.
Does a repair reset the maintenance interval? Generally no. Interval resets follow the scope defined in the applicable maintenance program and data. A repair addressing a discrete finding usually leaves the existing clock running.
Who decides whether a component needs a repair or an overhaul? Engineering judgement at induction, against the findings, the applicable Component Maintenance Manual and the operator's maintenance program, not a price list.
What documentation comes back with the component? A maintenance record entry describing the work performed and its completion date, which is what the recording rule requires. A component released by an approved organization is normally accompanied as well by an authorized release certificate, such as FAA Form8130-3 or EASA Form 1, depending on the approvals involved.
