pilot.report
Add

Digital Pilot Logbook: Verified Flight Hours, Sealed Entries and Per-Aircraft History

A digital pilot logbook should be more than a spreadsheet, and the Logbook section (/logbook) makes it evidence: every flight, ferry and maintenance event recorded against a specific aircraft, then sealed with a cryptographic fingerprint so verified flight hours can be trusted, not just claimed.

Open your logbook
Logbook — entries

Interactive preview — every element opens the live section.

Contents

One journal across every aircraft you fly

The Logbook is a single journal that spans all of your aircraft rather than a separate book per tail. Open /logbook and you see one chronological stream of entries — flights, ferries, repositioning legs and maintenance events — with the aircraft tail shown on each row and a filter to narrow the view to a single type or a single aircraft. There is no double-entry: an entry lives against its aircraft and simultaneously appears in your unified logbook.

Each entry carries the fields that matter for that kind. Flights and ferries record departure and arrival airports (ICAO and city), air time in H:MM, distance, the pilot in command and, where relevant, total time on the airframe. Maintenance entries instead capture the work performed, the station and the mechanic who signed it off. The result is a record that reads naturally whether you are reviewing your own hours or an aircraft's service history.

  • Five entry kinds: flight, ferry, repositioning, maintenance and article
  • Flights capture from/to airports, air time (H:MM), distance and pilot in command
  • Maintenance captures work performed, station and the signing mechanic
  • Total time on the airframe (TT) can be recorded to anchor an aircraft's running hours
  • Every entry is tied to a specific aircraft and to you as its owner
ExampleAn owner-pilot logs a Sunday flight EGTF → EGKA at 0:45, a ferry leg the next week, and an oil-and-filter change signed off by an EASA Part-66 mechanic — all three sit in the same journal, each tagged to the aircraft's tail.

Sealing entries: tamper-evident, immutable flight records

New entries start as drafts you can edit freely. When a record is final, you seal it. Sealing computes a SHA-256 fingerprint over the entry's canonical content — date, kind, air time, route, pilot, maintenance details and the linked aircraft — and stores that hash together with the seal timestamp. From that moment the entry is immutable: it cannot be edited, and any later change would produce a different fingerprint, so tampering is detectable.

This is what turns a logbook from a private notebook into verifiable evidence. A sealed entry is deliberately locked rather than blocked from correction: if you genuinely need to fix a sealed record, the workflow is to create a new version instead of quietly rewriting history. Drafts and sealed entries are counted separately so you always know how much of your journal is finalised.

  • Draft entries are fully editable; sealed entries are locked
  • Sealing stores a SHA-256 content fingerprint plus a seal timestamp
  • Any change to a sealed entry would alter its hash — tampering is evident
  • Corrections are made by creating a new version, never by silent edits
  • The stats panel shows how many entries are sealed versus still draft
ExampleAfter a flight is logged and reviewed, the pilot taps Seal, confirms the one-way warning, and the row switches to a green 'sealed' badge — its hours are now locked and countable as verified.

Verified flight hours you did not type yourself

The strongest hours in a logbook are the ones you did not enter by hand. When you rent an aircraft through the platform's rental flow, returning the aircraft closes the deal and automatically writes a flight entry into the logbook — dated, with air time derived from the Hobbs-out to Hobbs-in difference, and with you tagged as pilot in command. That entry is sealed on creation, so the renter walks away with confirmed hours the moment the owner accepts the aircraft back.

Because the pilot in command can be tagged to a real profile on the platform, a sealed flight created this way links your hours to your public identity rather than a free-text name. These are the hours that carry weight: recorded by a second party, backed by Hobbs readings and sealed automatically, they are far harder to inflate than a number written into a paper book.

  • Completing a rental auto-creates a flight entry in the logbook
  • Air time is computed from Hobbs-out to Hobbs-in, not typed in
  • The renter is tagged as pilot in command and gains confirmed hours
  • The auto-created entry is sealed immediately, making it tamper-evident
  • Pilot-in-command tagging links hours to a real platform profile
ExampleA renter flies 1.6 Hobbs hours; on return the owner records Hobbs-in, and a sealed 1:36 flight entry appears in the renter's logbook automatically — verified hours with no self-reporting.

