Aircraft Journey Log Guide for Pilot-Owners

An aircraft Journey Log gives a pilot-owner a dependable account of what has happened to the aircraft and what still needs attention. It is an aircraft-centred record: each flight adds to one continuous history, even when the owner is also the Pilot in Command (PIC) on most flights.

The practical aim is simple. You should be able to recall the last flight, preserve the source values while they are available, coordinate any maintenance follow-up and find the current context before the aircraft is used again. The next pilot may be you on the next flight. If another pilot occasionally flies the aircraft, the same record should also make that handover intelligible.

This guide explains that rhythm for a light aeroplane operated under Part-NCO in the EASA context, with the continuing-airworthiness discussion scoped to Part-ML. It does not turn one screen or form into a universal compliance checklist: the applicable operation, aircraft, national requirements and record system still determine the exact particulars and processes required.

What job does an aircraft Journey Log do?

The Journey Log preserves the sequence of the aircraft's use. A useful entry identifies the flight, associates it with the correct aircraft and PIC, records the selected time and usage values, and captures relevant observations. Read together, the entries help the owner reconstruct what happened without relying on memory, loose paper or a message buried in a chat.

That makes the record useful in three directions:

Backwards: What was the last flight, who was PIC and what values were recorded?
Now: Is there operational context that must be checked before the aircraft is used again?
Forwards: What do I, another pilot or the person coordinating maintenance need to review or escalate?

For operations within Part-NCO's scope, NCO.GEN.105(a)(8) is the important starting point: it places on the PIC the recording of aircraft utilisation data and known or suspected defects after the flight or series of flights, in the aircraft technical log or Journey Log. The current rule, its applicability and any national overlay should be checked for the operation at hand.

The Journey Log is not the PIC's personal logbook. A personal logbook supports the individual's record of experience and flight time. A Journey Log follows the aircraft. The same flight may contribute to both records, but the records have different subjects and should not be treated as interchangeable.

What should a pilot review before flight?

Start with the most recent aircraft record, not just your recollection of the previous flight. The exact pre-flight process depends on the operation and aircraft, but the records review should make the current context findable.

Check, as applicable:

the latest Journey Log entries and whether their sequence makes sense;
any reported malfunction, abnormal indication or damage that has not simply disappeared from view;
any separately controlled deferred item and the conditions or limits attached to it;
the current revision of the aircraft documents needed for the operation; and
whether a follow-up action you or another pilot recorded remains open.

The absence of a warning on one screen is not an airworthiness determination. A Journey Log is one part of the records picture, and maintenance status, required equipment, operational limitations and document validity may be controlled elsewhere. Digital records help only when the owner knows which record is authoritative for each question.

This is particularly important in a mixed paper-and-digital setup. If a report is recorded on paper but flights are logged digitally, the digital context needs to direct the owner or next pilot to the paper record. If the current document revision is kept digitally, the paper folder should not quietly become a competing source of truth.

What should be recorded after flight?

Record facts while they are still fresh and source values are available. A clear entry normally answers four practical questions: which flight, which aircraft, who was PIC and what happened.

Depending on the applicable record system, the entry may include:

flight date and aircraft identifier;
departure and destination aerodromes;
off-block, take-off, landing and on-block times, with a stated time standard;
take-offs and landings;
an aircraft usage or counter value with its unit and source;
nature of flight;
fuel or oil information where the system uses it;
factual incidents, observations or troubles; and
PIC identification or confirmation.

Do not copy this list into a form and assume it is complete for every operation. NCO.GEN.150 and AMC1 NCO.GEN.150 should be distinguished. The rule requires specified aircraft, crew and journey particulars to be retained for each flight or series of flights in a Journey Log or equivalent. The AMC describes particulars that should be included where applicable: nationality and registration, date, crew names and duties, departure and arrival places and times, hours of flight, nature of flight, incidents and observations, and the PIC's signature. The AMC is an acceptable means of compliance; it does not make this article's field list a universal statutory form.

Time labels also matter. Block time is commonly derived from off-block to on-block. Airborne time is derived from take-off to landing. A tachometer or another maintenance-relevant counter is a separate source value. They may all change during one flight, but they do not necessarily measure the same thing or advance at the same rate. Record the label, unit and source instead of silently converting one into another.

For a filled row with concrete times and an explanation of each field, see the aircraft Journey Log entry example.

How should observations be written?

Write what was observed, where in the flight it occurred and whether it changed. Avoid diagnosing a component unless the writer is both competent and acting in the appropriate role.

For example, “Amber charging indication illuminated intermittently for approximately 20 seconds during descent; indication normal after landing” preserves useful facts. “Alternator failed but aircraft serviceable” combines an unverified diagnosis with an unsupported operational conclusion. Under AMC1 ML.A.403, an observed equipment malfunction is treated as a defect even when its cause has not been diagnosed; calling it an observation must not downgrade its significance.

A good observation can include:

the phase of flight or ground context;
the indication, sound, smell, behaviour or visible condition;
whether it was continuous or intermittent;
any immediate action taken by the crew; and
a reference to a separate report when the aircraft's records process uses one.

Recording the report does not decide whether further flight is permitted, and a PIC signature is not a Certificate of Release to Service (CRS). The reporting record, the qualified decision and the evidence of rectification are distinct. The aircraft defects under Part-ML article follows that lifecycle in detail.

How does the record stay useful for the next flight?

