This article explains how to complete and validate Flight Log entries in Portside Horizon, including how to correctly record times, flight phases, and takeoffs/landings.
It also explains common validation errors, such as mismatched takeoff and landing cycles.
From the main menu:
Trips → Flight Log → [Select Flight Log Entry]
(Reference: Screenshot – Flight Log Entry Example)
The Flight Log screen is where pilots and dispatchers record the operational details of a flight segment.
It includes:
Flight times (Out, Off, On, In)
Flight phases (Instrument, Night, Training, etc.)
Takeoffs and landings (Day/Night)
Operational events (Holds, RNAV, Diversion)
Accurate data entry here ensures compliance, flight time tracking, and maintenance record integrity.
| Flight Log # | Sequential flight log identifier (e.g., 1). |
| Departure / Arrival Airports | The IATA or ICAO codes for origin and destination (e.g., KTUL → KAPC). |
| Save / Cancel Buttons | Use Save to record progress or Cancel to discard unsaved edits. |
Each flight segment includes Out, Off, On, and In times, all logged in UTC.
| Out | Time aircraft leaves the gate or parking (brakes released). |
| Off | Time aircraft becomes airborne. |
| On | Time aircraft touches down on landing. |
| In | Time aircraft arrives at the gate or parking (brakes set). |
Under the time section, additional fields track flight conditions and types of operation:
Field | Purpose |
| Instrument / Simulated Instrument | Time spent under instrument flight conditions or simulated IMC. |
| Night | Duration of flight conducted during night conditions. |
| Training | Time logged for training purposes. |
Tracks total day/night takeoffs and landings.
Values entered here must align with the total airframe cycles for the flight.
Field | Description |
| T/O Day / T/O Night | Number of takeoffs during day/night. |
| Ldg Day / Ldg Night | Number of landings during day/night. |
| Holds / P-RNAV | Optional fields for procedures performed during flight. |
| T&G (Touch-and-Go) | Number of touch-and-go maneuvers completed. |
| Diversion / Divert Reason | Checkbox and notes if flight diverted from planned route. |
Field | Meaning |
| Dep Taxi | Taxi-out duration before takeoff. |
| Arr Taxi | Taxi-in duration after landing. |
| FT (Flight Time) | Calculated from “Off” to “On” times. |
| BT (Block Time) | Total time from “Out” to “In” (gate-to-gate). |
Example:
Out: 20:00 → In: 23:00 = 3:00 Block Time (BT)
Off: 20:06 → On: 22:54 = 2:48 Flight Time (FT)
When saving, Horizon automatically validates entries to ensure data consistency.
If discrepancies are detected, warning messages will appear in red as depicted in the screenshot below.
| Error Message | Meaning | Resolution |
|---|---|---|
| ⚠️ “Total takeoffs for all pilots must equal airframe cycles.” | The number of takeoffs entered for all pilots does not match the total recorded cycles for the aircraft. | Review and correct total takeoffs so the aircraft cycle count equals total takeoffs across pilots. |
| ⚠️ “Total landings for all pilots must equal airframe cycles.” | The number of landings does not match the aircraft’s cycle total. | Ensure each flight’s logged landings equal the aircraft’s recorded landings. |
Review all time fields for accuracy.
Ensure takeoffs and landings match total aircraft cycles.
Confirm that all required flight phases are filled in.
Click Save to finalize the entry.
If validations fail, error messages will appear in red until corrections are made.
Always record times in UTC to ensure consistency across systems.
Log Out/Off/On/In immediately after each event to minimize errors.
Double-check day vs. night classification for accuracy in pilot logbooks.
Maintain matching takeoff/landing counts for airframe tracking integrity.
Use the Divert Reason field for any unplanned destination changes to aid reporting.
Field | Value |
| Flight Log | 1 |
| Route | KTUL → KAPC |
| Out / Off / On / In (UTC) | 20:00 / 20:06 / 22:54 / 23:00 |
| T/O Day / Ldg Day | 1 / 1 |
| FT / BT | 2:48 / 3:00 |
| Warnings | None (all cycles match) |
Section | Purpose |
| Flight Times | Records Out/Off/On/In events to calculate flight and block times |
| Flight Phases | Tracks conditions such as Instrument, Night, and Training |
| Takeoffs & Landings | Ensures takeoff/landing counts match airframe cycles |
| Validations | Prevents mismatched data and ensures accurate reporting |
A flight departs KTUL at 20:00 UTC and arrives KAPC at 23:00 UTC.
Pilots log 1 day takeoff and 1 day landing with no night flight or diversions.
When saved, no validation errors appear, confirming that airframe cycles = 1 takeoff + 1 landing.