How it works
Public data, no scraping fragility, honest about its limits.
1 · Live AD feed
We poll the Federal Register public JSON API daily for FAA final rules under 14 CFR Part 39 (that's what an AD legally is). Each AD's full text is parsed for the applicable make/model/series, effective date, and compliance window.
2 · Match to your fleet
You add aircraft by make + model (+ optional serial and current hours TIS). We match each AD's applicability against each tail.
3 · Deadlines + status
For recurring ADs we compute the next-due date or hours from the effective date (or your recorded last-compliance). You record method-of-compliance per AD; the status board and audit export follow.
Honest limits
Make/model/series matching is reliable. Serial-exact applicability often depends on a manufacturer Service Bulletin we cannot see in the public AD text, so a model-level match may over-include. We flag match confidence and tell you to verify with your A&P/IA. This is a tracking aid, not a maintenance record.