Pilot in command: free text or tagged to a real profile

Every flight or ferry can name a pilot in command. You can type a name as free text, or tag a pilot who already has a profile on the platform. When a valid handle is provided, the entry is linked to that pilot's profile and their display name is denormalised onto the row, so the logbook shows a clickable link to /u/username instead of an unverifiable string.

This matters for shared aircraft and instruction. An owner logging a flight flown by someone else can credit the actual pilot, and that pilot's confirmed hours accrue against a real identity. Tagging is optional and reversible on drafts — clear the field and the entry falls back to plain text — but once an entry is sealed, the pilot attribution is locked in with the rest of the record.

  • Name a pilot in command as free text, or tag an on-platform profile
  • A tagged pilot links the entry to their public profile at /u/username
  • Useful for shared aircraft, club fleets and instruction
  • Tagging is editable on drafts and locked once the entry is sealed
ExampleAn owner logs a training flight and tags the instructor's handle; the entry links straight to the instructor's profile, and after sealing that attribution is permanent.

Live statistics and flight recency

The Logbook does the arithmetic for you. A stats panel at the top rolls up total flight hours, the number of flights, hours flown in the last 90 days, how many aircraft appear in your journal, and the split between sealed and draft entries. Hours are summed from the H:MM air time on flight and ferry entries, so the totals reflect what you actually recorded, not a running figure you have to maintain.

The last-90-days figure is the seed of flight recency. Because it is computed only from your logbook — and, for verification, from sealed entries — it feeds directly into the Currency section, where it becomes recent-experience tracking alongside licence and medical expiry. In other words, keeping the logbook current is what keeps your readiness dashboard honest.

  • Totals: flight hours, number of flights, aircraft count, sealed vs draft
  • Hours summed from H:MM air time on flight and ferry entries
  • A 90-day hours figure captures recent flight experience
  • Entries are broken down by kind (flight, service, ferry, position, article)
  • Recency from sealed entries feeds the Currency readiness tracker
ExampleA pilot's panel reads 214:20 total, 96 flights across 3 aircraft, 8:10 in the last 90 days and 78 sealed of 91 entries — a five-second read of both experience and recency.

How it works

  1. Add an aircraft to your garage, then open /logbook and tap New entry.
  2. Choose the kind — flight, ferry, repositioning or maintenance — and fill the relevant fields.
  3. For flights, record from/to airports, air time in H:MM and the pilot in command (typed or tagged).
  4. Save as a draft; edit it freely until the record is final.
  5. Seal the entry to lock it — a SHA-256 fingerprint and timestamp make it tamper-evident.
  6. Rental flights are logged and sealed automatically on return, adding verified hours with no manual entry.
  7. Watch the stats panel for total hours, recency and your sealed-versus-draft count.

FAQ

How are flight hours in the logbook verified?

Hours become verifiable when an entry is sealed: sealing stores a SHA-256 fingerprint of the entry's content, so any later change would alter the hash and be detectable. The strongest hours come from completed rentals, which auto-create a sealed flight entry with air time computed from Hobbs readings rather than typed in by hand.

Can I edit or delete a sealed logbook entry?

No. Once sealed, an entry is immutable — this is what makes the record tamper-evident and trustworthy. If a sealed entry genuinely needs correcting, the workflow is to create a new version rather than silently rewrite history. Drafts, by contrast, stay fully editable until you choose to seal them.

Is the logbook per aircraft or one book for all my flying?

Both. Each entry is tied to a specific aircraft and contributes to that aircraft's history, but /logbook shows a single unified journal across every aircraft you own, with a filter to narrow by aircraft or by entry kind. There is no double-entry — an entry appears in both views at once.

How does the logbook connect to my currency and readiness?

Flight hours logged in the last 90 days are computed straight from your logbook, and recency for the Currency tracker is drawn from sealed entries. Keeping the logbook current therefore keeps your readiness dashboard accurate, showing recent experience next to your licence, medical and rating expiry.

Start a logbook nobody can dispute

Sealed, tamper-evident entries — hours that survive any audit or pre-buy.

Open logbook Free for pilots and owners · 35 languages