How the operating day runs in FlyerOS

The operating day is one board that moves a flight through its stages: booked, checked in, dispatched, airborne, returned, closed. Each stage has a job, and one gate before dispatch stops a flight that should not go.

The stages

1. Checked in. The people arrive and the flight is confirmed as going ahead.
2. Pre-dispatch gate. FlyerOS re-checks the flight against the state right now, serviceability, currency, weather-driven changes, and will not release it if something has changed since it was booked.
3. Dispatched. The gate has passed; the flight is authorised to go.
4. Returned. The aircraft is back.
5. Closed out. Times and counters are recorded and the record is signed.

Why the gate exists

A booking was valid when it was made, but the world moves, a snag is raised, a medical lapses. The pre-dispatch gate is the last check against reality, so a problem is caught at the desk rather than at the aircraft.

A clean close-out

Closing a flight records what it did, times, counters, and the sign-off, as a by-product of the day. That is what keeps the training record and the aircraft's hours correct without anyone typing them in twice.