Military Airfields / Inspections
Airfield Inspections
Daily airfield and lighting inspections, pre- and post-construction inspections, and joint monthly inspections, aligned to DAFMAN and UFC requirements.
Request a demoAn inspection is only as good as what it catches, and what it proves afterward
A daily inspection needs to show what was inspected, what was unsatisfactory, and what was not inspected. Unanswered items must remain visible so an incomplete check does not read as a passed one.
Glidepath connects checklist answers, findings, photos, and follow-up discrepancies. Construction and joint-monthly inspections retain their own formats and schedules.
Built around DAFMAN and UFC requirements
Record an answer for each inspected item
Answers start blank. Mark satisfactory, unsatisfactory, or not applicable as appropriate. Partial filings identify items that were not inspected.
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.
Update the selected runways
Surface-condition changes recorded during the inspection apply only to the runways selected for it, keeping other runway records intact.
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.
Capture additional findings in place
Record wildlife, construction, surface conditions, heavy aircraft, FOD, emergencies, or driving spot checks without leaving the inspection, where the relevant module and permissions allow it.
What it automates
One inspection a day, highlighted on a user's dashboard
See at a glance whether the daily inspections are complete, who completed them, and who to reach if one is still in progress.
Uninspected items remain explicit
An unanswered item does not default to a satisfactory result. The filed record distinguishes completed inspection work from gaps.
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.
Straight answers
Do inspection items default to satisfactory?
No. Answers start blank. Record satisfactory, unsatisfactory, or not applicable for the work performed; a partial filing identifies items not inspected.
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?
Daily airfield and lighting inspections allow one of each type per installation and operational day. Resume the existing draft if one is underway. Construction and joint-monthly inspections do not have that daily limit.