Military Airfields / ACSI
Airfield Compliance and Safety Inspection (ACSI)
Airfield Compliance and Safety Inspection records with automated report creation.
A once-a-year inspection that can't afford to lose a finding
The Airfield Compliance and Safety Inspection runs ten sections and roughly a hundred items, each citing the regulation it verifies. Spread that across several inspectors over several days and the real risk isn't missing an item on the page. It's losing track of who verified what, and whether a finding from day one ever made it into the record.
One long inspection, still one continuous record
Ten sections, worked as a team
Add inspectors, SMEs, and observers to the team roster and everyone works the same draft (pavement, markings, signs, lighting, and the rest), auto-saving as each item gets answered.
A failed item opens a finding, or links one you already have
Mark an item Fail and a discrepancy panel opens on it immediately: write a new finding with a comment, photos, and a map pin, or link an existing entry straight from the Discrepancy Log so the location, photos, and description carry over instead of getting retyped.
Export the report and streamline coordination
One click exports every discrepancy, remark, photo, and DAFMAN 13-204 requirement into a single formatted PDF. Add a digital signature block and route for coordination.
One fiscal year, one filed record
Glidepath enforces exactly one completed ACSI per base per fiscal year, so the certification on file is never in question.
What it automates
One draft, not several inspectors' separate notes
Everyone on the team roster works the same draft in real time, so nobody reconciles separate notes into one file at the end of a multi-day inspection.
Link Existing turns a repeat finding into one click
A finding already open in the Discrepancy Log attaches to the ACSI item directly, so the ACSI record carries that discrepancy as its own evidence instead of describing the same finding twice. Do it once, call it done.
Straight answers
Can a fiscal year end up with more than one completed ACSI?
No. Glidepath enforces exactly one completed ACSI per base per year at the database level, so there's never a question of which copy is the record.
What happens when an item fails?
A discrepancy panel opens on that item immediately: write a new finding with photos and a location, or link one that's already in the Discrepancy Log so its details carry over instead of being retyped.
Can more than one inspector work the same ACSI?
Yes. Add inspectors, SMEs, and observers to the team roster and everyone works the same draft, which auto-saves as items get answered.
What blocks the file button?
An unanswered item, a failed item without a documented risk control measure, or Risk Management not identified. All three have to be clear before the ACSI can be filed.