A useful record does not depend on the owner remembering every detail from the previous flight. It depends on the entry being complete, available and explicit about open context. If another pilot flies the aircraft, those same qualities create a useful handover without requiring both people to meet beside it.

The continuity loop is:

Step	Record consulted or created	Question it should answer
Review before flight	Latest Journey entries, current aircraft documents and any separately controlled open items	What is the recorded aircraft context now?
Record flight facts	Completed aircraft-centred flight entry	What use took place, when and under whose PIC responsibility?
Report observations	Factual Journey note or linked report	What was noticed, without inventing a diagnosis?
Carry open context forward	Decision record or separately maintained deferred-item record, where applicable	What remains open, on what basis and under which conditions?
Next pilot reviews	The same continuous record set	What must be understood or resolved before the next use?

This is an editorial workflow, not an approved form or a complete compliance checklist. Its value is the closed loop: the owner reviews the current record and contributes the next reliable entry, while an occasional second pilot can follow the same pattern.

Verbal handover and messages can add context, but they should not become the only place where a safety-relevant observation or open action exists. “I will remember it” is equally hard to reconstruct months later. A dated aircraft record with a named coordinator for the next step is much stronger.

What changes when the aircraft is shared?

Shared ownership adds more readers and more opportunities for context to fragment, but it does not change the basic record discipline. Co-owners should agree where the current Journey Log and controlled documents live, how another pilot finds open technical context and who coordinates follow-up. Those administrative arrangements do not make a co-owner, app group owner or group administrator the legal or technical decision-maker for a defect.

For routine flights, each PIC records their own aircraft usage and observations under the applicable process. For ownership, continuing-airworthiness and maintenance decisions, record the person acting in the relevant legal or qualified role rather than treating every co-owner as interchangeable.

What is the Journey Log not?

Several adjacent records are easy to confuse with a Journey Log.

It is not a personal pilot logbook

The Journey Log follows the aircraft. It should not be designed around logging personal experience, ratings or credit. The PIC identity belongs in the aircraft entry because it connects the flight to the responsible person, not because the aircraft record replaces that person's logbook.

It is not automatically a formal Part-M technical log system

M.A.306 describes an aircraft technical log system within a defined Part-M scope. It should not be presented as a universal mandate for every Part-ML aircraft. Terminology and record-system obligations depend on the operation and regulatory context.

It is not a complete maintenance record

A flight entry may identify utilisation and point to an observation, but it does not replace maintenance data, work records, release evidence, status records or the current deferred-maintenance information required in the applicable context. Keep links between those records without collapsing them into one ambiguous note.

It is not a universal counter ledger

Airborne minutes, block minutes, tach readings and other counters can serve different purposes. A Journey Log should preserve the actual source values used by that aircraft's system. It should not invent a universal conversion or imply that one cumulative total governs every maintenance limit.

Are digital, paper and mixed Journey Logs acceptable?

The practical question is less about the medium than about whether the applicable record is complete, legible, controlled and available when needed. A well-run paper log can preserve excellent continuity. A poorly governed digital spreadsheet can create duplicates and silent overwrites. The reverse is equally true.

For each medium, test these controls:

Availability: can the person who needs the record retrieve it at the aircraft or before the operation?
Identity: is it clear who created or confirmed an entry?
Sequence: can users understand the order of flights and later additions?
Correction: does an amendment preserve what changed instead of quietly rewriting history?
Document control: can users identify the current document revision without losing superseded versions?
Backup and recovery: can you restore the record after loss, damage or access failure?

AMC1 NCO.GEN.150 expressly allows the required information to be recorded in a form other than printed paper provided accessibility, usability and reliability can be assured. Those are records controls, not a promise that every implementation or file format is accepted in every context. Check the format, signature and retention requirements that apply to the specific operation.

What operating rhythm works for a pilot-owner?

The strongest process is short enough to repeat after every flight and visible enough to audit periodically.

Before each use

The pilot reviews the latest aircraft entries, open technical context and current required documents. If an item is unclear, the process identifies who must clarify it. Silence or an empty status is not treated as approval.

Immediately after each flight

The PIC records the flight facts, the time standard and source values used, plus any known or suspected defect. The entry is checked for impossible chronology, missing units and ambiguous wording while the source information remains available.

When an observation needs assessment

The report is made visible promptly. The person acting within the applicable authority records the decision and its basis separately. If an item remains unrectified, its current status and conditions remain available to the PIC; it is not hidden inside an old flight row.

On a regular records review

The owner or agreed record coordinator checks for gaps, duplicate sources, unsigned entries, unexplained counter changes and open items with no responsible next step. This is record-quality control, not a substitute for the technical judgement required by the underlying issue.

How does Logga support the current workflow?

Logga's current product includes an aircraft Journey Log with PIC signature and PDF export. It also keeps private aircraft documents as versioned records, so users with the appropriate access can identify a current revision while preserving document history.

That supports the flight-entry and document-control parts of an owner-managed aircraft workflow. The current Journey entry includes a free-text incidents and observations field. A dedicated defect register, assessed-deferral workflow and list, maintenance-closure integration and automated airworthiness decisions are not current Logga capabilities. Where this guide describes those processes, it describes the records discipline an owner needs—not an implemented maintenance module.

One continuous aircraft Journey Log gives a pilot-owner a durable operational memory. Its quality comes from disciplined use: review the current context, record the completed flight, report observations factually, preserve qualified decisions separately and make open context available for the next flight.

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