Configuration baselines
Delivery and redelivery binder review inside a modification-baseline source file
This review tests the delivery and redelivery binder section of a modification-baseline source file against the evidence that is supposed to sit behind it. A records specialist reads the binder index line by line and asks whether each listed record is present, applicable to the serial number, and supported by SB compliance records, STC files, equipment lists, and embodiment evidence. It is typically commissioned while a configuration baseline is being built or defended ahead of a transition. What comes back is an exception list telling the configuration manager which binder entries stand on source evidence and which do not.
When this review is needed
- A configuration baseline is being rebuilt and the binder from the last transition is the main input.
- A lease return is approaching and nobody has checked the binder index against source records since delivery.
- An STC or major modification was embodied mid-lease and the binder may never have picked it up.
- Two copies of the binder circulate with different contents and the team cannot say which reflects the aircraft.
The problem
Redelivery binders get assembled in the final weeks of a transition, under deadline, by whoever is available. Years later the same binder is treated as the authoritative account of the aircraft's configuration. The index says one thing, the section behind the tab holds something else, and every modification embodied since sits in the operator's system without ever reaching the binder. A configuration manager building a baseline on that foundation inherits every one of those silent gaps.
What gets reviewed
- Binder index entries compared one for one against the documents actually filed in each section
- SB and modification entries checked against compliance records and embodiment evidence
- STC entries traced into the STC file, including amended master drawing lists where applicable
- Equipment list entries reconciled with effectivity notes for this serial number
- Configuration-control log cross-checked for changes the binder never absorbed
- Version control across duplicate or partial copies of the binder
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 index line resolves to a document that is present, legible, and applicable to this tail
- Each modification the binder claims is backed by embodiment evidence rather than the SB text alone
- STC references match the approved data revision recorded at embodiment
- Effectivity statements inside the binder agree with the configuration-control log
- Records added since the last transition appear in the index instead of loose at the back of a section
Evidence normally required
- The delivery or redelivery binder, including its index, in whatever form it survives
- SB compliance records and the modification status for the airframe
- STC files and associated approved data for embodied changes
- Equipment lists and effectivity notes for the serial number
- The configuration-control log or its equivalent in the operator's system
Common discrepancies
- Index lines pointing at documents that were removed, misfiled, or never filed
- A modification embodied after delivery that exists in the control log but nowhere in the binder
- STC paperwork filed without the approved data revision that supported embodiment
- An equipment list revision in the binder that predates the configuration the aircraft actually flies
What is at stake
A baseline built from an unverified binder carries the binder's errors forward into status reports, effectivity decisions, and the next transaction. Exceptions then surface when a counterparty's review team reads the index against the sections, at the point in a deal where every unsupported line has a negotiating price attached.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix the binder version
Establish which copy of the binder is the working reference and log every variant in circulation.
Read the index against the sections
Resolve every index line to a filed document and record presence, legibility, and applicability.
Trace entries to source
Check modification, STC, and equipment entries against embodiment evidence, approved data, and the configuration-control log.
Issue the exception list
Deliver the supported-versus-unsupported map with a retrieval plan for each open entry.
What the buyer receives
- A source-specific exception list keyed to the binder index
- A supported-versus-unsupported map of the binder for the configuration support package
- A retrieval plan for each unsupported entry naming the likely holder of the missing record
Who uses the output
- Configuration managers assembling or defending a modification baseline
- Records teams preparing the binder for a lease return or sale
- Asset managers deciding which gaps to chase before a counterparty finds them
How the work fits into the transaction or program
A binder review is one source-file check inside a wider modification-baseline validation. Its exception list feeds the configuration support package directly, and its retrieval plan usually becomes the first work queue when the baseline moves from assessment into remediation ahead of a transition.
Jurisdiction-specific considerations
Under FAA oversight the binder draws on records kept to 14 CFR 91.417, while an EASA-managed aircraft carries continuing-airworthiness records structured to Regulation (EU) No 1321/2014. Binder conventions differ between the two regimes, and an aircraft that has crossed registries often holds a hybrid: the review reads each section against the regime in force when the record was created.
Regulatory limits
The review reports on documentary support for binder entries. It does not approve modifications, issue any airworthiness determination, or amend approved data; those functions stay with the design approval holders and the responsible authority.
What this review does not cover
- Engineering evaluation of the modifications themselves
- Physical verification that a modification is installed on the aircraft
- Assembly of a replacement binder from scratch, which is scoped separately
Specific to this review
- Binders are usually assembled in the last weeks before a redelivery, which is precisely when index accuracy slips.
- An index that reads clean can hide substitution: the section holds a document with the right title from the wrong revision or the wrong tail.
- Modifications embodied between transitions are the most common absentees, because no redelivery event ever forced them into the binder.
- Unsupported index lines discovered by a counterparty become priced exceptions, so the review costs far less than the argument it prevents.
Sources
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.
U.S. Government (eCFR). Requirement to transfer maintenance records with an aircraft on sale or transfer of ownership.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Is this the same as a full modification-baseline validation?
No. The binder review covers one source file: the delivery and redelivery binder and its index. A full baseline validation reads every source file in the package, including SB records, STC files, and effectivity data, and the binder review's exception list becomes one input to that larger picture.
What happens to entries the review cannot support?
Each one lands on the exception list with the likely holder of the missing record identified, so the configuration manager can decide whether to retrieve, reconstruct, or carry the entry as a documented open item in the configuration support package.
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.