Configuration & modification status
Aircraft configuration-baseline validation
Configuration-baseline validation confirms that the modifications, repairs, and equipment the records claim are installed match what is approved and what is physically fitted. It is used before a transaction, after a heavy check, or when modification history has accumulated across operators. It covers modification and effectivity status, the approval basis for each change, and the link between recorded configuration and the type design. You receive a validated configuration baseline, a list of unsupported or unrecorded changes, and the approval evidence behind each modification.
When this review is needed
- Modification history has built up across several operators and no one has reconciled it recently.
- A buyer needs the configuration confirmed before pricing the asset.
- A heavy check changed the configuration and the records have to catch up to the airframe.
- A modification is claimed but the approval basis behind it has never been checked.
The problem
Configuration drifts as modifications, repairs, and equipment changes accumulate, and the records that should track them lag behind the airframe. A modification embodied without its approval data, or recorded against the wrong effectivity, leaves the baseline saying one thing while the aircraft is another. That gap surfaces at the worst time, during a transaction or an audit.
What gets reviewed
- Embodied modification and STC status against the recorded effectivity for this serial number
- The approval basis and substantiation data for each embodied change
- Service Bulletin embodiment recorded with the correct revision and effectivity
- Repairs reconciled to approved data and their effect on configuration
- Recorded configuration mapped to the type design and approved modifications
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 claimed modification carries approval data appropriate to the installation and jurisdiction
- Effectivity on embodied changes matches the serial number and the airframe history
- Recorded configuration reconciles with the type design and the approved modification list
- Repairs that alter configuration are supported by approved or acceptable data
- Equipment changes are recorded as modifications where the type requires it rather than treated as routine swaps
Evidence normally required
- The modification and STC status list with effectivity
- Approval and substantiation data for embodied changes
- Service Bulletin embodiment records
- Type design and configuration reference for the aircraft
Common discrepancies
- A modification recorded against effectivity that does not apply to this serial number
- An embodied change with no traceable approval or substantiation data
- A repair that altered configuration without an approved-data reference
- Configuration records that lag a change made during a recent heavy check
What is at stake
A configuration baseline that does not match the airframe undermines every status built on top of it. A modification without traceable approval data can force removal or re-substantiation, and an unrecorded change can stall acceptance until the basis is reconstructed.
How the work runs
Pull the claimed configuration
Assemble the modification, STC, and SB status the records assert for the serial number.
Check effectivity and basis
Confirm each change applies to this aircraft and carries appropriate approval data.
Reconcile to type design
Map the recorded configuration against the type design and approved modifications.
List the exceptions
Flag unsupported, mis-recorded, or unrecorded changes with the evidence behind each.
What the buyer receives
- A validated configuration baseline tied to the type design
- A list of unsupported, mis-recorded, or unrecorded changes
- The approval evidence assembled per modification
Who uses the output
- Records teams setting a configuration baseline the rest of the file rests on
- Engineering deciding how to treat a modification with no traceable basis
- Asset and acquisition teams pricing the configuration the records actually support
How the work fits into the transaction or program
Validation establishes the configuration baseline that AD applicability, equipment status, and later modification tracking all depend on. It is run before a transaction or right after a heavy check so the records catch up to the airframe before anything else is built on them.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Aircraft-specific considerations
Modification and effectivity structure differ by aircraft family, so the validation is scoped to the specific type and serial number rather than applied uniformly. Equipment changes that are routine on one family can be a tracked modification on another, which changes where the records most often drift.
Regulatory limits
Validation confirms the recorded configuration is internally consistent and supported by approval data. It does not approve a modification, grant an STC, or determine that the aircraft is in an airworthy configuration.
What this review does not cover
- A physical configuration survey of the aircraft
- Developing or approving new modification or repair data
- Any airworthiness determination on the installed configuration
Specific to this review
- Effectivity is where configuration records most often break: a modification can be real but recorded against a serial number it does not apply to.
- A modification without traceable approval data may have to be removed or re-substantiated, which is far more expensive than confirming the basis up front.
- Configuration drift accumulates silently across operators because each change is small and the records lag the airframe.
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.
Frequently asked questions
Does this confirm the aircraft is physically in the recorded configuration?
The validation works from the records and the approval basis. It confirms the recorded configuration is internally consistent and supported. A physical configuration survey is complementary and is often run alongside it.
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.