Aircraft records
Function-by-function records attribution under Article 83bis oversight
operators, CAMOs, lessors use this review when ongoing operation under an Article 83bis agreement. EE reconciles 83bis agreement's function-by-function allocation, AD status maintained against the correct mandating authority for each transferred function, ARC held under whichever state retained it with logbooks, releases, approvals, status lists, and custody evidence. A discrepancy is any item that cannot be traced to source support or could fail because of aD compliance tracked against the wrong state after transfer. The package gives the team a status reconciliation, open-items register, and closure evidence plan.
The problem
distinct from assembling the transfer agreement: once an 83bis agreement is in force, oversight of specific functions (AD mandating, C of A, crew licensing, maintenance approval) splits between the state of registry and the state of the operator, and the records must show which authority's requirements govern each function day to day.
What gets reviewed
- Inventory the records named in the brief and mark who controls each original.
- Compare 83bis agreement's function-by-function allocation with the next registry, operator, or buyer review basis.
- Review release, approval, and utilization evidence for gaps at the changeover date.
- Document unresolved exceptions with affected status lines and requested closure evidence.
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
- Source support is adequate when logbook, release, and status data agree on date, serial number, and effectivity.
- Record a discrepancy if aD compliance tracked against the wrong state after transfer appears in the delivered file.
- Acceptance remains unresolved when a foreign approval, translation, or copy status is undocumented.
- A handover item passes when the next party can identify the exact record it will rely on.
Evidence normally required
- 83bis agreement's function-by-function allocation
- AD status maintained against the correct mandating authority for each transferred function
- ARC held under whichever state retained it
- maintenance approvals traced to the responsible authority
- audit trail showing the operator followed the right state's rules per function
- Current AD status report
Common discrepancies
- AD compliance tracked against the wrong state after transfer.
- function assumed transferred that the agreement left with the registry.
- records that never distinguish which authority governs a given task.
- The file treats 83bis agreement's function-by-function allocation as closed without enough support.
What is at stake
AD compliance tracked against the wrong state after transfer, a function assumed transferred that the agreement left with the registry, records that never distinguish which authority governs a given task, and an oversight visit by one authority finding the operator followed the other's rules.
How the work runs
Frame Article 83bis
Confirm the exact event, affected file set, buyer role, and decision standard before any ad status is treated as sufficient.
Trace Split Records
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 Function Attribution
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Aircraft Authority
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
- Article 83bis oversight split records review status reconciliation
- Records custody tracker
- Approval and release evidence table
- Priority closure register
How the work fits into the transaction or program
The regulation-intersection burden, distinct from assembling the transfer agreement: once an 83bis agreement is in force, oversight of specific functions (AD mandating, C of A, crew licensing, maintenance approval) splits between the state of registry and the state of the operator, and the records must show which authority's requirements govern each function day to day; the 83bis agreement's function-by-function allocation, the AD status maintained against the correct mandating authority for each. The evidence set centers on the 83bis agreement's function-by-function allocation, the AD status maintained against the correct mandating authority for each transferred function, the C of A and ARC held under whichever state retained it, maintenance approvals traced to the responsible authority, and the audit trail showing the operator followed the right state's rules per function. The likely weak points are AD compliance tracked against the wrong state after transfer, a function assumed transferred that the agreement left with the registry, records that never distinguish which authority governs a given task, and an oversight visit by one authority finding the operator followed the other's rules. Handoff: CAMO manager, ongoing operation under an Article 83bis agreement, Function-by-function records attribution under Article 83bis oversight.
Start with a single asset
Reconcile maintenance tracking against the underlying records.
Regulatory limits
The output supports the applicant and transaction team with organized evidence. Final airworthiness, conformity, operational, and regulatory decisions remain with the competent authority, authorized representative, operator, CAMO, or contracting party.
Specific to this review
- Article 83bis oversight split records review depends on the aircraft status at the transfer date, not on an older audit snapshot.
- ICAO and EASA and FAA 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.
- 83bis-function-oversight-records-attribution is the page-specific risk that drives the request list and closure plan.
- The scope uses the Article 83bis Oversight Split question as the control point, so the review stays tied to Ongoing operation under an Article 83bis agreement and the buyer decision behind it.
- The evidence starts with AD status and follows Records Review Function Attribution 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 Under Aircraft Authority Govern questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Article 83bis oversight split records review status reconciliation; 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.
International Civil Aviation Organization. International standards for the airworthiness of aircraft and the framework states use for type and continuing airworthiness.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
What makes this transitions review different from a general file audit?
The scope is tied to article 83bis oversight split and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block ongoing operation under an article 83bis agreement 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 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.