Military Airfields / ACSI

ACSI

Airfield Compliance and Safety Inspection records with automated report creation.

Request a demoDAFMAN 13-204 V2

The problem

A once-a-year inspection that can't afford to lose a finding

The Airfield Compliance and Safety Inspection runs across ten sections and roughly a hundred items (pavement, clearances, markings, signs, lighting, wind cones, obstructions, arresting systems), 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.

Documenting and maintaining an annual ACSI has never been easier.

How it works

One long inspection, still one continuous record

  1. 01

    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.

  2. 02

    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.

  3. 03

    Export the report and streamline coordination

    With one click, all discrepancies, remarks, photos and requirements from DAFMAN 13-204 are automatically exported in a single, professionally formatted PDF file. Add a digital signature block and route for coordination.

  4. 04

    One fiscal year, one filed record

    Glidepath enforces exactly one completed ACSI per base per fiscal year, so the certification that's actually on file is never in question.

ACSI list showing one completed inspection for a demo airfield
The ACSI list for a demo airfield, headed "Airfield Compliance and Safety Inspection" with its DAFMAN 13-204v2, Para 5.4.3 cite underneath: summary cards reading 1 Total, 1 Completed, 0 In Progress, 0 Drafts sit above All/Draft/In Progress/Completed/Staffed filters and a search box, with the fiscal year's filed inspection (ACSI-2026-A4F7 for Demo AFB, 2026, dated 2026-07-04) carrying 183 passed, 2 failed, 0 N/A, a Completed badge, and a Reopen action.

Built on the regulation

The citation, implemented

  • DAFMAN 13-204 V2, Para 5.4.3

    The ten-section checklist, the discrepancy linkage, and the once-a-year filing rule all implement the Airfield Compliance and Safety Inspection the paragraph requires.

The benefit

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. No more manually adding discrepancies and supporting information. Do it once, call it done.

Related

Works alongside

FAQ

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.