Live status

The live status view is the core of the Flights module. It presents a real-time list of flights with their current status, making it the primary tool for monitoring active operations at the aerodrome.

What you see first

When you open the Flights module, the flight list is displayed with the following columns:

Open versus closed flights

The most important distinction in this module is the flight status:

What an open flight means in practice

An open flight is not automatically an error. It can represent several situations:

• The flight is genuinely still in the air and has not yet landed
• The pilot has landed but has not yet completed the arrival flow in the Pilot App
• The arrival flow was interrupted or skipped, leaving the flight in an open state that requires follow-up
• A technical issue prevented the arrival from being recorded

Using the flight list for operational monitoring

The flight list is designed to give you fast answers to common operational questions.

Who is currently flying?

1. Open Flights.
2. Look for all flights with open status.
3. Review the PIC, aircraft registration, and route for each open flight.
4. This gives you an immediate picture of who is in the air and where they are headed.

Which aircraft are currently active?

1. Open Flights.
2. Look for open flights.
3. Note the aircraft registration and aircraft type columns for each open flight.
4. Any aircraft shown on an open flight is currently committed to that flight and should not be dispatched for other operations.

When is a flight expected to return?

1. Find the open flight in the list.
2. Note the departure time and the route (departure and destination airfields).
3. Estimate the expected return time based on the route distance and typical flight duration for that aircraft type.
4. If the flight has been open significantly longer than expected, consider following up (see Follow-up and troubleshooting).

Has a specific flight been completed?

1. Open Flights.
2. Search for the flight by PIC, aircraft registration, or route.
3. Check the status column.
4. If the status is closed and both departure and arrival times are present, the flight has been completed.
5. If the status is open, the flight has not yet been fully closed out.

Reviewing open flights during operations

During busy operational days, it is important to review open flights regularly rather than waiting until the end of the day:

1. Open the flight list.
2. Scan the status column for open flights.
3. For each open flight, compare the departure time against the current time.
4. If a flight has been open for a reasonable duration given its route, no action is needed yet.
5. If a flight has been open much longer than expected, investigate further — the pilot may have landed without completing the app flow, or the flight may need operational attention.
6. Prioritise follow-up for flights that are significantly overdue, as these may indicate a safety concern or an app issue that needs resolution.

Good practice

• Review open flights regularly during busy operations, not just at the end of the day
• Use the flight list as a live status board for real-time awareness of what is in the air
• Evaluate open flights in context — consider the departure time, route, and expected duration before deciding that something needs attention
• Do not treat every open flight as a problem; many will close naturally as pilots complete their arrival flows
• Compare the timing and route carefully before concluding that a flight is missing a close-out
• Use this module for operational monitoring, not as a replacement for detailed aircraft history — switch to Fleet when you need aircraft-specific data
• Coordinate with flight instructors on training flights that remain open longer than expected, as the flight instructor may have additional context about the flight plan