Configuration baseline gap
Incomplete aircraft configuration baseline in the records
An incomplete configuration baseline means the documented statement of what is fitted to the aircraft does not capture every modification, repair, and serialized component actually installed. It is a problem for lessors, airlines, and MROs at induction, transition, or transaction diligence. The check reconciles the baseline against the modification list, the fitted components, and the embodiment evidence behind them. You receive a list of items missing from or wrong in the baseline and the path to correct it.
When this review is needed
- An aircraft is inducted and the incoming operator needs a baseline that reflects everything fitted.
- A transition requires a configuration statement the receiving authority and operator can accept.
- Diligence finds modifications or components in the records that the baseline does not list.
The problem
The configuration baseline is the reference everything else is checked against, so a baseline that misses a modification or a fitted component quietly distorts every downstream status. Changes embodied late, repairs recorded only in a work pack, and components swapped without updating the master list all leave the baseline lagging the aircraft. Once the baseline is wrong, the status lists built on it inherit the error.
What gets reviewed
- The configuration baseline as the master statement of the as-fitted aircraft
- Each modification and repair against its embodiment evidence
- Serialized components fitted against the baseline's record of them
- Items embodied or swapped without a baseline update
- Downstream status lists that depend on the baseline
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
- Every embodied modification and repair appears in the baseline
- Each serialized component fitted is reflected in the baseline record
- The baseline matches the embodiment evidence, not only the work-pack summary
- Changes made late in service are captured rather than left off the master list
- Status lists built on the baseline reconcile with the corrected configuration
Evidence normally required
- The current configuration baseline or master configuration record
- Modification and repair status list with embodiment evidence
- Serialized component fitment and status records
- Work packages for changes embodied in recent visits
Common discrepancies
- A modification embodied in service but absent from the baseline
- A serialized component fitted that the baseline does not record
- A repair captured only in a work pack and never added to the master list
- A baseline that disagrees with the embodiment evidence behind a change
What is at stake
An incomplete baseline can hide a modification that drives recurring tasks or an effectivity change, so the maintenance program and AD status built on it are wrong too. Correcting it can cascade into re-checking dependent records, and at a transition an unreconciled baseline blocks acceptance of the configuration the asset is delivered on.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Read the master list
Take the current configuration baseline as the stated as-fitted record for the airframe.
Reconcile to evidence
Compare it against the modification list, serialized fitments, and the embodiment evidence behind each change.
Capture the omissions
Identify changes embodied late, repairs left in work packs, and swaps that never reached the master list.
Correct and cascade
Record the corrected configuration and list the downstream status lists the correction re-opens.
What the buyer receives
- A register of items missing from or incorrect in the configuration baseline
- The corrected as-fitted configuration with its embodiment evidence shown
- A list of downstream status lists affected by the correction
Who uses the output
- Engineering establishing the as-fitted configuration the rest of the records rest on
- Continuing-airworthiness staff re-checking the status lists the correction touches
- Asset teams delivering a configuration the receiving party can accept
How the work fits into the transaction or program
The review treats the baseline as the foundation the rest of the records depend on, so a configuration error is corrected before the status lists built on it are trusted. It feeds the corrected baseline and the discrepancy register a transition relies on.
Aircraft-specific considerations
How a baseline is structured tracks the type's modification economy. A widebody carrying cabin, galley, and connectivity changes across multiple cabin reconfigurations holds a deeper modification layer than a freighter conversion of the same family, so the reconciliation is scoped to the change history the individual airframe actually accumulated.
Jurisdiction-specific considerations
An accepted configuration in one authority is read against the registry the aircraft is moving to. A modification valid in the prior system may need a validated or accepted basis before the receiving authority accepts the baseline.
Regulatory limits
The review confirms whether the configuration baseline is complete and consistent with the embodiment evidence. It does not approve a configuration, validate a modification, or make an airworthiness determination.
What this review does not cover
- Approving a configuration or validating a modification
- Physical survey of the aircraft to confirm what is fitted
- Issuing any airworthiness determination on the corrected baseline
Specific to this review
- The baseline is the reference every status list is checked against, so a single missing modification can propagate error into the maintenance program and AD status alike.
- A change captured only in a work pack is treated as not yet in the baseline, since the master list and the embodiment evidence are reconciled as separate sources.
- Correcting the baseline can re-open dependent records, because effectivity and recurring tasks often hang off the very change that was missing.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
Frequently asked questions
Why correct the baseline before checking the status lists?
The status lists are built on the baseline, so an error in the baseline propagates into the maintenance program and AD status that depend on it. Correcting the baseline first means the dependent records are reconciled against an accurate as-fitted configuration.
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.