Category A means grounded.
MEL tracking software that enforces the Minimum Equipment List. Categories A, B, C and D with auto-calculated rectification deadlines. Category A blocks dispatch through the Feasibility Engine the same one that runs crew FTL and CAMO warnings.
MEL tracking that enforces the rule.
Every MEL item, every category, every rectification deadline with dispatch enforcement built in.
A, B, C and D with correct intervals
Category A: before next flight. B: 3 calendar days. C: 10. D: 120. The system tracks the clock; nobody memorises the rules.
Rectification deadlines calculated automatically
Enter the deferral and the category. The rectify-by date populates from the intervals no manual arithmetic, no calendar mistakes.
Category A won't let the trip publish
Live Category A and overdue items are enforced through the Feasibility Engine at trip publish. It's a hard stop, not a soft warning.
On the same check as FTL and CAMO
Every trip pre-check surfaces MEL alongside crew FTL, aircraft availability, document expiry and CAMO warnings. One panel. One decision.
Every open item on the alert stream
Open MELs, approaching rectification dates and overdue items land on the notification bell alongside document expiry and FTL warnings.
Every deferral, every rectification, timestamped
Every state change on every MEL logged with user attribution and timestamp. Audit-ready log for CAA / FAA / GCAA inspection.
Four categories. Four different clocks.
A, B, C and D each have different rectification intervals. The system knows the difference and calculates the deadline the moment the defect is deferred. Deadlines land on the notification bell 3 days out for B, 7 days out for C, and 30 days out for D.
MEL category matrix
MEL runs on the same pre-check as FTL and CAMO.
Every trip publish runs a Feasibility check. Crew FTL, aircraft availability, document expiry, CAMO warnings and MEL all on one screen. If any of them fail, the trip can't publish. See maintenance tracking for the CAMO half of the check, and flight and duty tracking for the FTL half.
Feasibility check · TS-2842
Three ways an MEL in Excel ends the AOC.
Every operator tracking MEL in a spreadsheet has had one of these mornings. Usually the day after it happens.
The Cat A got treated as a Cat B.
Someone deferred an ATA 28 as Category B. It should have been A. The aircraft flew for three days with a legal-on-paper deferral that was illegal on the actual MEL. The inspector found it.
Day four flew a Cat B.
The deferral clock started Monday. Friday flight. Nobody in the flight release chain remembered day 4 was Thursday. Overdue MEL. Regulatory finding. The accountable manager's name on the paperwork.
The maintenance log is in seven places.
MELs tracked in the maintenance provider's spreadsheet. Deferrals emailed as PDFs. Rectifications noted in a WhatsApp. Audit day, the operator can't produce a coherent MEL history because there isn't one.