What Is a Transition CAMO — and the AD-Status Review That Makes Handovers Clean
When a fleet changes hands — a new operator, a new registry, a returned lease, or simply a change of continuing-airworthiness provider — someone has to take over the management of that fleet's airworthiness. That incoming organisation is acting as a transition CAMO: the Continuing Airworthiness Management Organisation responsible for the aircraft through, and after, the changeover.
The transition is where airworthiness risk concentrates, because the incoming CAMO inherits a status it didn't compute. Of everything that has to be re-established, the AD position is one of the highest-stakes and easiest to get wrong. This article explains what a transition CAMO is and how a disciplined AD-status review turns a risky handover into a clean day-one position.
What a transition CAMO is — and when one is used
A CAMO manages the continuing airworthiness of aircraft under Part-CAMO: maintenance programmes, airworthiness reviews, and compliance with directives among them. A transition CAMO is that same function performed at a moment of change — most commonly:
- an operator switching from one CAMO to another,
- an aircraft moving between operators,
- a lease starting or ending (onboarding or redelivery),
- or a change of State of Registry.
In each case the aircraft's continuing-airworthiness record moves with it, and the receiving organisation has to accept that record — or challenge it — before it can manage the aircraft with confidence.
The handover risk: you inherit an AD status you didn't compute
The core problem is simple: the applicable-AD list you're handed was determined by someone else, under their assumptions, with their data. It may be excellent. It may also contain the ordinary errors that accumulate in any manually maintained record — a mis-recorded modification state, an aircraft anchored to a slightly wrong type, an engine variant that changed and wasn't reflected, a recurring AD marked closed, a superseded directive still open, or a cross-jurisdiction AD that never entered the list.
Accepting that status uncritically means adopting its errors as your own. From the changeover date, they're your findings to answer for. The safe posture is not to trust the inherited list, but to re-establish it from source and reconcile.
The AD-status review: re-establish applicability per tail, from source
A clean transition rebuilds the AD position rather than importing it. Per aircraft, that means:
- Anchor the aircraft correctly to its type certificate (TCDS) and model — the foundation from which the entire applicable-AD set follows.
- Confirm the configuration that decides applicability: serial number (MSN), modification and STC state, installed part numbers.
- Confirm the engine and propeller variant actually fitted — powerplant ADs follow the engine, not the airframe.
- Compute the applicable set by reading each directive's effectivity against that confirmed state, across every relevant authority, deduplicating comply-once directives.
- Establish deadlines and recurring items — one-time vs recurring, and the next due point for each recurring requirement.
The output is an applicable-AD list you can stand behind because you derived it, not one you accepted on faith.
Reconciling incoming records against computed status
Re-establishing the list is only half the job; the other half is reconciliation. Put your independently computed status next to the incoming record and look at the differences:
- Items on the incoming list but not on yours — over-application, or a difference in configuration data to resolve.
- Items on yours but not on the incoming list — potential gaps the previous holder missed.
- Compliance states that don't match — an item they marked complied that your evidence doesn't support, or vice versa.
Every difference is a question to close before the changeover, on your terms, with time to investigate — not during an audit, under pressure, with the outcome already on your certificate.
A clean day-one position — a short checklist
By the changeover date, aim to have:
- Every tail anchored to the correct TCDS and type — or explicitly flagged as unresolved.
- Configuration and engine variant confirmed per aircraft.
- An independently computed applicable-AD set per tail.
- Reconciliation against the incoming record, with every difference resolved or documented.
- Deadlines and recurring items established with next-due points.
- The whole thing captured as evidence, so the position is defensible from day one.
How Aviagent helps a transition
Aviagent is built to produce exactly this. It anchors each aircraft, computes the applicable set across EASA, FAA, TCCA, and ANAC from the directives' own effectivity, and gives you an independent second source to reconcile against the record you're inheriting — with every determination shown with its reasoning and confirmed by your engineers. Where data is missing to decide, it flags an explicit unknown to resolve rather than guessing. The result is a documented, day-one AD position you own — the difference between inheriting someone else's status and establishing your own.
FAQ
What is a transition CAMO? A CAMO managing an aircraft's continuing airworthiness through a change — of operator, registry, lease, or provider. It has to accept or re-establish the aircraft's airworthiness status, including its AD position, at the handover.
Can't I just accept the previous CAMO's AD list? You can, but you inherit its errors. From the changeover date, any mistake in that list is yours to answer for. Re-establishing the applicable set from source and reconciling is the lower-risk approach.
What's most likely to be wrong in an inherited AD list? Common issues include a wrong type anchor, an out-of-date modification or engine-variant record, a recurring AD marked closed, a superseded directive still open, and a missed cross-jurisdiction AD.
How long does an AD-status review take? It depends on fleet size and data quality, but computing applicability independently — rather than checking tail by tail in a spreadsheet — is what makes it feasible within a transition timeline.
See which ADs apply to your fleet — free, in about 30 seconds. Try the free AD lookup, or book a 20-minute walkthrough.
Related reading: Which airworthiness directives apply to your aircraft (the pillar) · Building an audit-ready AD evidence chain · AD compliance at aircraft redelivery.
About the author — Satya Neerupudi is Founder & CEO/CTO of Aviagent and an aeronautical engineer with 25 years in continuing airworthiness at SAS, GE Aviation, Pratt & Whitney, and HAL.