Civilian Airports / Traffic Log
Airport Traffic Log
A live log of every aircraft the field is working today, with overdue alerts, movement counts, and public display boards.
The flight log, the tower, and the terminal display never quite agree
The day's movements get kept in a shared spreadsheet at the operations desk, relayed to the tower by phone, and retyped again for anything the public sees. Three copies of the same day drift apart the moment it gets busy, and the traffic count gets rebuilt from whichever copy survived.
And nothing in a spreadsheet watches the clock. An aircraft past its ETA looks exactly like every other open row until somebody happens to notice.
One live log behind every screen at the airport
The flight plan on the left, the actual times on the right
Each traffic category ends in a blank row: type the callsign, pick the aircraft from a search over 2,702 FAA designators (your airport's last 90 days float to the top), set the flight type, and record actuals as they happen. Every keystroke persists; there is no save button.
The ETA computes itself
ETA fills in from ETD plus ETE, then re-derives the moment a departure time is recorded. Everything runs Zulu: the times, the day boundary, the date in the header.
An overdue aircraft raises its own alarm
Five minutes past ETA turns the row amber; past 30 minutes it goes red and a pop-up blocks until answered. Acknowledge quiets it on every screen at the airport, and one press starts your linked overdue-aircraft Emergency Checklist, one execution per flight.
The same entry feeds the tower board and the terminal FIDS
Flight Strips is the tower's working board for entering departure and arrival times. FIDS is the public flight-information display, written plain for travelers: recorded times in green, estimates in grey, under a live Zulu clock. Both run on their own kiosk links.
What it automates
Overdue detection is a rule, not a habit
The two-tier alarm runs on every qualifying row against the Zulu clock. Only a recorded arrival or a corrected ETA clears it, so a quiet screen means nothing is waiting.
Traffic counts generate themselves
Movement tallies by aircraft identifier and by Aircraft Design Group, counted on the date each actual happened, with a Traffic Count PDF and a sixteen-column Daily Logbook PDF on demand.
The day closes itself
Close Day fires automatically at your Zulu rollover: still-open flights carry forward once, and every finished day stays readable in the Logbook calendar without any archiving by hand.
Straight answers
What happens when a flight goes overdue?
Five minutes past ETA the row turns amber; more than 30 minutes past it turns red and a pop-up lists every unacknowledged overdue flight. You can snooze it five minutes on that device, acknowledge it for every screen at the airport, or start the linked overdue-aircraft Emergency Checklist directly from the pop-up.
What does the public terminal display show?
FIDS is written for readers with no aviation background: no initials, no shorthand, no route text, and no overdue markers. Recorded times show green, estimates grey, under a live Zulu clock and a permanent all-times-are-Zulu note. Which categories reach it is a per-category setting.
How are movements counted?
A recorded departure is one movement and a recorded arrival is another, each counted on the date its actual time happened. Traffic Count tallies them by aircraft identifier and by Aircraft Design Group over 7, 30, or 90 days or 12 months.
How does a day end?
Close Day runs itself once Zulu time passes your configured rollover. Still-open flights move forward one day, exactly once, and every finished day stays readable in the Logbook, including its PDF.