Directives you did not have to look up
EASA publishes, AerSynx syncs overnight, and the aircraft still linked to the previous revision are on your screen by morning, as gaps.
CONTINUING AIRWORTHINESSAirworthiness you can prove.
Directives, life limits, maintenance programmes, deferred defects and review certificates — tracked against the aircraft, not against a spreadsheet tab, and pushed to Supply when a limit approaches.
For the CAMO analyst who signs the compliance statement, and the postholder who answers for it.
- 8 key modules
- 29,406 AD references
- overdue is strictly before today
WHAT CHANGES FOR YOU
Life limits that open the purchase order
When an LLP or HTC component crosses the threshold, the requisition is already in Supply, deduplicated, with the part and the tail number on it.
Closures you can defend
A swap, an overhaul or a MEL rectification cannot close without an OCR-complete record attached to the right event and the right aircraft. The server enforces it, not a checklist.
SIGNATURE WORKFLOW
A revised directive, from Cologne to your finding.
Nobody looks anything up. The library moves, the gap appears, the analyst decides.
- 01EASA publishes
2024-0187 R1 → R216-Sep, evening - 02Nightly sync
05:45 · 29,406 referenceslibrary updated - 03Applicability
envelope: A320-232 ✓ MSN in range ✓AI only if the envelope cannot decide - 04GAP Monitor
TC-AXB, TC-AXC still on R105:47 · revision gap - 05Finding
FND-2026-0091 · assignedthe analyst escalates
CONNECTS TO
KEY MODULES
AD Tracking and AD Library
EASA and FAA directives kept as separate records, never merged, each with its authority, source and document. The library holds 29,406 published references and is synced every morning; when a directive is revised or superseded, the aircraft still linked to the previous issue appear as gaps before anyone opens a browser. Applicability is decided by the type and variant envelope first and by AI only when the envelope cannot decide, and every decision is audited.
- 29,406 references
- nightly EASA sync
- revision & supersedure gaps
LLP Tracking and Review Queue
Life-limited parts against an absolute cycle limit that overhaul, swap and shop visit never reset. One formula computes remaining life for every consumer: the API, the replacement flow, exports, forecast and KPIs. AI-extracted candidates from delivery reports wait in a review queue; only an analyst writes the master record, and the back-to-birth chain is shown installation by installation.
- absolute limit
- one formula everywhere
- analyst writes, AI proposes
ALL MODULES IN CAMO
| Module | Primary job | Signals |
|---|---|---|
| AD Tracking and AD Library | Directive compliance and reference library | 29,406 referencesnightly EASA sync |
| LLP Tracking and Review Queue | Remaining-life control | absolute limitone formula everywhere |
| LDND and MPD Management | Recurring task scheduling | utilisation-drivenMPD mapped |
| Component Status | HTC, OCCM and avionics status | HTC · OCCM · avionicsnightly recalculation |
| AMP Management and Gap Analysis | Programme revisions and MPD gaps | revision effectivitygap vs MPD |
| MEL / CDL | Deferred defects with deadlines | category ladderevidence to close |
| Reliability, Forecast and ARC | Trends, forecast and review readiness | monthly periodsalerts on change only |
| Workflow Events, History and Packages | Master record events and handovers | two faces per eventsingle-writer history |
AD Tracking and AD Library
EASA and FAA directives kept as separate records, never merged, each with its authority, source and document. The library holds 29,406 published references and is synced every morning; when a directive is revised or superseded, the aircraft still linked to the previous issue appear as gaps before anyone opens a browser. Applicability is decided by the type and variant envelope first and by AI only when the envelope cannot decide, and every decision is audited.
LLP Tracking and Review Queue
Life-limited parts against an absolute cycle limit that overhaul, swap and shop visit never reset. One formula computes remaining life for every consumer: the API, the replacement flow, exports, forecast and KPIs. AI-extracted candidates from delivery reports wait in a review queue; only an analyst writes the master record, and the back-to-birth chain is shown installation by installation.
LDND and MPD Management
Last done / next due for every recurring task, driven by the aircraft's own utilisation rather than a fixed calendar, against the manufacturer's planning document. Imports are queued and processed every minute; calendar intervals are normalised the same way everywhere (a month is 30.4375 days, a year 365.25).
Component Status
Hard-time, on-condition, avionics, software, life-vest and oxygen generator status with counters derived from the flight timeline and recalculated every night. A component removal opens a reliability defect automatically, so the analysis and the record cannot disagree.
AMP Management and Gap Analysis
Maintenance programme revisions with their effectivity, so an aircraft is measured against the revision it actually flies under, plus a gap analysis of the programme against the manufacturer's MPD. Templates live with the programme, not in a separate document store.
MEL / CDL
Open items with their category deadline ladder, extensions and dispatch state, on a master MEL/CDL per aircraft type. Rectification cannot close without an OCR-complete, AI-summarised record attached to a Shop Visit or Inspection event on the same aircraft. Overdue items are notified every morning.
Reliability, Forecast and ARC
Reliability periods computed monthly from the events already recorded, with alerts only when a control limit is crossed or the trend flips. Forward maintenance forecasts carry full precision and round only on screen. Airworthiness review readiness shows what stands between the aircraft and its ARC.
Workflow Events, History and Packages
Swaps, overhauls, shop visits and transitions as position-aware master records with two faces per event: the removed part and the installed part. The component on/off history has a single writer, so it cannot be contradicted elsewhere. Work packages are handed from engineering to the maintenance organisation without retyping.
IN THE BACKGROUND
Still working when nobody is logged in.
- Daily 05:45EASA AD library synced; revisions and supersedures detected
- Daily 07:00LLP and HTC thresholds swept; requisitions opened without duplicates
- DailyMEL and structural-repair deadlines checked
- MonthlyReliability periods computed; alerts only on change
COMMON QUESTIONS
CAMO
The questions this workspace gets asked most often.
What is CAMO software?
CAMO software manages continuing airworthiness for an aircraft fleet: airworthiness directives, life-limited parts, the maintenance programme, deferred defects and airworthiness review certificates. It exists so that a Continuing Airworthiness Management Organisation can show, at any moment, that every applicable requirement has been met and can produce the evidence for it.
How are airworthiness directives kept up to date?
The EASA library is synchronised every morning and revisions and supersedures are detected automatically, against a reference catalogue of 29,406 directive references. A directive that supersedes another does not quietly replace it — the change is raised so an analyst decides what it means for each aircraft in the fleet.
Does a life limit automatically open a purchase order?
It opens the demand. Life-limited part and hard-time thresholds are swept daily, and a part approaching its limit raises a requisition in Supply without creating a duplicate for a requirement that is already being handled. The buyer sees the requirement with the aircraft and the limit that caused it.
Is a task due today counted as overdue?
No. Overdue means strictly before today; a task due today is due, not late. Merging the two states looks harmless in a spreadsheet and is not: it either grounds an aircraft that was never out of limits, or it teaches the planner to ignore an alert that is wrong most mornings.
IN THE FIRST SESSION
Bring one aircraft and its open directives.
We load its ADs, LLPs and LDND, run the revision check against the library and show which gaps appear. Forty-five minutes is enough to see whether the workflow fits yours.