Military Airfields / Airfield Checks
One check can encounter several kinds of work
A routine airfield sweep can turn up FOD, a surface-condition change, wildlife activity, or a construction issue. The record needs to keep those observations with the check in progress.
Glidepath starts one Airfield Check, then lets the team record the work encountered without choosing a separate check type before leaving the desk.
Start once, record what the check encounters
Start the airfield check
One Start airfield check button opens the shared workflow. Resume a saved draft when the check is already in progress.
Add the work encountered
Record FOD, surface conditions, wildlife, construction, heavy aircraft, emergencies, or other observations on the same check. Driving spot checks are available when that module and permission are enabled.
Flag a problem without leaving the check
Find something wrong mid-check and mark it on the spot (a comment, a location, a photo) and decide right there whether it becomes a discrepancy. Nothing gets re-described later.
Every check becomes a dated record
Completing a check produces a PDF record naming who completed it and when, archived in the check's history alongside every other completed check, searchable later by type, area, or date.
What it automates
The check follows the situation
Add the relevant observations as the work develops instead of opening separate checks for each subject.
Related findings stay together
The completed record retains the work captured during that check, with its source context.
A complete history, not scattered write-ups
Every check type lands in the same searchable history, attributed to who ran it and when.
Straight answers
Do I choose a check type before starting?
No. Start one Airfield Check and add the work encountered from Record on This Check. Older records retain their original check-type history.
If a check turns up a problem, does it automatically become a discrepancy?
You decide. Flag the issue with a comment, a photo, and a location right where you found it, then choose whether to log it as a discrepancy. Nothing forces the decision either way.
Is there a record of who completed a check?
Every completed check produces a PDF record naming who completed it and when, and it's archived in the check's history alongside every other check.
How is this different from the Shift Checklist?
Shift Checklist covers recurring shift tasks and resets on the installation’s configured schedule. Airfield Checks document situational field work and the observations collected during it.
Connected modules
Inspections
Daily airfield and lighting inspections, pre- and post-construction inspections, and joint monthly inspections, aligned to DAFMAN and UFC requirements.
Discrepancies
Every airfield discrepancy tracked from identification through verified closure.
Shift Checklist
A three-state shift checklist that resets on your base’s configured schedule and preserves prior days in history.