Civilian Airports / Records Export
Records Export
Records retention and disposition exports, inspection-ready.
The problem
A record has to outlast the app that produced it
Software that runs daily operations and software that produces a defensible, retained record are two different bars to clear. Plenty of tools manage the first and leave the second as a manual export project the moment a record actually has to leave the system.
"Leaving the system" isn't hypothetical. An inspector's request, a records-retention schedule, or a genuine platform change all eventually ask for the same thing: a complete, filable copy of what happened, not just continued access to look at it.
How it works
Pick a period, pick a format, generate the file
- 01
Any period, from a month to everything
This month, last month, this quarter, this fiscal year, a custom range, or all time (the full "leaving Glidepath" grab), set once and applied across every module selected.
- 02
Choose exactly what the record needs to include
PDF documents, Excel workbooks, photos, an interactive viewer, or raw JSON: any combination switches on or off before anything gets generated.
- 03
Every module, or just the ones that matter
Waivers, inspections, discrepancies, training, SMS, AEP, wildlife, PPR, contractors, and the rest each check independently, so a partial export takes no more effort than a full one.
- 04
Nothing leaves this device to build it
Generation runs entirely in the browser, and the finished ZIP carries a start-here cover sheet and a SHA-256 manifest of every file inside it.
Built on the regulation
The citation, implemented
- 14 CFR §139.301
§139.301 requires the records supporting an airport's certification to be kept and available. The export's PDF, Excel, and photo package, built with a SHA-256 manifest of every file, is that retained record produced on demand instead of assembled by hand whenever it's asked for.
The benefit
What it automates
Every format a records schedule might ask for
PDF, Excel, photos, an interactive viewer, or raw JSON, all selected from one screen instead of hunting down a separate export per module.
A manifest proves what's actually in the export
A SHA-256 hash per file plus a start-here cover sheet mean the package can prove its own contents, not just claim to be complete.
Nothing has to leave the browser to build it
Generation runs entirely client-side, so producing the export doesn't mean handing the underlying data to another service first.
Related
Works alongside
FAQ
Straight answers
Can I export just one module, or does it have to be everything?
Any combination: every module checks independently, so a single module for a narrow date range is as easy as the full "leaving Glidepath" export.
What formats does the export include?
PDF documents, Excel workbooks, photos, an interactive viewer, and raw JSON. Toggle any combination on before generating.
Does record data get sent anywhere to build the export?
No. Generation runs entirely in your browser, so the underlying data never leaves the device producing the export.
How do I know the export is complete once I have it?
The ZIP includes a start-here cover sheet and a SHA-256 manifest listing every file, so its contents can be verified, not just assumed.