1. Create the correct record
Open the flight form in the logbook and choose an actual flight. Confirm date, aircraft and airports. Simulator and duty activities have different fields and totals.
2. Check the time zone
Review the form UTC/local configuration before entering times. Use a coherent reference and check departure and arrival zones when using local times.
3. Enter the events in order
Out is off-block, Off is takeoff, On is landing and In is on-block. Check chronological order, especially for flights crossing midnight.
4. Review calculated durations
Block time is In minus Out; airborne time is On minus Off. The engine normalizes sequences crossing to the next day. Also review roles and flight conditions.
5. Save and inspect
Complete required fields, save and inspect the flight in the logbook. For stopovers, review each leg and the total. Keep duty time distinct from flight time.
Demonstration example
Demonstration in a single UTC reference: Out 10:00, Off 10:12, On 11:18, In 11:30. Block time: 01:30 (1.50 h). Airborne: 01:06 (1.10 h). Taxi before and after: 00:12 each. Decimal digits do not represent minutes.
Before you finish
- Date, UTC/local configuration and airports are correct.
- Out → Off → On → In is a coherent sequence.
- Block and airborne times are distinguished.
- Duty, simulator and actual flights use their own categories.
Frequently asked questions
Is 01:30 the same as 1.30 hours?
No. Thirty minutes is half an hour, so 01:30 equals 1.50 decimal hours.
What should I check when crossing midnight?
Check the base date, time zones and event order. The app normalizes the sequence, but you should verify that it represents the actual flight.