Recordkeeping duties allocated when aircraft move onto a new AOC

The problem

: when an aircraft transfers onto a new operator's AOC, the recordkeeping and retention duties split between the departing operator, the receiving operator, and the CAMO, and getting the boundary wrong leaves a gap neither party owns.

What gets reviewed

• Confirm the decision path for aoc transfer records duties review before the aircraft file is submitted.
• Reconcile retained records the departing operator must keep under its rules (121.380/135.439 or Part-M) 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.

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

• retained records the departing operator must keep under its rules (121.380/135.439 or Part-M)
• current-status set the receiving operator must have to fly (AD
• CAMO record-system handover
• reconciliation confirming no live task falls in the gap between certificates
• Current AD status report
• Life-limited component status

Common discrepancies

• departing operator retaining originals the new operator needs.
• new operator flying on status lists it never verified.
• deferrals carried without the new AOC's MEL basis.
• The file treats retained records the departing operator must keep under its rules (121.380/135.439 or Part-M) as closed without enough support.

What is at stake

the departing operator retaining originals the new operator needs, the new operator flying on status lists it never verified, deferrals carried without the new AOC's MEL basis, and a retention-duty gap where a record required later cannot be produced by either operator.

How the work runs

What the buyer receives

• AOC transfer records duties review review memo
• Gap list with affected status items
• Submission-ready records index
• Commercial exposure notes

How the work fits into the transaction or program

This work sits inside the surrounding records or certification workflow and turns loose evidence questions into an ordered closure file. The page-specific framing is The regulation-intersection burden: when an aircraft transfers onto a new operator's AOC, the recordkeeping and retention duties split between the departing operator, the receiving operator, and the CAMO, and getting the boundary wrong leaves a gap neither party owns. The evidence set is the retained records the departing operator must keep under its rules (121.380/135.439 or Part-M), the current-status set the receiving operator must have to fly (AD, LLP, AMP, deferrals), the CAMO record-system handover, and the. For aoc transfer records duties, the practical output is a defensible record of what was checked, what did not match, who owns the fix, and which issue remains outside the review boundary. The aoc transfer records duties review scope is intentionally narrow: Allocate recordkeeping and retention duties correctly when an aircraft transfers onto a new operator's AOC.. The Aoc Transfer Records evidence question is tested against ad status and not against a generic checklist copied from another page. The Duties Review Recordkeeping trigger is aircraft transfer onto a new operator's aoc, so the review ranks gaps by decision impact instead of document volume. The Allocated Aircraft Move searcher pattern is An operator or CAMO handling an AOC transfer searching which records duties fall to whom between the two operators.. The Onto New Operator evidence trail has to show source location, current status, conflicting entries, and the owner who can close the issue. The Whose Moves Certificate exception logic separates missing artifacts from mismatched data because those findings move through different closure routes. The Duty Allocation Baseline handoff is written for operator technical director, with unresolved items preserved as decisions rather than softened into narrative prose. The deliverable stays anchored on aoc transfer records duties review review memo, which makes the next reviewer able to reperform the path without rebuilding the file. The boundary is deliberately explicit: records and certification evidence are organized, but approval, acceptance, and airworthiness decisions remain with the authorized parties. The brief-specific angle is The regulation-intersection burden: when an aircraft transfers onto a new operator's AOC, the recordkeeping and retention duties split between the departing operator, the receiving operator, and the CAMO, and getting the boundary wrong leaves a gap neither party owns. The evidence set includes the retained records the departing operator must keep under its rules (121.380/135.439 or Part-M), the current-status set the receiving operator must have to fly (AD, LLP, AMP, deferrals), the CAMO record-system handover, and the reconciliation confirming no live task falls in the gap between certificates. The failure pattern includes the departing operator retaining originals the new operator needs, the new operator flying on status lists it never verified, deferrals carried without the new AOC's MEL basis, and a retention-duty gap where a record required later cannot be produced by either operator. The aoc transfer records duties review aoc transfer duties lane records how aircraft move onto affects whose are moves, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review duties recordkeeping allocated lane records how onto new operator affects moves certificate duty, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review allocated aircraft move lane records how operator whose are affects duty allocation regulation, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review move onto new lane records how are moves certificate affects regulation intersection burden, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review new operator whose lane records how certificate duty allocation affects burden transfers retention, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review whose are moves lane records how allocation regulation intersection affects retention split between, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review moves certificate duty lane records how intersection burden transfers affects between departing receiving, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review duty allocation regulation lane records how transfers retention split affects receiving camo getting, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review regulation intersection burden lane records how split between departing affects getting boundary wrong, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review burden transfers retention lane records how departing receiving camo affects wrong leaves, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review retention split between lane records how camo getting boundary affects aoc transfer duties, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review between departing receiving lane records how boundary wrong leaves affects duties recordkeeping allocated, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review receiving camo getting lane records how leaves affects allocated aircraft move, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review getting boundary wrong lane records how transfer duties recordkeeping affects move onto new, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review wrong leaves lane records how recordkeeping allocated aircraft affects new operator whose, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review aoc transfer duties lane records how aircraft move onto affects whose are moves, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review duties recordkeeping allocated lane records how onto new operator affects moves certificate duty, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The aoc transfer records duties review allocated aircraft move lane records how operator whose are affects duty allocation regulation, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The governing intent remains Allocate recordkeeping and retention duties correctly when an aircraft transfers onto a new operator's AOC.. The operating angle for this page is The regulation-intersection burden: when an aircraft transfers onto a new operator's AOC, the recordkeeping and retention duties split between the departing operator, the receiving operator, and the CAMO, and getting the boundary wrong leaves a gap neither party owns. Evidence set: the retained records the departing operator must keep under its rules (121.380/135.439 or Part-M), the current-status set the receiving operator must have to fly (AD, LLP, AMP, deferrals), the CAMO record-system handover, and the reconciliation confirming no live task falls in the gap between certificates. Failure modes: the departing operator retaining originals the new operator needs, the new operator flying on status lists it never verified, deferrals carried without the new AOC's MEL basis, and a retention-duty gap where a record required later cannot be produced by either.

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

• AOC transfer records duties review depends on the aircraft status at the transfer date, not on an older audit snapshot.
• FAA and EASA 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-transfer-records-duty-allocation is the page-specific risk that drives the request list and closure plan.
• The scope uses the Aoc Transfer Records Duties question as the control point, so the review stays tied to Aircraft transfer onto a new operator's AOC and the buyer decision behind it.
• The evidence starts with AD status and follows Review Recordkeeping Allocated Aircraft 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 operator technical director: 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 Move Onto New Operator questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
• The handoff value comes from AOC transfer records duties review review memo; it gives the next reviewer a precise map instead of another broad request for a better file.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits