Skip to content

Lease transition

MAG Dual Release records evidence

For MROs, equipment suppliers, Aircraft records teams, the trigger is setting up or auditing dual-release paperwork. The decision: whether component release certificates carry a valid dual release under the FAA-EASA Maintenance Annex Guidance, so parts can be installed on either authority's aircraft without rework. Evidence set: block 12 dual-release statements, the certifying organization's dual approval status at the work date, work-order references, MAG change level in force. EE checks release certificate, issuing organization approval evidence, work order or shop file against the current status claim and the acceptance criteria supplied for the review. The buyer receives a discrepancy register, evidence map, closure.

What gets reviewed

  • The decision: whether component release certificates carry a valid dual release under the FAA-EASA Maintenance Annex Guidance, so parts can be installed on either authority's aircraft without rework.
  • Evidence set: block 12 dual-release statements, the certifying organization's dual approval status at the work date, work-order references, MAG change level in force.
  • Tie every accepted line to the affected serial number, date, revision, or work package.
  • Separate recoverable filing defects from issues that need technical disposition.

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

  • Accept the mag dual release position when source evidence matches the summary claim and affected asset.
  • Question the mag dual release position when a spreadsheet, index, or status flag is the only support.
  • Escalate the mag dual release item when configuration, serial, approval, or repeat-task logic changes the outcome.

Evidence normally required

  • release certificate
  • issuing organization approval evidence
  • work order or shop file
  • receiving inspection notes
  • correction or reissue trail

Common discrepancies

  • single-authority releases on parts destined for the other system, dual-release wording from a superseded MAG change, shops signing dual release for work outside their EASA approval scope.
  • A mag dual release summary cites evidence that is missing, stale, or filed under another asset.
  • The closure package omits the document that would let the next reviewer repeat the conclusion.

How the work runs

01

Frame FAA EASA

Confirm the exact event, affected file set, buyer role, and decision standard before any release certificate is treated as sufficient.

02

Trace Dual Release

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.

03

Sort Records Evidence

Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.

04

Package Transition Block

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

  • MAG Dual Release evidence map with source-page references
  • MAG Dual Release discrepancy register sorted by blocker, reservation, and monitor item
  • MAG Dual Release document request list naming the exact missing or corrected record
  • Decision note for the setting up or auditing dual-release paperwork team

How the work fits into the transaction or program

The whether component release certificates carry a valid dual release under the FAA-EASA Maintenance Annex Guidance, so parts can be installed on either authority's aircraft without rework; block 12 dual-release statements, the certifying organization's dual approval status at the work date, work-order references, MAG change level in force. The evidence set centers on block 12 dual-release statements, the certifying organization's dual approval status at the work date, work-order references, MAG change level in force. The likely weak points are single-authority releases on parts destined for the other system, dual-release wording from a superseded MAG change, shops signing dual release for work outside their EASA approval scope. Handoff: MRO quality manager, setting up or auditing dual-release paperwork, MAG Dual Release records evidence.

Start with a single asset

Confirm release certificates and component traceability are complete.

Regulatory limits

This mag dual release records review does not approve data, issue a release, determine airworthiness, or guarantee authority acceptance. Regulators, authorized persons, operators, and transaction parties make final decisions under their procedures.

Specific to this review

  • The mag dual release decision depends on source-record trace, not the neatness of the delivered index.
  • A small mismatch in date, serial, revision, or method can change the acceptance position.
  • The useful output records why each disputed line was accepted, corrected, or left open.
  • The scope uses the FAA EASA Mag Dual question as the control point, so the review stays tied to Setting up or auditing dual-release paperwork and the buyer decision behind it.
  • The evidence starts with Release certificate and follows Release Requirements Records 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 MRO quality 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 Lease Transition Block Must questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
  • The handoff value comes from MAG Dual Release evidence map with source-page references; 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 Verify dual-release statements on 8130-3 and Form 1 certificates against current MAG requirements..

Sources

Frequently asked questions

What makes this records review different from a general file audit?

The scope is tied to faa easa mag dual and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block setting up or auditing dual-release paperwork or can be closed later without changing the decision.

What evidence has to be available before this work starts?

The starting point is release certificate, 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 mro quality 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.