Flight logger

The Flight logger guides the user through a structured departure or arrival flow.

Departure flow

The usual departure sequence is:

1. choose the route as NAV or LOCAL
2. enter the route aerodrome information
3. enter flight details such as time, POB, PIC, and remarks
4. select the aircraft or enter aircraft details manually
5. review the overview page
6. register the departure

Arrival flow

The usual arrival sequence is similar, but focuses on closing the active flight:

1. review the route and flight details
2. confirm or adjust aircraft and Hobbs information
3. add remarks if needed
4. report a defect when required
5. review the overview page
6. register the arrival

Aircraft and Hobbs

When the flight is linked to a rental aircraft, the logger can ask for:

• aircraft registration and type
• Hobbs at departure
• Hobbs start and end at arrival

The exact Hobbs format depends on the aircraft.

Defects in the arrival flow

On arrival, the app can show a defect reporting card. When used, the user can:

• switch defect reporting on
• enter a short defect title
• describe the issue
• attach photos from the device or camera

Operational checks users may encounter

• the app can show open defects before departure
• the app can prevent departure when the aircraft is unavailable for use
• some buttons may be disabled until the required information is complete

Good practice

• register departure as close as possible to the actual departure time
• register arrival immediately after landing
• keep remarks short and factual
• use clear defect titles and add photos when they help