Aircraft Journey Log Entry Example: One Flight

What does a clear aircraft Journey Log entry look like after one ordinary flight in your own aircraft? The example below starts with the source facts, turns them into one completed aircraft-centred row and then checks what the owner can understand when returning to the record before a later flight.

The flight, aircraft identifier, person and aerodromes are fictional. The row is illustrative, not an approved form or a universal list of required fields. Actual particulars depend on the operation, aircraft, applicable rules, national requirements and the aircraft's record system.

For the wider operating rhythm around the row, read the aircraft Journey Log guide.

What does the finished entry look like?

This is a simple daytime Part-NCO flight in a light aeroplane owned and flown by Pilot A, whose continuing airworthiness is managed under Part-ML. Pilot A is both the owner and PIC for this flight, but those remain distinct legal roles. All clock times are UTC on 14 July 2026.

This row does two jobs without trying to do everything. It preserves the flight facts, then points to a separate report for an observation that needs follow-up. It does not diagnose the light, decide whether the aircraft may fly again or claim maintenance rectification.

Which source facts should be captured first?

Before calculating anything, preserve the values available immediately after the flight:

• the calendar date used by the record system;
• the aircraft's actual nationality and registration marks or other required identity;
• crew names and duties, where applicable;
• departure and arrival places;
• each recorded event time and its time standard;
• the raw start and end reading of the named aircraft counter;
• take-off and landing counts;
• the nature of the flight;
• the PIC's factual account of any incident or observation; and
• the PIC's confirmation under the method used by the record system.

This order matters. If the raw counter reading is replaced immediately with a calculated duration, the record loses information about its source. If local time is entered without a time zone, a later reader may not know whether a conversion was already applied. If an observation is rewritten as a diagnosis, the record stops reflecting what the pilot actually saw.

Within the relevant Part-NCO scope, NCO.GEN.150 requires specified aircraft, crew and journey particulars to be retained for each flight or series of flights in a Journey Log or equivalent. Its associated AMC describes particulars that should be included where applicable, such as nationality and registration, date, crew names and duties, departure and arrival places and times, flight hours, nature of flight, incidents and observations, and the PIC's signature. The AMC is an acceptable means of compliance, not wording that makes every illustrated field universally statutory in every context.

How are block time, airborne time and the counter different?

The four event times support two useful durations in this fictional example:

Illustrative arithmetic, not a universal aircraft-counter rule.

Block time here means the interval from off-block to on-block. It includes ground movement before take-off and after landing.

Airborne time here means the interval from take-off to landing. It does not include those ground intervals.

The tach-hour meter is the named source used in this fictional aircraft's record process. Its change of 1.2 tach hours equals 72 tach minutes in that counter's decimal basis. It still does not equal the flight's 1 h 20 min block time or 1 h 04 min airborne time, because an installed counter may advance on a basis different from elapsed clock time. That basis must come from the instrument and aircraft documentation.

Maintenance-relevant time or cycles are the values and definitions used by the applicable maintenance data and aircraft records. A maintenance threshold may depend on flight time, operating time, cycles, landings, calendar time or another defined measure. The Journey Log writer should preserve the appropriate source data, not invent a conversion from whichever number is most convenient.

The lesson is to label every value. “Time: 1.2” is ambiguous. “Tach start 1254.6, tach end 1255.8, unit: tach hours” preserves what was read. Whether and how that counter feeds a maintenance status calculation is a separate, aircraft-specific question.

How should the row be built step by step?

1. Identify the aircraft and flight

Use the aircraft identity required by the actual record system, plus the correct calendar date. The fictional FICTIONAL-A1 label above prevents this teaching example from being mistaken for a real aircraft record.

2. Identify people by duty

“Pilot A — PIC” is more useful than an unexplained name. No personal flight-time credit or qualification is inferred. A Journey Log is not the place to decide what time an individual may claim in a personal logbook.

3. Enter places and UTC event times

The sequence should be possible: off-block, take-off, landing, on-block. Here, each event occurs on the same UTC date. A flight crossing midnight needs explicit date handling rather than an assumption that a clock value that appears smaller occurred earlier.

4. Preserve counts and counter readings

The flight has one take-off and one landing. Both the start and end counter readings are retained. This lets a later reviewer verify the arithmetic and spot a transcription error instead of seeing only a derived total.

5. Describe the nature of flight

“Private, daytime cross-country” gives operational context without inventing a commercial purpose or training credit. Use the categories chosen for the aircraft's records rather than free-form labels that drift over time.

6. Add observations in neutral language

The pilot recorded a post-flight ground-check result: the right landing light did not illuminate. The row says when and where it was noticed, avoids a diagnosis and references separate report DR-014.

That reference does not authorise further flight. The next step is assessment under the applicable operational and continuing-airworthiness context. The aircraft defects under Part-ML article explains the boundary between report, qualified decision and rectification evidence.

7. Complete PIC confirmation

The example describes a confirmation event instead of displaying a fake handwritten signature. In a real record, use the applicable signature or confirmation method and preserve its link to the person and entry.

Logga's current Journey Log supports PIC signature and PDF export. That makes it possible to confirm an operational entry and export the current record. The signature does not serve as maintenance release evidence, and the PDF is not by itself proof that every applicable requirement has been satisfied.

What should the owner be able to tell before the next flight?

A later reader—including Pilot A returning for the next flight—should be able to reconstruct the aircraft's recent use without relying on memory to decode the row:

The row should not display a green “complete” state that makes the separate report look resolved. Completion of the flight entry and closure of the reported issue are different events.

What are the most common mistakes?

• treating the aircraft row as a personal pilot logbook;
• leaving the time standard implicit or using one label for different time bases;
• converting a counter without preserving readings, units and source;
• writing a diagnosis instead of a factual observation;
• equating PIC confirmation with maintenance release; and
• closing the flight row while hiding its open report.

A later correction should preserve or leave legible the original value, show the corrected value, and identify who changed it, when and why. A good aircraft Journey Log entry is not the longest row. It is the row whose source facts, labels and references remain clear months later—to the same owner or to an occasional different pilot.

Contact Logga about setting up the current Journey Log for your aircraft.