Civilian Airports / Airport Checks
Airport Checks
FOD, surface, and situational condition checks that run between scheduled inspections, each with its own record.
The problem
The scheduled self-inspection isn't the only time something needs checking
Weather rolls through mid-afternoon. An arrival calls in debris near the threshold. Wildlife shows up close to the approach end an hour before a departure. None of that waits for tomorrow's self-inspection, and none of it fits the self-inspection's checklist either, because each situation is asking about something completely different in the moment it's actually happening.
Handle those as a quick verbal note or a text message and there's nothing to point back to afterward: no record of what was actually checked, what turned up, or who confirmed it. The gap between scheduled inspections still needs its own answer, not a shrug until the next one starts.
How it works
Pick it, run it, file it, without switching tools
- 01
Choose the situation in front of you
FOD, surface condition, an in-flight or ground emergency, a heavy aircraft arrival, a wildlife concern, construction, or something outside all of those: selecting it brings up only the fields that particular situation calls for.
- 02
Answer what that specific check asks
A construction check runs down its own point-by-point list. An emergency check moves through its own sequence of actions. A simpler check is a direct entry. None of them borrow fields meant for a different situation.
- 03
Flag a problem on the spot
Notice something wrong partway through and capture it right there: a note, a photo, exactly where it was found. Whether it becomes a discrepancy is a decision made in that same moment.
- 04
Filed the moment it wraps up
A finished check joins the archive immediately, tagged with who ran it and when, so it turns up again later by its type, its area, or its date.
The benefit
What it automates
Only the fields that situation actually needs
A construction check and a FOD check aren't asking about the same things, so nobody fills in a field that has nothing to do with what they're looking at.
A finding doesn't need retelling
Note it, photograph it, and pin its location once, during the check itself. That's what carries forward if it becomes a discrepancy.
One place to look back on every check
Regardless of type, every completed check lands in the same history, tagged with who ran it and when.
Related
Works alongside
FAQ
Straight answers
How does this differ from the scheduled self-inspection?
Self-inspections are the recurring §139.327 program, run on its own schedule. Airport checks cover whatever comes up outside that schedule (FOD, wildlife, construction, an emergency, and more), each filed on its own.
Does flagging a problem during a check automatically create a discrepancy?
No, that stays a separate choice. The note, photo, and location are captured on the spot; turning it into a discrepancy is a decision made right then, not automatic.
Can I look up who ran a particular check?
Yes. Every entry in the history names who completed it and when, and can be searched by type, area, or date.
What if the situation doesn't match one of the listed types?
"Other" covers it, with a direct entry for whatever the situation actually is.