Import records
First-aircraft import records aligned with a new operator certificate
This review is for airlines, operators, CAMOs facing first aircraft induction for a new AOC. EE examines import pack plus maintenance program approval sequencing, CAMO or maintenance control readiness, configuration conformity to the intended ops spec. against the applicable authority, contract, and continuing-airworthiness record basis. The work calls out weak proof, timing conflicts, untranslated or uncertified records, and requesting the C of A before the AMP is approved so the application loops. Deliverables include a review memo, records index, discrepancy register, and next-action list.
The problem
preparing records for the heightened scrutiny of a start-up operator's first import, where the aircraft's C of A file and the AOC demonstration draw on the same evidence and any sequencing error delays both.
What gets reviewed
- Confirm the decision path for first aircraft import records for a new aoc before the aircraft file is submitted.
- Reconcile import pack plus maintenance program approval sequencing to logbook entries, certificates, approvals, or status reports.
- Challenge assumptions about carryover items, accepted approvals, and stale summaries.
- Package the open list so commercial, records, and technical owners can close items in sequence.
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
- Verify that the file answers the specific import, redelivery, or registration question raised by the brief.
- Mark stale data as failed when AD, LLP, mod, or deferral status stopped before the review date.
- Review copies for certification, legibility, and link to the source package before treating them as evidence.
- Keep commercial acceptance separate from technical closure in the discrepancy register.
Evidence normally required
- import pack plus maintenance program approval sequencing
- CAMO or maintenance control readiness
- configuration conformity to the intended ops spec
- Current AD status report
- Life-limited component status
- Modification and repair approval list
Common discrepancies
- requesting the C of A before the AMP is approved so the application loops.
- findings during the AOC demonstration traced back to induction records nobody quality-checked.
- The record owner cannot produce originals or certified copies before review.
- The file treats import pack plus maintenance program approval sequencing as closed without enough support.
What is at stake
requesting the C of A before the AMP is approved so the application loops, and findings during the AOC demonstration traced back to induction records nobody quality-checked.
How the work runs
Frame First Aircraft
Confirm the exact event, affected file set, buyer role, and decision standard before any ad status is treated as sufficient.
Trace New Aoc
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 Review Aligned
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Certificate Under
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
- First aircraft import records for a new AOC review memo
- Gap list with affected status items
- Submission-ready records index
- Commercial exposure notes
How the work fits into the transaction or program
The decision is preparing records for the heightened scrutiny of a start-up operator's first import, where the aircraft's C of A file and the AOC demonstration draw on the same evidence and any sequencing error delays both; the import pack plus maintenance program approval sequencing, CAMO or maintenance control readiness, and configuration conformity to the intended ops spec. The evidence set centers on the import pack plus maintenance program approval sequencing, CAMO or maintenance control readiness, and configuration conformity to the intended ops spec. The likely weak points are requesting the C of A before the AMP is approved so the application loops, and findings during the AOC demonstration traced back to induction records nobody quality-checked. Handoff: head of airworthiness, first aircraft induction for a new AOC, First-aircraft import records aligned with a new operator certificate.
Start with a single asset
Prove the review on a single tail, then scale across the fleet.
Regulatory limits
EE identifies gaps and prepares the records case. It does not perform regulatory certification, sign a release to service, approve design data, or make the final technical acceptance decision for any authority or buyer.
Specific to this review
- First aircraft import records for a new AOC depends on the aircraft status at the transfer date, not on an older audit snapshot.
- ICAO context changes what evidence is persuasive even when the status heading looks familiar.
- A summary gains value only when the release, approval, inspection, or utilization record behind it can be found.
- aoc-startup-first-import is the page-specific risk that drives the request list and closure plan.
- The scope uses the First Aircraft Import New question as the control point, so the review stays tied to First aircraft induction for a new AOC and the buyer decision behind it.
- The evidence starts with AD status and follows Aoc Records Review Aligned 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 head of airworthiness: 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 Operator Certificate Under Double questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from First aircraft import records for a new AOC review memo; it gives the next reviewer a precise map instead of another broad request for a better file.
Sources
International Civil Aviation Organization. International standards for aircraft operation, including maintenance program and recordkeeping expectations.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
Frequently asked questions
What makes this transitions review different from a general file audit?
The scope is tied to first aircraft import new and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block first aircraft induction for a new aoc or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is ad status, 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 head of airworthiness 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.