Military Airfields / Airfield Status

Airfield Status

Live runway, NAVAID, and Weather status the whole base works from: one screen, always current.

The problem

One board, or five different versions of the airfield

A runway closure, a NAVAID outage, a bird watch condition upgrade. Each one matters to the tower, to command post, to the fire department, and to whoever is about to launch. When that information moves by radio call and hallway conversation, the versions drift: one office is still working off the last update while another already knows about the next one.

Airfield Management personnel end up relaying the same status to several different offices in several different ways, on top of everything else the shift requires.

How it works

Every status, one board, updated live

  1. 01

    Every status on one screen

    Runway status, NAVAID status by runway end, ARFF readiness, current weather, construction and closures, personnel and contractor escorts, and transient aircraft on the field all render on the same board.

  2. 02

    Changes push to every screen instantly

    The board updates in real time: a status change lands on every open screen without a refresh, with an automatic fallback check in the background in case a connection drops.

  3. 03

    Status changes happen on the board itself

    Click a runway, NAVAID, or field-condition chip, choose the new status, add a note if the situation calls for one. No separate form to open.

  4. 04

    A record forms without anyone writing it down

    Every status change also lands in the events log automatically, creating a picture of the day's events.

Airfield Status board showing runway, NAVAID, ARFF, and field-condition status for a demo airfield
The Airfield Status board for a demo airfield: Runway 01 open with RSC Dry and BWC LOW, NAVAID status broken out by runway end, and ARFF readiness at a glance, alongside current weather, construction closures, and transient aircraft on the field.

The benefit

What it automates

One board for every office

The tower, command post, fire response, and maintenance read the same status the instant it changes, not several phone calls behind each other.

No separate form for a status change

Updating a runway, NAVAID, or field condition happens on the same chip you're already looking at, with a note attached if the situation needs one.

A record forms itself

Status changes write to the events log automatically, so there's a trail of what changed and when without an extra step for anyone.

Related

Works alongside

FAQ

Straight answers

Does the board update automatically, or does someone have to refresh it?

It updates in real time: a status change pushes to every screen with the board open, with a short automatic check running in the background as a backup.

Who can change a status?

Update access is permission-gated: the permission matrix decides who can update the board, whether that's the Airfield Manager or whichever other roles your base assigns it to.

What shows up on the board besides runway and NAVAID status?

ARFF readiness, current weather, construction and closures, personnel and contractor escorts on the airfield, and transient aircraft awaiting departure.

Does changing a status create a permanent record?

Yes. Status changes write to the events log automatically, so there's a record of what changed and when without any extra step.