A320 family modifications
Airbus A320 family modification and STC status records review
This review checks that the Service Bulletin, STC, and modification status recorded for an Airbus A320 family aircraft is backed by approval data and correct effectivity. It is run for a lessor, operator, or manager evaluating or transferring an A320 family asset with an accumulated modification history. The work reconciles the modification status report against SB embodiment records, STC files, and configuration lists, confirming each change applies to the serial number and carries its approval. You receive a supported exception list, a source map from status line to approval, and a closure plan for the specific serial number.
When this review is needed
- A buyer needs the SB and STC embodiment status confirmed before pricing the configuration.
- An STC is claimed as embodied but its approval file has never been located.
- A modification was recorded against an effectivity that may not apply to this serial number.
- The aircraft is changing register and the modification approvals have to be re-checked for acceptance.
The problem
An A320 family aircraft accumulates Service Bulletins, STCs, and operator modifications across its life, and the status report that summarizes them is only as reliable as the approval data behind each line. An SB can show as embodied with no accomplishment record, an STC can be listed without its approval file, or a modification can be recorded against an effectivity that never applied to this serial number. The report reads clean until a buyer or a receiving authority asks for the basis behind a line.
What gets reviewed
- Service Bulletin embodiment reconciled to accomplishment records and effectivity
- STC files confirmed present with their approval for each claimed installation
- Modifications checked for the approval basis appropriate to the serial number
- Configuration lists reconciled to the embodied modification and STC status
- Effectivity on each change validated against the serial number and airframe history
- Superseded or reversed modifications reflected correctly in the status report
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 embodied SB traces to an accomplishment record with matching effectivity
- Every claimed STC has its approval file and installation evidence on hand
- Modifications carry approval data appropriate to the installation and register
- Recorded effectivity for each change applies to this serial number
- The configuration list reconciles with the embodied modification status
Evidence normally required
Common discrepancies
What is at stake
A modification without traceable approval can force removal or re-substantiation, and an SB shown embodied without evidence leaves the configuration status unsupported. On a register change, an STC valid under one authority may not be accepted by the other, and a modification recorded against the wrong effectivity means the configuration baseline is wrong before anything is built on it.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Pull the claimed status
Assemble the SB, STC, and modification status the report asserts for the serial number.
Trace approval and effectivity
Confirm each change carries approval data and applies to this tail.
Reconcile the configuration
Match the embodied status against the configuration list and airframe history.
List the exceptions
Flag modifications without traceable approval or correct effectivity and plan recovery.
What the buyer receives
- A supported exception list of modifications and SBs without traceable approval
- A source map from each status line to its approval and effectivity evidence
- A closure plan to recover the missing approval files or correct the status
Who uses the output
- Asset and acquisition teams pricing the configuration the records support
- Records teams assembling the modification evidence for the data room
- Continuing-airworthiness teams confirming embodiment for the receiving register
How the work fits into the transaction or program
The modification-status review sets the configuration position that AD applicability and equipment status depend on, so it feeds the configuration baseline directly. Its exception list drives recovery of the missing approval files while the modifying organizations are still reachable, and the reconciled status carries into the transaction or the register change the asset is heading into.
Aircraft-specific considerations
A320 family aircraft carry heavy modification histories driven by repeated cabin reconfigurations, connectivity and avionics upgrades, and operator-specific STCs, so the status report is long and the approval files are spread across several installing organizations. Effectivity is the frequent break, because a modification recorded against a family-level effectivity may not apply to a specific serial number, so the review validates each line against the tail rather than the family.
Jurisdiction-specific considerations
An A320 family aircraft moving between FAA and EASA registers carries modifications approved under one system that the other must accept, and an STC valid in one may need validation in the other. The review notes where each modification approval will need bilateral acceptance or re-validation for the receiving authority rather than assuming it carries across on its face.
Regulatory limits
The review confirms the recorded modification status is supported by approval data and correct effectivity. It does not approve a modification, grant or validate an STC, or determine that the installed configuration is airworthy.
What this review does not cover
- A physical configuration survey of the aircraft
- Developing, approving, or validating any modification or STC data
- Any airworthiness determination on the modified configuration
Specific to this review
- Effectivity is the most common failure point, because a real modification can be recorded against a serial number it never applied to.
- An SB marked embodied is only as good as the accomplishment record behind it, which is what a buyer will actually trace.
- An STC valid under the register it was installed on may still need validation for the register the aircraft 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). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Federal Aviation Administration. STC application process, certification basis, and continued airworthiness obligations of an STC holder.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
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.
Frequently asked questions
Does a status line marked embodied mean the modification is fully supported?
Not by itself. The line has to trace to an accomplishment record for an SB or an approval file for an STC, and the effectivity has to apply to this serial number. The review checks those behind each line, because an embodied marking without the evidence is what leaves the configuration status open at 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.