Configuration records
Aircraft modification status records review
A modification status review is for lessors, airlines, and acquisition teams who need to know that the aircraft's recorded modification standard is real and supported. It runs before a transaction, a return, or a configuration baseline reset. It reconciles each modification against its embodiment evidence, its approval basis, and the effectivity that makes it applicable, and it checks that the recorded standard matches the configuration claimed. You receive a reconciled mod-status matrix, a register of unsupported or open mods, and the evidence needed to close them.
When this review is needed
- A modification status list is being relied on for a transaction and its embodiment evidence has not been checked.
- A return condition specifies a modification standard and the recorded status has to be proven against it.
- A buyer needs the optional and mandatory modifications mapped to what is actually embodied and approved.
- A configuration baseline is being reset and the mod history feeding it has to be reconciled first.
The problem
A modification status list is easy to generate and hard to trust. It records that a mod is incorporated, but the embodiment record, the approval basis, and the effectivity that justify the entry are spread across work orders, supplements, and prior operators. A mod marked embodied with no embodiment evidence, or one applied outside its effectivity, leaves the configuration standard claimed on the list unsupported by the records behind it.
What gets reviewed
- Each modification on the status list and its mandatory or optional classification
- Embodiment evidence tying the mod to the specific aircraft and the work that incorporated it
- The approval basis for each mod, whether a manufacturer change, an SB, or a separate approval
- Effectivity, so each mod applies to the serial number and configuration recorded
- Partial or superseded embodiments and the standard they leave the aircraft at
- Consistency between the recorded mod standard and the configuration baseline claimed
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 modification marked embodied is supported by embodiment evidence on this aircraft
- Every modification cites an approval basis appropriate to the change it makes
- Recorded mods fall within the effectivity for the aircraft serial and configuration
- Partial or superseded embodiments are reflected accurately rather than shown as complete
- Service Bulletin embodiments reconcile with the work orders that recorded them
- The recorded mod standard is consistent with the configuration baseline the aircraft is held against
Evidence normally required
- The modification status list with mandatory and optional classification
- Embodiment records and the work orders that incorporated each mod
- Approval references for each modification
- Service Bulletin status and effectivity data
- The configuration baseline the aircraft is tracked against
- Supplements and prior-operator records covering earlier embodiments
Common discrepancies
- A modification marked embodied with no embodiment evidence on the aircraft
- A mod recorded against a serial number that falls outside its effectivity
- An approval basis missing or inappropriate for the change the mod makes
- A partial embodiment shown on the list as a complete one
- An SB embodiment that does not reconcile with the work order claimed to have done it
- A recorded mod standard that disagrees with the configuration baseline of record
What is at stake
An unsupported modification status can mean the aircraft is not at the standard the list and the deal assume. A mod may need re-evidencing or re-embodiment, a configuration mismatch can block a return, and a status accepted without its embodiment evidence transfers the cost of resolving it to the new owner.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the list
Take the modification status list and classify each mod as mandatory or optional and as embodied or open.
Trace embodiment
Match each embodied mod to its embodiment record, approval basis, and effectivity on this aircraft.
Reconcile the standard
Compare the recorded mod standard against the configuration baseline the aircraft is held against.
Register and close
Record unsupported, partial, or out-of-effectivity mods and recommend how to resolve each.
What the buyer receives
- A reconciled mod-status matrix mapping each mod to its embodiment and approval evidence
- A register of unsupported, partial, or out-of-effectivity mods with the record each touches
- A recommended path to re-evidence, re-embody, or correctly record each open item
Who uses the output
- Records teams correcting the mod status list before a transaction or return
- Continuing-airworthiness staff confirming the configuration standard of record
- Asset and acquisition teams pricing configuration risk
How the work fits into the transaction or program
The review turns a modification list into a supported configuration standard, so mod gaps surface before a return or a baseline reset relies on them. It pairs with an STC status review for non-manufacturer changes and feeds the configuration baseline the asset is held against.
Aircraft-specific considerations
Modification effectivity is driven by serial number, build standard, and prior embodiments, so two aircraft of the same type can carry different applicable mods. The review reads effectivity against the specific tail rather than assuming a fleet-wide modification standard.
Jurisdiction-specific considerations
A modification approved under one authority is not automatically valid under another, and a change accepted on import may rest on a bilateral arrangement rather than a fresh approval. The review records the approval basis each modification relies on for the authority the aircraft operates under.
Regulatory limits
The review confirms that the recorded modification status is supported, internally consistent, and traceable. It does not approve a modification, validate a foreign approval, or determine the airworthiness of the modified configuration.
What this review does not cover
- Engineering approval or validation of any modification
- Physical configuration inspection of the aircraft
- Any airworthiness determination on the modified configuration
Specific to this review
- A modification status list states embodiment, while the embodiment evidence proves it; the two are reconciled separately because a list entry can stand with nothing behind it.
- Effectivity is part of the check, since a mod recorded on a serial number outside its effectivity is unsupported even when embodiment work appears to exist.
- Partial and superseded embodiments are a distinct finding class, because a list often shows them as complete when the aircraft sits at an intermediate standard.
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. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Does a modification status list prove the aircraft's configuration?
It claims a configuration; it does not prove one. The review reconciles each entry against embodiment, approval, and effectivity evidence so the recorded standard actually matches what the records support.
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.
Walk through your situation with an engineer who has done this work.