Civilian Airports / Modifications & Exemptions
Modification of Standards & Exemptions Tracking
Modification of standards requests and Part 139 exemptions tracked from submission to a documented decision.
The problem
A modification or an exemption request needs a record before it needs an answer
A modification of standards request or a Part 139 exemption doesn't move because someone remembers to follow up on it. It moves because there's a decision to track toward: submitted, under review, approved, or denied, with the reasoning and the documentation attached to whichever one it lands on.
Right now, that request lives wherever it was originally filed: an email thread, a scanned letter, someone's memory of a call with the district office. Finding it again later, or proving when and how it was decided, means that trail has to survive as long as the decision itself does.
How it works
Built to track a request from submission to a decision
- 01
Every request carries its own status
A modification of standards request or an exemption gets a status of its own (submitted, under review, approved, or denied) instead of living in whoever's inbox it started in.
- 02
The decision keeps its documentation attached
Approval or denial carries its own paperwork and date, so the reasoning behind a decision doesn't have to be reconstructed later from memory.
- 03
Tied to the specific standard it modifies
A request references the exact design standard or requirement it's asking to modify, so the record shows precisely what's different from the baseline, and why.
- 04
Ready before an inspector asks for it
A modification or exemption record is ready to produce the moment it's asked for, not reassembled from wherever it happened to be filed.
The benefit
What it automates
Nothing tracked only in an inbox
A request's status lives in one record instead of an email thread, so it survives a change in staff or a gap in memory.
A decision that explains itself
Approval or denial carries its documentation and date with it, so the reasoning is part of the record instead of a separate search.
Tied to the standard, not just a filing
Every request references the specific standard it modifies, so the record shows what's different from the baseline at a glance.
FAQ
Straight answers
What counts as a modification of standards?
A request to deviate from a specific FAA design or safety standard for a documented reason, tracked from submission through a final decision.
Does this track exemptions differently from modifications?
Both move through the same status track (submitted, under review, approved, or denied), with the documentation behind each decision attached to it.
What happens once a request is decided?
Approval or denial locks in with its own date and supporting documentation, so the decision is part of the permanent record, not a separate file to track down.
Does a request reference the specific standard it modifies?
Yes. Each request ties back to the standard or requirement in question, so the record shows exactly what's being modified and why.