Repairs and alterations
Embraer E-Jet repair approval data records review
This review checks that each repair and alteration recorded on an Embraer E-Jet rests on approved data and closes with a proper return-to-service entry. It is run by or for a party evaluating, transferring, or maintaining the tail who needs the repair history to be defensible. It covers the damage reports behind each repair, the disposition applied, the approved data supporting it, and the return-to-service entry that closed it. You receive a repair map for the airframe, a list of repairs whose approval basis is unsupported, and a source map from each repair to its substantiating data.
When this review is needed
- An E-Jet is being acquired and its repair history has to be defensible before pricing.
- A structural repair is recorded but the approved data behind it has never been checked.
- A repair carries recurring inspection requirements and their tracking needs confirming.
- The tail is transferring and each alteration has to reconcile to the receiving records.
The problem
A repair is only as sound as the data that approved it. A damage report leads to a repair with no traceable approved data, a disposition cites a manual reference that does not cover the actual damage, or a return-to-service entry closes a repair whose substantiation is missing. Repairs that seem settled on the airframe can leave the owner holding an alteration that cannot be supported when someone finally reads the basis.
What gets reviewed
- Damage reports linked to the repair each one drove
- Repair dispositions checked against the approved data cited
- Approved data traced for each repair and structural alteration
- Recurring inspection requirements arising from a repair and their tracking
- Return-to-service entries closing each repair against its substantiation
- Alterations reconciled to their approval basis for the destination register
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Send a representative, redacted record set and we will scope the review.
What gets validated
- Each repair cites approved data appropriate to the damage and its location
- The disposition applied matches the manual or approval reference it names
- Recurring inspections arising from a repair are recorded and on interval
- Every repair closes with a return-to-service entry supported by its data
- Structural alterations carry an approval basis the receiving register will accept
Evidence normally required
- The repair and alteration records with the repair map for the airframe
- Damage reports and repair dispositions on file
- Approved data and substantiation for each repair
- Return-to-service entries closing the repairs
- Any recurring inspection requirements the repairs impose
Common discrepancies
- A structural repair with no traceable approved data behind the disposition
- A disposition citing a manual reference that does not cover the actual damage
- A repair with a recurring inspection that was never entered into tracking
- A return-to-service entry closing a repair whose substantiation is missing
What is at stake
A repair without traceable approved data can force removal, re-substantiation, or re-work, which is far costlier than confirming the basis up front. A repair carrying an unrecorded recurring inspection can lapse into an open airworthiness item, and at transfer an unsupported alteration can stall acceptance until its basis is reconstructed.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Build the repair map
Assemble the recorded repairs and alterations and locate each on the airframe.
Trace the approval basis
Check each disposition against the approved data it cites and the damage it addressed.
Track the recurring items
Confirm any recurring inspection from a repair is recorded and on interval.
Report the exceptions
Deliver the repair map, the unsupported-basis list, and the source map.
What the buyer receives
- A repair map for the airframe with the approval status of each repair
- A list of repairs and alterations whose approval basis is unsupported
- A source map from each repair to its substantiating data
Who uses the output
- Engineering deciding how to treat a repair with no traceable basis
- Asset managers pricing the repair exposure on the airframe
- Records teams closing the repairs whose approval data is missing
How the work fits into the transaction or program
The repair history feeds the configuration and structural picture the rest of the file rests on, so this check sits alongside the AD and configuration reviews. What it surfaces drives the substantiation chase and the engineering calls that have to be settled before a transfer or a heavy check.
Aircraft-specific considerations
E-Jets in regional service accumulate repairs at a pace that reflects high cycle counts and frequent ground handling, so the repair map on a mid-life tail can be dense and layered. Cabin reconfigurations tied to operator changes add alterations whose approval basis has to be read against the current interior standard rather than the original one, which is where the repair history most often needs untangling.
Jurisdiction-specific considerations
A repair approved under one authority's data may need a bridging assessment before another authority accepts it, particularly for structural work approved by delegated authority. The review flags where a repair's approval basis is sound for the outgoing register but would need re-basing for the destination.
Regulatory limits
The review confirms whether each repair's approval basis and return-to-service are supported. It does not develop or approve repair data, issue a return to service, or make an airworthiness determination on any repair.
What this review does not cover
- Developing or approving new repair or alteration data
- Performing or re-performing any repair
- Any airworthiness determination on the repairs or the airframe
Specific to this review
- A disposition that names a manual reference not covering the actual damage is worse than a missing one, because it reads as approved until the reference is checked.
- Repairs carry recurring inspections that outlive the repair event, so an untracked one becomes an open item long after the work looks closed.
- Structural alterations approved by delegated authority are the ones most likely to need re-basing when the tail crosses registers.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
What if a repair has no traceable approved data?
It is flagged as unsupported and handed to engineering to decide whether an acceptable basis can be reconstructed or the repair has to be re-substantiated or removed. Confirming the basis before a transfer or heavy check is far cheaper than discovering the gap under time pressure.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Talk through the aircraft, records, evidence, deadline, and next useful step.