A320 family repairs
Airbus A320 family repair and alteration records review
This review checks that every repair and alteration on an Airbus A320 family aircraft is backed by approved data and mapped to a location on the airframe. It is run for a lessor, operator, or manager evaluating, transferring, or holding an A320 family asset. The work reconciles the repair map, damage reports, and dispositions against the substantiation each change relied on, then confirms the return-to-service entry follows. You receive a supported exception list, a source map tying each repair to its approval, and a closure plan scoped to the specific serial number.
When this review is needed
- A buyer is pricing an A320 family tail and needs each recorded repair backed by traceable approval data.
- A lessor is preparing redelivery and the repair map has to reconcile to the airframe before handback.
- A structural repair has accumulated over several operators and no one has reconciled the dispositions recently.
- An alteration is claimed in the file but the approval basis behind it has never been checked.
The problem
Repairs collect on an A320 family airframe across years of high-cycle service, and the paper behind them scatters across damage reports, dispositions, and shop paperwork held by whoever did the work. A repair can sit on the aircraft with a clean sign-off but no retrievable approved data, or be recorded against a map location that does not match the structure. The gap stays quiet until a buyer or an auditor asks for the basis.
What gets reviewed
- Every recorded repair matched to a location on the airframe repair map
- Approved or acceptable data confirmed behind each repair and alteration
- Damage reports reconciled to the disposition that closed them
- Alterations checked for the approval basis appropriate to the installation and register
- Return-to-service entries confirmed to follow each closed repair
- Structural repair manual references validated against the revision in force at the time
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 on the map traces to a damage report and an approved-data reference
- The location recorded for a repair matches the structure it was applied to
- Alteration approvals suit the jurisdiction the aircraft was registered in when the work was done
- Dispositions that reference a repair manual cite a revision that was current at accomplishment
- The return-to-service entry for each repair is present and consistent with the disposition
Evidence normally required
- The aircraft repair map or structural repair drawing for the serial number
- Damage reports, dispositions, and the approved data referenced by each
- Task cards and work orders covering the repair accomplishment
- The alteration and modification records that touch structure
- Airframe logbooks showing the return-to-service entries
Common discrepancies
- A repair on the map with a sign-off but no retrievable approved data behind it
- A disposition referencing a repair manual revision that was not current when the work closed
- A recorded repair location that does not reconcile with the airframe structure
- An alteration whose approval basis suits a different register than the one it was flown under
What is at stake
A repair without traceable approval data can force removal, re-substantiation, or a conservative assumption the current owner pays for at the next transaction. Left unaddressed, an unsupported alteration undermines the configuration status built on top of it, and the cost of proving the basis rises as the shops and engineers who held the data move on.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the repair map
Pull the recorded repairs and alterations and locate each one on the airframe map for the serial number.
Trace the basis
Confirm approved or acceptable data behind each repair and check the disposition that closed the damage report.
Reconcile to structure
Verify each repair location and manual reference against the airframe and the revision in force at accomplishment.
List the exceptions
Flag repairs without a traceable basis and sequence them into a closure plan.
What the buyer receives
- A supported exception list naming each repair without a traceable basis
- A source map tying every repair on the airframe to its approval evidence
- A closure plan sequencing the unsupported items by recoverability and cost
Who uses the output
- Asset managers pricing the repair position on a specific A320 family tail
- Records teams assembling the repair evidence a counterparty will demand
- Engineering deciding how to treat a repair whose approved data cannot be found
How the work fits into the transaction or program
The repair-approval review feeds the configuration baseline and any structural repair review that follows, because both rest on the map being reconciled first. Its exception list drives remediation while the current holder still has access to the shops and engineers who did the work, and the source map carries into the data room the transaction depends on.
Aircraft-specific considerations
A320 family airframes accumulate repairs quickly under short-sector, high-cycle operation, and many tails have passed through cabin reconfigurations and connectivity modifications that add alterations to the structure. Landing-gear and pressurized-fuselage repairs are the most frequent, so the review weights the map toward those areas and toward the transitions between operators where a disposition tends to lose its approved data.
Jurisdiction-specific considerations
An A320 family aircraft that has flown under both FAA and EASA registers may carry repairs approved under one system and alterations under the other, so the review notes where a repair basis will need bilateral acceptance or rework for the receiving register rather than assuming a single approval path.
Regulatory limits
The review evaluates whether each repair and alteration is supported by traceable approval data. It does not approve a repair, issue or restore any authority acceptance, or determine that the airframe is in an airworthy condition.
What this review does not cover
- Physical inspection or survey of the repaired structure
- Developing or approving new repair or alteration data
- Any airworthiness determination on the repaired aircraft
Specific to this review
- The approved data behind a structural repair is the part most likely to be missing, because it often stayed with the shop rather than the airframe file.
- A repair recorded against the wrong map location reads as compliant until the structure it names is inspected against the record.
- On a tail that has crossed registers, a repair valid under the register it was done on may still need acceptance for the register it will fly under next.
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
Does this confirm the repairs are physically present as recorded?
The review works from the records and the approval data, so it confirms each repair is mapped, substantiated, and returned to service on paper. A physical survey of the repaired structure is a separate step and is often run alongside it during a transaction.
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.