Working with app-created movements
The Pilot App can create movement entries automatically as part of the normal flight flow. That means the register may already contain the aerodrome movement without staff having to enter it manually.
Manual work is still useful when local staff need to:
- correct missing information
- add a local airfield action
- verify what happened from the aerodrome point of view
When to continue in another module
Continue in Flights when you need to know whether a flight is still open or already completed.
Continue in Fleet overview when you need:
- aircraft-side flight history
- defect follow-up
- Hobbs context
- dispatch-related review
Typical tasks
Check whether a movement was registered
- Open
Flight register. - Search by aircraft registration, PIC, or route.
- Confirm whether departure or arrival is present.
- Review remarks if more context is needed.
Add a missing local entry
- Use
Add Reg.from the module navigation. - Choose the correct entry type.
- Fill in the movement details.
- Save and confirm it appears correctly in the register.
Good practice
- use this module for aerodrome registration work, not for aircraft maintenance or billing
- treat the register as the local movement record, even when some entries arrive automatically from the normal flight flow
- switch to the more specialised module as soon as the question is no longer about the aerodrome record itself