Military Airfields / Inspections
Inspections
Daily airfield and lighting inspections marked by exception, plus construction and joint-monthly records, aligned to DAFMAN 13-204.
The problem
An inspection is only as good as what it catches, and what it proves afterward
A daily airfield or lighting inspection touches dozens of items (runway surface condition, bird watch condition, every light and marking), and the ones that matter are the ones marked wrong, not the ones that passed. Losing a failed item in a long list, or forgetting to log it before moving on, is how a real discrepancy goes unrecorded.
A construction or joint-monthly inspection isn't an item checklist at all (it's a record of who attended and what was discussed), so it needs its own format, not a checklist that doesn't fit the meeting. Perfect for streamlining documentation requirements.
How it works
Built around DAFMAN 13-204 V2 and UFC requirements
- 01
Work through the checklist, exceptions only
Click to document a failed item. Bird watch condition and runway surface condition are the two entries every airfield inspection actually requires; everything else, you only touch what's wrong.
- 02
A failed item opens its own record on the spot
Mark an item Fail and a discrepancy stub opens right there (a comment, a photo, a location) without leaving the inspection. Decide then whether to log it as a discrepancy; file the inspection and that decision is locked in.
- 03
Runway condition feeds the status board
Log a runway condition reading during the inspection and it carries straight through to the Airfield Status board. Nobody re-enters it a second time.
- 04
Construction and joint-monthly get their own format
These aren't item checklists: they're a record of who was there, what was covered, and the photos to back it up, filed in the same history as every other inspection.
Built on the regulation
The citation, implemented
- DAFMAN 13-204 V2
The daily airfield and lighting checklist, its required bird watch and runway surface condition entries, and the one-inspection-per-day rule are all built around what the regulation requires of the record.
The benefit
What it automates
One inspection a day, highlighted on a user's dashboard
Easily identify whether the daily inspections have been completed and who completed them. If an inspection is in-progress, who to reach out to with the status of completion.
Exception marking keeps you moving
Every item defaults to Pass: you only stop to mark what fails, so a routine inspection moves as fast as it should.
A record that holds up
Export or email a completed inspection as a PDF report, attributed and dated, ready the moment anyone needs to see it.
Related
Works alongside
FAQ
Straight answers
Do I have to mark every single item, even the ones that pass?
No. Every item defaults to Pass. You only touch the ones that fail. Bird watch condition and runway surface condition are the two entries every airfield inspection actually requires.
What happens when I mark an item as failed?
A discrepancy stub opens right there in the inspection: add a comment, a photo, a location, and choose whether to log it as a discrepancy before you file.
Do construction and joint-monthly inspections use the same item checklist as the daily inspection?
No. Those are a different record (who attended, what was covered, and photos), filed alongside the daily inspections in the same history.
Can two people start the same inspection twice in one day?
No. Glidepath blocks a second same-type inspection for the same day, enforced in the app and backed by a database rule.