Civilian Airports / Airport Status
Airport Status
Live field, NAVAID, and surface-condition status your whole operation works from.
The problem
Everyone needs the current picture, and current keeps changing
The active runway, whether it's open, and whether every NAVAID serving it is up can all change inside the same shift, and the operations desk, the tower, and ARFF all need the answer as of right now, not the version relayed by radio an hour ago.
Multiply that across two runway ends, every aircraft type ARFF has to be ready for, and whatever construction or personnel are currently on the airport, and keeping one accurate picture in front of everyone who needs it gets hard the moment something changes and somebody isn't looking at the same screen.
How it works
One status board, current for everyone reading it
- 01
The active runway, front and center
Active runway, open or closed, plus runway surface and bird condition fields, set from the desk that owns the call and visible to everyone else immediately.
- 02
NAVAID status for both runway ends
ILS, glideslope, localizer, and PAPI shown good or down for each end, so an outage is tied to the approach it actually affects, not buried in a general alert.
- 03
ARFF readiness by aircraft type
Every aircraft type the airport serves carries its own readiness state (Optimum down to Inadequate), set with a click and read off the board instead of passed along by radio at shift change.
- 04
Everything else, on the same screen
Personnel currently on the airport, construction and closures, and any miscellaneous notice worth flagging, with current weather and active alerts across the top.
The benefit
What it automates
One current answer, not several versions of it
Runway, NAVAID, and ARFF status live on the same screen operations, the tower, and ARFF all read from, so nobody's working off a version that's already stale.
An outage is visible the moment it's marked
NAVAID status updates the board immediately, tied to the specific runway end it serves, instead of waiting for a separate report to catch up.
ARFF readiness travels with the aircraft, not a shift
A readiness state per aircraft type means the next shift reads it off the board instead of relying on whatever got passed along at handoff.
Related
Works alongside
FAQ
Straight answers
What shows up on the Airport Status board?
The active runway and its status, NAVAID status for both runway ends, ARFF readiness by aircraft type, personnel currently on the airport, construction and closures, and current weather with any active alerts. One screen for all of it.
How current is the information on the board?
As current as the last update. The board reflects whatever the operations desk has entered, and everyone viewing it sees the same version at the same time. There's no separate copy to fall out of sync.
Does it break out NAVAID status by runway end?
Yes: ILS, glideslope, localizer, and PAPI status for each end separately, so an outage is tied to the specific approach it affects.
How does ARFF readiness work on the board?
Each aircraft type the airport serves gets its own readiness state (Optimum, Reduced, Critical, or Inadequate), set with a click and visible to everyone reading the board, not just whoever set it.