Ferry flight records
Aircraft ferry flight records package preparation
operators, owners, CAMOs use the review to test whether delivered records support the stated position before Ferry flight of an aircraft. The reviewer follows Ferry permit support file and Aircraft status package into Airworthiness and registration evidence, Maintenance release record, logbook entries, tracking exports, and event records. The package delivered to the buyer is a discrepancy register, source index, owner-tagged request list, and closeout summary.
When this review is needed
- A maintenance, storage, conversion, or delivery event created new records that must be reconciled to status.
- The responsible team needs to know whether the gap is missing evidence, inconsistent data, or unresolved work.
- A prior owner, shop, or system migration may hold the only page that supports the claim.
The problem
Records packages for this topic usually mix source pages with summaries and correspondence. The defect appears when those materials disagree on applicability, accomplishment, or current configuration.
What gets reviewed
- Confirm which records must accompany the aircraft and which remain as permit support.
- Check status reports for open defects, limitations, due tasks, and configuration notes.
- Review maintenance release evidence for the condition in which the aircraft will be ferried.
- Assemble registration, airworthiness, and operating documents requested for the route.
- Create a missing-item list before crew release or repositioning handover.
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
- Pass when the aircraft status, permit support, operating documents, and release entry describe the same condition.
- Fail when a ferry permit is ready but open defects are not reflected in the carried records package.
- Pass when route-specific document requests are tracked separately from aircraft maintenance records.
- Fail when records are split between maintenance and operations with no handover list.
Evidence normally required
- ferry permit or application support file
- aircraft status report
- open defect and MEL or CDL list
- maintenance release and logbook entries
- registration and airworthiness documents
- route and destination requirements supplied by the operator
Common discrepancies
- Open defect list updated after the permit support package was prepared.
- Maintenance release entry missing from the records set carried with the aircraft.
- Airworthiness document copy expired or inconsistent with registration data.
- Route document request handled by operations but absent from the technical package.
What is at stake
A weak file can force repeated document requests and delay technical acceptance. It can also blur the difference between missing evidence and actual work that may still be due.
How the work runs
Frame Ferry Flight
Confirm the exact event, affected file set, buyer role, and decision standard before any ferry permit support file is treated as sufficient.
Trace Package Preparation
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Aircraft Evidence
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Travel Not
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
- Decision register for ferry flight records exceptions
- Trace table from status claim to source evidence
- Correction and retrieval plan with owners assigned
- Management summary separating immediate blockers from monitor items
Who uses the output
- records manager uses the register to decide which lines can be accepted or escalated.
- operations lead uses the evidence map to request missing technical records.
- CAMO manager uses the closure plan for transaction, audit, or delivery decisions.
How the work fits into the transaction or program
The decision is assembling the records package that must accompany a one-time ferry flight, distinct from qualifying for the permit itself: what the receiving authority, the ferry crew, and any en-route states will expect to see; the special flight permit / permit to fly and its conditions, the airworthiness statement and inspection basis for the ferry, the specific limitations and any inoperative-equipment justification, current weight/balance and configuration for the ferry condition, insurance and. The evidence set centers on the special flight permit / permit to fly and its conditions, the airworthiness statement and inspection basis for the ferry, the specific limitations and any inoperative-equipment justification, current weight/balance and configuration for the ferry condition, insurance and de-registration/registration status covering the flight, and the AD/maintenance status snapshot at departure. The likely weak points are a permit granted but the supporting airworthiness evidence not packaged, inoperative items flown without a documented basis, a configuration on the aircraft that does not match the ferry limitations, and registration timing that leaves the aircraft undocumented mid-ferry. Handoff: records manager, ferry flight of an aircraft, Aircraft ferry flight records package preparation.
Start with a single asset
Reconcile maintenance tracking against the underlying records.
Jurisdiction-specific considerations
FAA and EASA references are used as evidence context for recordkeeping and compliance support. The review does not treat one authority's record format as automatic acceptance by another authority or by a counterparty.
Regulatory limits
The review tests whether the delivered records support the stated position. It does not create regulatory approval, perform conformity, sign maintenance releases, or decide final acceptance for the responsible authority or certificate holder.
What this review does not cover
- Maintenance planning beyond the affected evidence lines
- Acceptance of parts or documents on behalf of a regulator
- Pricing advice for open technical exposure
Specific to this review
- For this review, a ferry records package is evidence for the flight condition and handover, not the permit itself.
- A recurring records trap is that the package should reconcile maintenance status with operational documents before the aircraft moves.
- Separating carried documents from retained support files prevents last-minute confusion at departure or arrival.
- The scope uses the Ferry Flight Records Package question as the control point, so the review stays tied to Ferry flight of an aircraft and the buyer decision behind it.
- The evidence starts with Ferry permit support file and follows Preparation Review Aircraft Evidence references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for records manager: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Must Travel Not Just questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Decision register for ferry flight records exceptions; it gives the next reviewer a precise map instead of another broad request for a better file.
- The source discipline is stricter on this page than on a general audit because the claim being tested is Assemble the complete records package that must travel with an aircraft on a ferry flight..
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
International Civil Aviation Organization. International standards for the airworthiness of aircraft and the framework states use for type and continuing airworthiness.
Frequently asked questions
What makes this records review different from a general file audit?
The scope is tied to ferry flight records package and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block ferry flight of an aircraft or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is ferry permit support file, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives records manager a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
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.