Operational follow-up

This page explains how to work with movements that were created automatically by the Pilot App, how to verify that the register is complete, and when to continue your follow-up work in another module.

Working with app-created movements

The Pilot App creates movement entries automatically as part of the normal flight flow. When a pilot completes a departure or arrival in the app, the corresponding movement appears in the Flight register without staff needing to enter it manually.

This means that on a typical operational day, the register will already contain most of the movements you expect to see. Your role as an administrator or flight instructor is to verify that the register is complete and accurate, and to add or correct entries only where necessary.

What arrives automatically

• Flight departures — created when a pilot initiates a departure through the Pilot App
• Flight arrivals — created when a pilot completes an arrival through the Pilot App

What may still need manual attention

• Airfield openings and closings — these are aerodrome-level actions that are not typically initiated by individual pilots through the app
• Movements by visiting aircraft — transient aircraft that do not use the Pilot App will not have automatic entries
• Corrections to app-created entries — if the app captured incorrect details (for example, a wrong route or time), the entry may need manual correction
• Movements where the app flow was interrupted — if a pilot started but did not complete the app flow, the movement may be partially recorded or missing entirely

Typical follow-up tasks

Verify that movements were registered

This is the most common follow-up task. You are checking that the register reflects what actually happened at the aerodrome.

1. Open Flight register to view the movement list.
2. Review the entries for the current day or the period in question.
3. Compare the listed movements against what you know happened operationally — for example, which aircraft departed, which arrived, and at what times.
4. Search by aircraft registration or PIC if you need to find a specific movement.
5. If a movement is present and correct, no action is needed.
6. If a movement is missing, add it manually (see Manual entries and export).
7. If a movement is present but has incorrect details, correct the entry.

Add missing entries

When you identify a movement that should be in the register but is not:

1. Confirm the movement is genuinely missing by searching the register thoroughly.
2. Gather the correct details — movement type, date, times, aircraft, route, PIC, and POB.
3. Use Add Reg. from the module navigation to create the entry.
4. Fill in all fields accurately and save.
5. Verify the new entry appears in the correct position in the movement list.

Check register completeness at the end of the day

Performing an end-of-day review helps ensure that the register is a reliable record:

1. Open the movement list and filter or scroll to the current day.
2. Count the number of departure and arrival entries and compare against the known flight activity for the day.
3. Check that any airfield opening and closing entries are present with correct times.
4. Look for entries with missing fields, such as a departure with no corresponding arrival or an entry with no PIC recorded.
5. Address any gaps or errors before closing out the day.

When to continue in Flights

Continue in Flights when your question is about whether a flight is still open or has been completed. The Flights module is the live operational status board and is designed for monitoring active flight state.

Specific reasons to switch to Flights:

• You want to see which flights are currently open and have not yet been closed
• You need to check the live status of a flight that departed but has not yet arrived
• You want to investigate whether a pilot completed their arrival flow in the app
• A flight appears to have been going on for too long and you need to follow up on its status

The Flight register tells you what movements were recorded. Flights tells you whether a flight is still operationally active.

When to continue in Fleet

Continue in Fleet when your question moves beyond the aerodrome record and into aircraft-specific territory. The Fleet module is designed for aircraft history, maintenance context, and billing.

Specific reasons to switch to Fleet:

• You need the full flight history for a specific aircraft, not just the movements at this aerodrome
• You need Hobbs time data for maintenance scheduling or billing
• You are following up on a defect or maintenance item related to the aircraft
• You need dispatch-related information or aircraft availability status
• The follow-up involves financial or billing questions related to flight time

The Flight register tells you what happened at the airfield. Fleet tells you what happened with the aircraft.

Understanding the boundary

A useful way to decide where to work is to ask yourself what the question is really about:

• "Was this movement recorded at the aerodrome?" — stay in the Flight register
• "Is this flight still going on?" — switch to Flights
• "What is the flight history for this aircraft?" — switch to Fleet
• "Does this aircraft need maintenance attention?" — switch to Fleet
• "Did the pilot complete the arrival in the app?" — start in Flights, then check the Flight register if needed

Good practice

• Use the Flight register for aerodrome registration work, not for aircraft maintenance or billing
• Treat the register as the official local movement record, even when most entries arrive automatically from the Pilot App
• Review the register regularly during and after operations to catch missing or incorrect entries early
• When you spot a gap, resolve it promptly rather than leaving it for later
• Switch to the more specialised module as soon as your question is no longer about the aerodrome record itself
• Coordinate with operations staff and flight instructors to verify movements you did not directly observe before making corrections
• Keep a consistent routine for end-of-day register reviews on busy operational days