Delivery acceptance
Delivery-acceptance aircraft records review
A delivery-acceptance records review is the independent check the receiving party runs on the delivery binder at the point an aircraft changes hands. It serves lessors taking an aircraft on lease, airlines and operators accepting an asset, and management companies signing for a client. The trigger is an offered delivery with acceptance imminent. It measures the binder against the agreed delivery conditions, confirms the AD, LLP, and release evidence is present and supported, and flags anything that should be a delivery condition before signature. You receive an acceptance-readiness assessment, a conditions-to-delivery list, and the items to resolve or carry as agreed exceptions.
When this review is needed
- A delivery has been offered and the receiving party must accept or reject within a defined window.
- The delivery conditions reference a records standard and someone has to confirm the binder meets it.
- An acceptance is happening across borders and the receiving authority's expectations are in play.
- A client is taking delivery through a manager who needs an independent technical read before signing.
The problem
The delivery binder is assembled by the delivering side and presented as final at the moment acceptance is due. Conditions are written against the records, yet the binder is large and the window is short, so the AD evidence, the releases, and the configuration list often go unchecked. Whatever is accepted at signature becomes the receiving party's problem to unwind.
What gets reviewed
- The delivery conditions and the records standard they reference
- Binder completeness measured against the agreed delivery index
- AD and SB status with accomplishment evidence present in the binder
- Life-limited part status and the release evidence supporting it
- Authorized release certificates for components delivered with the aircraft
- Configuration and modification status against what delivery requires
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 delivery-condition item maps to a document actually present in the binder
- Applicable ADs are evidenced in the binder, not merely listed on a summary
- LLP status in the binder is supported by release and accumulation documents
- Delivered components carry release certificates valid for the operating jurisdiction
- The delivered configuration matches the modification standard the conditions require
- Binder summaries reconcile with the source documents filed alongside them
Evidence normally required
Common discrepancies
- A delivery-condition item with no corresponding document in the binder
- An AD listed as met on the summary but unevidenced in the binder
- An LLP status entry that lacks the release behind it
- A delivered component whose release certificate is missing or wrong-form
- A modification standard that the binder does not actually confirm
- A binder summary that overstates what the underlying documents show
What is at stake
Accepting a binder that does not meet the agreed conditions transfers the shortfall to the receiving party. A missing release or an unconfirmed modification standard then has to be chased from a counterparty that has already delivered, which is slower and weaker than holding it as a delivery condition.
How the work runs
Anchor to the conditions
Read the delivery conditions and the records standard, then build the checklist the binder must satisfy.
Test the binder
Confirm each condition maps to a present, supported document rather than a summary line alone.
Sort open items
Separate items that must be resolved before signature from items that can be carried as agreed exceptions.
Hand over the position
Deliver the acceptance-readiness assessment and the conditions list so the receiving party can sign on known terms.
What the buyer receives
- An acceptance-readiness assessment against the delivery conditions
- A conditions-to-delivery list of items to resolve before signature
- An agreed-exceptions schedule for items to be carried with closure terms
Who uses the output
- Technical-acceptance teams deciding whether to sign for delivery
- Asset managers holding the delivering side to the agreed conditions
- Continuing-airworthiness staff preparing to operate the aircraft
How the work fits into the transaction or program
The review runs at the acceptance gate, after any pre-purchase confirmation and before the aircraft enters service. It turns the delivery conditions into a checked position so the receiving party signs knowing exactly what is open and on what terms.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Aircraft-specific considerations
Delivery conditions tend to lean on the configuration and modification standard for the type, so the binder check weighs that evidence heavily on heavily modified aircraft and weighs release completeness more on younger ones.
Jurisdiction-specific considerations
Acceptance across authorities is not settled by the binder alone. The prior maintenance program, the approval basis, and the form of each component release have to align with the receiving authority before the records support operation there.
Regulatory limits
The review confirms that the binder is complete, consistent, and traceable against the delivery conditions. It does not perform technical acceptance for the receiving party, make an airworthiness determination, or guarantee any authority will accept the aircraft.
What this review does not cover
- Physical survey or functional check of the delivered aircraft
- Renegotiation of the delivery conditions themselves
- Any airworthiness determination or regulatory approval
Specific to this review
- Delivery conditions are written against records, but the binder is presented as final exactly when the acceptance window is shortest.
- An item held as a documented delivery condition is far easier to enforce than the same item chased after the aircraft has been accepted.
- Binder completeness and binder accuracy are checked separately, because a complete-looking index can still contain documents that do not support their own summary lines.
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). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union Aviation Safety Agency. EASA authorised release certificate for components, equivalent in function to FAA Form 8130-3.
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 technical acceptance?
No. Technical acceptance is the receiving party's own sign-off. This review is the independent check of the delivery binder against the agreed conditions that informs that sign-off and shows what is still open.
Can items be accepted with documents still missing?
They can, if both sides agree to carry them as exceptions with closure terms. The review makes those items explicit so they are accepted on purpose rather than by oversight.
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.