Military Airfields / Driving Spot Checks
Airfield Driving Spot Checks
Random driving enforcement checks with AF Form 483 verification, pass-rate trending, and a board-ready PDF.
Enforcement checks deserve more than a free-text log entry
DAFI 13-213 and the local wing supplement expect the driving program to be enforced, and most airfields document that enforcement as a one-line entry in the Events Log. A line of free text can't answer the questions the Airfield Operations Board asks: how many checks ran this quarter, what the pass rate was, and which discrepancies keep showing up.
Without a structured record, the check itself varies with whoever conducts it. One person verifies the AF Form 483; another doesn't think to.
A structured check with a computed outcome
Identify the driver
Name, rank, unit, and office, with a contractor lookup that prefills the driver's details and AF Form 483 expiration straight from the Personnel on Airfield record.
Verify the credential and the vehicle
The AF Form 483 status (Valid, Expired, Not in Possession, None Issued) is its own dedicated field on every check, alongside the vehicle type and ID.
Work the locally configured item list
Each check item your base configures is toggled Pass, Discrepancy, or N/A, and a Discrepancy can't be saved without notes describing it.
The outcome computes itself
Anything other than a valid 483, or an observed violation, grades the check a Violation; otherwise a Discrepancy item grades it a Discrepancy; otherwise it's a Pass. The result posts to the Events Log as a one-line summary.
What it automates
The AOB report writes itself
One PDF export covers total checks, pass rate, the most common discrepancy items, and a by-checker breakdown for any date range, ready for the Airfield Operations Board.
A computed outcome, not a judgment call
Pass, Discrepancy, or Violation is derived from the 483 status, the item results, and the violation flag, so two checkers grading the same stop reach the same result.
History that survives item-list changes
Every logged check keeps its item labels as they read when it was logged, so renaming or retiring an item never rewrites what was checked.
Straight answers
How many spot checks can run per day?
Checks are random and unbounded; there's no one-per-shift limit. Log as many as enforcement calls for.
Where do the check items come from?
They're configured per base in Base Setup, with a default starting list (radio contact, tire FOD check, beacon and lighting, seat belts, speed compliance, and more) meant to be renamed, reordered, or replaced to match the local wing supplement.
What makes a check a Violation?
Any AF Form 483 status other than Valid, or the airfield driving violation box checked with a description. Item discrepancies alone grade the check as a Discrepancy.
Does a spot check reach the Events Log?
Yes. Saving a check posts a one-line summary (driver, unit, 483 status, outcome, location) to the Events Log automatically.