Audit-ready across every directive, program, and deferral.
Airworthiness directives, maintenance programs, deferrals, and certificates — tracked against one canonical model, with the proof logged and exportable before an auditor asks for it.
The compliance modules, on one model.
Each module reads the same asset registry, so applicability, deadlines, and evidence stay consistent across the fleet.
AD Tracking
ProductionFetch directives from EASA and FAA, follow revisions and supersessions, scope Part-21 applicability, and compute overdue status. A missed AD is an audit finding and a certificate risk.
EASA/FAA fetch · revision/supersede · applicability · import/export
AMP + MPD
ProductionMove maintenance programs through a draft-to-approved revision workflow, reference the MPD library, and run gap analysis against the active program.
revision workflow · MPD library · gap analysis · reports
LDND
ProductionTrack Last Done and Next Due across the task set, import utilization asynchronously, and surface interval-deviation findings before they age.
last done / next due · async import · interval-deviation findings
ARC
ProductionHold the M.A.901 readiness gate, manage extensions, and keep the review on schedule. An expired ARC grounds the aircraft.
M.A.901 gate · extensions · readiness state
MEL / CDL
ProductionRun the A/B/C/D deadline ladder with extension approval and dispatch control, link rectification evidence, and apply CDL performance penalties.
A/B/C/D ladder · extension approval · dispatch · evidence · CDL penalty
Gap Analysis
ProductionDetect deviations across AMP, AD, utilization, and structural data, acknowledge them, and escalate the ones that matter into a tracked finding.
AMP/AD/utilization/structural · acknowledge · escalate to finding
Structural Repairs
ProductionKeep damage and repair records together with photos and measurements, track expiry, and schedule the follow-up inspection.
damage + repair records · photo/measurement · expiry · follow-up
Every compliance deadline, in one ranked timeline.
Deadlines don't live in one system. The Horizon pulls them all into a single ranked view so the one that matters surfaces first — not last.
- Pulls from 7+ sources: ADs, LLPs, hard-time components, LDND, MEL/CDL deferrals, certificates, and lease milestones.
- A fleet hotlist ranks overdue, due-today, and approaching items together.
- Per-aircraft drilldown bundles related work so visits are planned, not reactive.
Compliance fails quietly.
None of these arrive with a warning. They surface at an audit, at dispatch, or at a ramp check — when it is already a finding.
- A repetitive AD silently returns to repeat after compliance, drops out of view, and the next interval is missed — a finding, or a grounded aircraft.
- An ARC is issued without M.A.901 readiness actually verified — an invalid certificate you will have to explain.
- A MEL deferral slips past its A/B/C/D rectification deadline — a dispatch you cannot justify.
Applicability and deadlines, made explicit.
The two judgements that quietly go wrong on a spreadsheet — which tail a directive applies to, and how long a deferral has left — resolved in the record, not in someone's head.
| Directive | TC-AHZ | D-AXLR | 9H-MNT |
|---|---|---|---|
| AD 2024-18-07 | |||
| AD 2025-03-12 | |||
| AD 2023-21-04 |
Applicability resolved per tail by MSN/effectivity — complied, due, open, or not applicable, never guessed.
The A/B/C/D ladder makes each deferral's rectification window explicit, and gates dispatch.
The rules an AD tracker built on a spreadsheet gets wrong.
There is no shortcut to these. They are the difference between a system that looks compliant and one that is.
Repetitive ADs return to repeat
After a repetitive AD is complied with, it goes back to repeat — not open — so the next recurring interval is tracked, not closed out by accident.
A status set that can't lie
Every directive sits in one of open · repeat · closed · superseded · cancelled · not_applicable. There is no accomplished — a soft word that hides whether the work actually recurs.
Applicability before alarm
Part-21 applicability is scoped by MSN and effectivity, and supersede chains are followed, so a tail is flagged for the directive that applies to it — not the whole type.
The MEL deadline ladder
Category A, B, C, and D deferrals each carry their own rectification clock with extension approval and dispatch control — the ladder enforced, not approximated.
The ARC readiness gate
An ARC cannot be issued until the M.A.901 readiness state is satisfied. The gate is in the workflow, not in someone's memory.
Deviations escalate, not vanish
Gap analysis across AMP, AD, utilization, and structural data turns an acknowledged deviation into a tracked finding — the ones that matter don't get cleared and forgotten.
When the auditor asks for proof, it's already there — logged, attributable, and exportable.
Show an auditor you're ready.
Book a walkthrough with our team, or tell us what you're trying to solve.