A Tuesday at an ATO
Eight aircraft, a simulator, six instructors, sixty students, an eleven-hour day. A booking is a plan, dispatch is the authorisation, and the closed record is the truth — three different things, and the software never confuses them.
Screens referenced are the demo environment (fictional Northstar data).
02:00 — the work that makes 07:00 possible
While the school sleeps, the overnight jobs run per organisation: maintenance due-dates recomputed from yesterday's counters, the next fortnight of confirmed activities re-evaluated against today's facts, the qualification and document expiry sweep, tomorrow's reminders as one digest per person. By morning the impact list already knows what will not fly.
07:00 — operations opens the board
The duty ops lead opens the Today board and, within a minute, knows whether today works: every activity by resource lane, fleet readiness across the top, the disruption panel showing exactly which of today's and this week's activities are now invalid and why, and the decisions to make before the first slot. An aircraft snagged last night already shows grounded — not serviceable on the board and defective in the tech log.
08:45 — the dispatch gate
The most important moment of the day. FlyerOS re-runs the full eligibility evaluation at the moment of dispatch, against current state rather than the projection used when the booking was made: is the aircraft serviceable right now, has maintenance become due, is the instructor inside duty limits as of this minute, are the student's documents valid today. Schedule validity does not guarantee dispatch validity. A dispatcher releases; the pilot in command acknowledges. If a block is overridden, who, why and under what authority is captured — and shown on the record for its lifetime.
10:35 — a defect that moves the schedule
A defect is reported from the aircraft, on a phone, in under a minute. Immediately and without anyone else acting: the aircraft's status changes, every affected future booking is surfaced with genuinely eligible swaps, maintenance and operations are notified, a technical-log entry is created, and the aircraft drops out of dispatch until released. A defect that does not move the schedule is a note, not a defect.
17:30 — the close
Each flight is closed next to the aircraft: off and on blocks, take-off and landing, counters, landings, fuel, outcome. Block and airborne time are derived, not retyped. The close emits everything a future charge would need. The exception queue catches anything left open — no flight is discoverable as unclosed in week three.
All day — next week, invisibly
The planner builds next week in a draft roster nobody else can see until it is published. Publishing validates the whole range, surfaces new conflicts now rather than at 07:00 on the day, and notifies affected people once as a digest.