Registry transition
EASA Import Airworthiness Review Ma904 source evidence review
CAMOs, operators, lessors use this review when import from a third country onto an eu register makes importing onto eu register evidence material. The work checks registration file, maintenance status summary against export package, release documents, modification approvals and the current configuration or transfer need. Discrepancies are logged when the source page does not prove the same asset, date, requirement, or status claim. The buyer receives importing onto eu register baseline reconciliation table, Conflicting-evidence log, Transfer readiness request list.
When this review is needed
- A Import from a third country onto an EU register makes importing onto eu register a gating item for closing, import, or continued tracking.
- Different systems show different dates, intervals, or component identities.
- The current holder needs a clean explanation for the receiving registry, CAMO, lender, or lessor.
- The package has enough paperwork to review, but it lacks a clear evidence path.
The problem
The hard part of importing onto eu register is deciding which document controls the answer. Log entries, certificates, program extracts, and status reports may all be present, yet only some prove the specific claim now being made.
What gets reviewed
- Establish the current importing onto eu register baseline from the supplied status file.
- Compare the baseline with source records, certificates, and program extracts.
- Look for breaks caused by custody changes, replacement parts, or revised instructions.
- Document whether each open line is missing evidence, conflicting evidence, or outside scope.
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 identity, timing, and source basis align across independent records.
- Fail when the status depends on an unreferenced note or unsupported manual entry.
- Check whether the receiving party can rely on the same document set after transfer.
- Escalate conflicts where two source records support different conclusions.
Evidence normally required
- registration file
- maintenance status summary
- export package
- release documents
- modification approvals
- maintenance program mapping
Common discrepancies
- FAA-era approvals without an EASA acceptance path stalling the ARC recommendation.
- program compliance impossible to show because prior-operator records lack task-level detail.
- timelines built on the ferry date instead of the records review's real duration.
What is at stake
A loose package can push the issue into a closing checklist, an import review, or a post-delivery dispute. Clear evidence grading gives the parties a record-based basis for acceptance, reserve, or recovery.
How the work runs
Frame EASA Import
Confirm the exact event, affected file set, buyer role, and decision standard before any registration file is treated as sufficient.
Trace Review Ma904
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 Onto Register
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Evidence Registry
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
- importing onto eu register baseline reconciliation table.
- Conflicting-evidence log.
- Transfer readiness request list.
- Reviewer notes for unresolved exceptions.
Who uses the output
How the work fits into the transaction or program
The what records the importing CAMO and competent authority will demand for the first ARC when an aircraft joins an EU member state register from a third country; full documented review of the aircraft records, AMP compliance demonstration against the new operator's program, mod and repair approvals re-based to EASA acceptance, LLP and AD status with source evidence. The evidence set centers on full documented review of the aircraft records, AMP compliance demonstration against the new operator's program, mod and repair approvals re-based to EASA acceptance, LLP and AD status with source evidence. The likely weak points are FAA-era approvals without an EASA acceptance path stalling the ARC recommendation, program compliance impossible to show because prior-operator records lack task-level detail, timelines built on the ferry date instead of the records review's real duration. Handoff: CAMO manager, import from a third country onto an EU register, EASA Import Airworthiness Review Ma904 source.
Start with a single asset
Reconcile maintenance tracking against the underlying records.
Jurisdiction-specific considerations
The receiving registry or operator may ask for the same evidence in a different order, so the package is organized by decision, source page, and open acceptance question.
Regulatory limits
EASA and approved organizations retain responsibility for approvals, airworthiness review outcomes, and continuing airworthiness decisions. This work packages evidence and exceptions for review, and it does not grant acceptance.
What this review does not cover
- Physical inspection of the aircraft or component.
- Regulatory applications or formal authority submissions.
- Legal interpretation of purchase, lease, or financing remedies.
Specific to this review
- Conflicts between independent records need a named controlling source, not a blended answer.
- A transfer-ready package shows why the evidence applies to this asset today.
- The most useful findings identify the mismatch, the affected decision, and the next document to request.
- The scope uses the EASA Import Airworthiness Review question as the control point, so the review stays tied to Import from a third country onto an EU register and the buyer decision behind it.
- The evidence starts with registration file and follows Ma904 Importing Onto Register 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 CAMO 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 Source Evidence Registry Transition questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from importing onto eu register baseline reconciliation table.; 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 Prepare the records package that survives an M.A.904 import airworthiness review onto an EU register..
Sources
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 transitions review different from a general file audit?
The scope is tied to easa import airworthiness review and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block import from a third country onto an eu register or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is registration 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 camo 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.