Logbook

Logbook on Pilot EFB Desk is the same record you keep on the phone, laid out as a table with room to work: a career band across the top, four views, and a spreadsheet mode for corrections that would take an afternoon one entry at a time. The foot of every logbook screen reads "Personal record only." - your own record, not your operator's system and not a legal document.

Find your way around

Click Logbook under Operations in the sidebar (Cmd+3). The shared top bar with its command field runs across this page as on every other desk, and the page's own header row is its actions toolbar: Export (the logbook actions menu - filters, saved filters, every export) and New entry. Under it sits the status rail, one strip read left to right: your picture or initials with your name, base, licence and last flight; the career total as the one large figure beside a twelve-month bar chart and "+HH:MM this month"; PIC, Night and LDG (landings); Recency, a small table with one line per rule (such as T/O · LDG, NIGHT and IFR) giving its segment track, its count against the requirement and its status word, each line opening Currency & Credentials; and the next credential due, or Add credentials if you have none. The rail sizes itself to its content: on a narrower window it first tightens, then splits into two deliberate rows with next due over recency. Then the four views:

The view is in the URL (/logbook?view=currency), so a bookmark reopens the one you want. On the Entries view a Time format toggle at the right of the tab row switches every duration between H:MM and Decimal. The top bar adds one control for this section only: the density button (dense or comfortable rows, for the tables). The Guided tours key there offers the Logbook walk while you are here - about five minutes through the actions, the status rail, the views, the table, the Bulk edit grid, the totals, currency and the map, built for what your logbook holds.

How to log a flight

1. Click New entry in the page header, or press Cmd+N. The New logbook entry desk opens over the table, 1180 px wide: the form on the left, a live rail on the right, each scrolling on its own. (For an empty form instead, open Export and choose New entry (blank form).)
2. Leave the entry type on Flight. With smart defaults on, the date, aircraft type, registration and departure are pre-filled from your recent flying. The summary band under the title reads Block, Air, Night, Type, Reg, Role and Ldg (Session, Type, Role and Appr for a simulator); a figure that cannot be derived yet reads "pending". A numbered 01-06 strip under it jumps to each section of the form.
3. Enter the times in UTC: each clock pair sits on one row - departure clock, the duration on the connector, arrival clock - for off-blocks and on-blocks, and wheels-off and wheels-on if you record air time. Block and air time are worked out as you type. A time that cannot be right is named at the clock it belongs to - a take-off outside the block, a landing after on-blocks, a zero-length block - and Save waits until it is fixed.
4. Count the take-offs, landings and approaches, with day and night separate, then add night, IFR, cross-country and instrument time, your role and who you flew with. Every one of those times has to fit inside the block (the session for a simulator), and a time that cannot be read is named rather than saved as zero. Each approach can carry its location and runway, and remarks take up to 2000 characters with a counter. A flown sector with block time and no landing gets a caution - fine for a positioning or diverted leg - that never stops the save.
5. Read the rail as you go: the entry at a glance (block, air, taxi out and in, slip against the schedule, night, landings), the OUT / OFF / ON / IN leg timeline, a pre-save checklist that confirms what is already right and lists what still needs you, and your recent legs on the same tail. The footer sums it up in one line - the block, air, night and landings, or "No block yet · N checks to clear".
6. Click Save entry, or press Cmd+Enter from anywhere in the form (Esc cancels; the rail shows the chords). The desk closes and the table refreshes in place.

How to find, sort and filter entries

1. On the Entries view, type in the search field - it reaches aircraft, ICAO codes, crew names and remarks.
2. Click a quick-filter chip: All flights, This month, Night, Cross-country or Sim. Each carries its count, and the chip rides the URL (/logbook?chip=night), so a shared link opens the same cut.
3. For anything finer, click Filters (date range on one From / To row, aircraft type, airport, role, entry type, route pair or flight folder). A live filter reads as a clause of the status line under the table - "filtered by MD-82" with Clear filters beside it - and the funnel chip lights with the count. Save a filter you reuse from Export > Save current filter; it appears under Smart groups above the table.
4. Click a column header to sort the whole logbook by it, and Clear in the status line to restore month order. Date and Route read left-aligned as the identity columns; every time and count column is centred, and a long remark shows as a Notes chip whose full text is in the entry detail.
5. Click Refresh to re-read the logbook from the local database. The button holds a spinner for a beat and the status line then reads "Refreshed HH:MMZ" for the rest of the session.

The table shows only columns that have data by default; the status line under it says so - "8 empty columns hidden · Show all 25 columns" - and flips to Hide empty columns once every column is shown. Fifty rows fill a page; Prev and Next page through the rest, and the page, sort and columns all sit in the URL beside the chip.

How to open, edit and delete an entry

1. Click a row. The entry opens in a modal over the table: the flight as a boarding-pass style hero, the route flown as a chart (aerodromes drawn as ring-and-runway symbols, the codes placed clear of the track), then every field the entry carries - Recorded time, conditions, crew, remarks and photos. A photo kept in this browser carries an Open · Save pair: Open shows it in a new tab, Save downloads it.
2. Click Edit in the modal footer. The same desk as New entry opens in place, with the entry loaded. Make the change and click Save changes; the confirmation reads "Entry updated" and carries Undo.
3. To go further back, scroll the detail to Version history, after the custom fields: each earlier version with its date and time, Edited or Restored, the fields that changed, and Restore behind a confirm. Ten rows show first, then Show all N versions. History stays in this browser and does not sync; it keeps the newest 50 versions of an entry (a signed entry keeps its whole trail), and a locked entry refuses a restore until you unlock it.
4. Log again starts a new entry pre-filled from this one. Open flight jumps to the linked flight folder when there is one.
5. Delete asks you to confirm, then a toast offers Undo for five seconds.

A signed entry shows a Locked badge and the footer button reads Unlock & edit: you are asked to unlock it before the form opens. The Signature card in the detail carries Sign & lock on an unsigned entry, and Re-sign & lock or Remove signature once it has been unlocked to edit. Under it, Instructor signature requests drafts a request to an instructor; remote signing is not switched on yet, so a request stays in this browser as a draft and nothing is sent. Every row also has Edit, Log again and Delete on hover. The open entry is in the URL too (?entry=), so a refresh or a shared link reopens it; a deep link to /logbook/view/<id> shows the same record as a page, and /logbook/<id> opens the editor directly.

How to edit many entries at once

Bulk edit is a Desk-only surface. It turns the Entries table into a spreadsheet grid and previews every change before it is written.

1. On the Entries view, click Bulk edit. The heading changes to Edit mode, with Shortcuts, Find duplicates, Columns, Add row and Done on the right. Any filter or chip you had set stays in force, so the grid holds only the rows you were looking at.
2. Tick the rows you want to change with the checkbox rail, or the header checkbox to select every filtered row. The bar reads how many are selected.
3. Choose an operation from the bar:
   • Set field - pick a field, pick or type the value, choose Selected rows or Whole filtered column, then Preview change.
   • Find & replace - find text across all text fields or one of them, with Match case and Whole field options, then Preview replace.
   • Duplicate copies the ticked rows; Delete marks them for deletion; Clear empties the selection.
   • Fill down: focus a cell and press Cmd+D to copy its value down the ticked rows.
   • Paste: copy a block from a spreadsheet and press Cmd+V at the focused cell (or the first ticked row); columns map left to right from that cell.
4. Read the preview. It lists each row with the before and after values and flags any change that feeds currency or totals. Click Apply (or Delete / Duplicate) to commit, or Cancel.
5. Click Done to leave edit mode.

Every batch is written as one transaction, so it lands whole or not at all. Cmd+Z undoes the last batch, and the Undo button in the edit-mode bar names what it would reverse. Leaving with an open cell, a staged preview or a write in flight asks first - in the app, and on the browser's own Back button or a trackpad swipe ("Discard the cell you are editing?"); Stay keeps the grid exactly as it was. Locked rows are greyed with a padlock, read-only in the grid and skipped by every bulk operation; a pasted line that lands on one is reported as skipped rather than shifting the rest down.

How to read your totals and career charts

1. Open Totals & Career. The lead panel gives total time, PIC, SIC, day, night and instrument for the window you pick, and tiles appear only for what you have logged - cross-country, approaches, multi-engine, turbine, simulator and more.
2. Scroll for Time by aircraft type, Hours by month, Milestones and the Carry-forward panel for hours from before Pilot EFB. Milestones is your career ladder for total time and PIC time: the current figure and the hours to the next rung, every rung as a chip (passed, next or ahead) and "N of M rungs passed". Simulator hours do not count toward a rung.
3. Under Analytics & career, click Insights dashboard. The Insights page opens with a Period switch (All time, Last 12 months or the current year), the Goals card, a stat strip, and the charts: cumulative hours, yearly and monthly totals, hours by role, fleet mix, conditions, approaches by type, records and career pace.
4. Click + Add goal on the Goals card, set an hours target, and the card tracks your pace toward it.
5. Print report opens the browser's print dialog with the analytics report laid out; choose Save as PDF there to keep it. Career view, back on Totals & Career, is the same record condensed into stat tiles and milestones, with a Qualification pathways card: each pathway quotes its regulation and shows which of your flights count toward its experience rules, and never says you are eligible.

How to check your recency

The currency view is a two-column desk: the posture, the lapse strip and the rule cards on the left, a working rail on the right (it stacks below 1180 px).

1. Open Currency & Credentials. The hero is a segmented ring - one arc each for current, expiring and lapsed rules - beside the headline with its count chips, one sentence on your posture, jump chips to the rules needing attention and a 2x2 instrument cluster. When no rule can be counted yet, an Unlock tracking panel stands in its place: the engine's reason, your raw 90-day counts and the aircraft types you flew against your saved profiles, with a door to the aircraft registry. If every type you flew already has a classified profile but the entries still carry no category or class, it says so and offers Apply profiles to past entries, which asks before it updates each profile's entries.
2. Read the Next 12 months strip: rules and documents on one track, a bar where a rule lapses, a diamond where a licence or check expires, red for what has already lapsed, every marker a button.
3. Read the rule cards, worst first. Each carries a window bar with a tick per contributing entry (the heaviest tick is the one whose drop-out lapses you, the shaded band what has already dropped out), the tally against the requirement and a fix line in words. A rule that needs attention offers Log a flight (Log approaches for the instrument rule); the other button opens the rule - Show the N entries when entries count toward it, Open rule when none do, Edit rule on one of your own. A line under the cards names the rule set in force.
4. Use the rail. The Recency horizon projects your recency "if nothing more is flown": drag the handle to any day in the next 12 months, or use Today, +1 mo, +3 mo, +6 mo and +12 mo, and read the Current, Expiring and Lapsed counts for that day, the lapse chips for the whole year and one sentence on what changes by then - a read-only projection from your logbook. The track uses the same bar, diamond and red marks as the strip. Qualifying activity lists the entries that count and opens them; What this can't see names the gaps the engine cannot fill and opens the rule.
5. Further down the rail, Credentials & reminders lists your ratings, checks, medical and documents with their expiry status. Add credential and Manage credentials go to Settings > Credentials, where each credential is dated. Logbook health at the foot is the door to the health console below.

The built-in rules follow the FTL regime you set for Duty. Under FAA they are 14 CFR 61.57: take-offs and landings over 90 days, night full-stop landings over 90 days, and instrument approaches over 6 calendar months - once instrument currency has been unmet for more than six calendar months, the rule says an instrument proficiency check is required, and an IPC credential (or an entry signed with the IPC endorsement) counts for it. The two landing rules count only landings you made as sole manipulator of the controls, so an entry recorded as pilot monitoring earns nothing; an entry with no pilot-flying record still counts, and the rule says how many there are. Under EASA they are FCL.060(b): three take-offs, approaches and landings as pilot flying in 90 days on the type or class, and one night take-off and landing as pilot flying, which a valid instrument rating makes not applicable - that card then reads Does not apply; FFS time counts for both. The desk applies the EU wording, and the card notes that the UK-retained text does not say "pilot flying". Your own rules survive a switch. To add one, click Add rule (on the standalone /logbook/currency page it sits in the header beside Log a flight) and give it a Display name, a type, an optional aircraft type, the Required landings or approaches, and the Rolling window (days).

How to run the logbook health check

1. On Currency & Credentials, click the Logbook health door in the rail. Its caption tells you how many advisory findings are waiting, or invites you to scan for gaps, overlaps and continuity breaks.
2. Read the Record health hero: a ring showing the share of scanned entries with no contradiction or review item, a Clean scan or Worst: chip, the scan time, and a count per severity.
3. Use the Triage rail to narrow the ledger: All findings, one severity, one family of check, Possible duplicates, or Reviewed.
4. Work the Findings ledger, grouped By issue or By entry. Each row explains the finding and names the entry; Open shows it read-only, Fix opens the editor on the exact field, and Reviewed acknowledges a finding you have judged fine. The ledger pages in batches; click Show more for the rest.

The console says what it is on the hero: "Advisory only. These are record-quality checks on your own logbook - internal contradictions and likely gaps - never a currency or legality determination, and a clean scan cannot confirm the record is complete."

A few rules keep the findings honest:

• An accidental double entry is reported once, under Possible duplicates - not again as an overlap or a break in your route.
• An overlap names the other entry it runs into, by route and out time, so you know which row to open. Overlaps are read on block time.
• A glider, balloon or airship logged from launch to rest is not flagged for carrying take-off and landing times.
• A long stretch with no flights (90 days or more) stays in the ledger as an incomplete-record note, but it no longer counts toward the Overview's logbook-health nudge or the iPhone's Home nudge and Currency badge.

How to export your logbook

The export path on Desk is CSV, delivered as a browser download.

1. Click Export in the page header and choose Export CSV. Pick the scope (all entries or the filtered set) and the dialect - Pilot EFB, ForeFlight, LogTen Pro or mccPILOTLOG - and the file downloads. Export logbook (CSV) under Settings > Export does the same for the whole logbook, as UTF-8 with BOM.
2. For a formatted logbook, choose Export PDF from the same menu and pick the layout - EASA, FAA, professional or US professional. On the desk this opens the browser's print dialog with the logbook laid out as one book: a cover with a contents list, the ruled ledger filling each sheet, the tail sections (device lessons, instrument evidence, signatures), and a running head on every sheet with "Page n of N" over the whole document. Choose Save as PDF there; the dialog is already seeded with the file name. Because a browser cannot tell the app whether you saved or cancelled, the app only ever reports that the dialog opened. Experience report and 8710 summary sit in the same menu, each laid out sheet by sheet with its own running head and page numbers; Share summary is plain text for job applications, with your name left out by default.
3. For an application or a renewal, choose Report profiles: pick Airline application, Insurance renewal or Authority recency on the left and read the evidence check on the right, which names the entries missing a field the report needs. While gaps remain the button reads Render anyway, and the PDF then carries an evidence-gaps appendix.

Every export follows one naming rule - pilot-efb-<document>[-<layout>][-<scope>]-<date>-<HHMMSS>Z.<ext>, for example pilot-efb-logbook-easa-last-30-days-2026-09-18-095828Z.pdf or pilot-efb-logbook-csv-2026-09-18-101204Z.csv - so the layout and scope are in the name and a later save never replaces an earlier one in your Downloads folder.

How to bring entries in

The Export menu's Bring records in section has both routes - Import existing logbook, and Review flights from duties with the number of imported roster sectors waiting.

• CSV import. Open Settings > Logbook settings and under Data click Import CSV. Click Pick CSV file (or drop the file on the window; files up to 10 MB), map the columns the wizard could not match, review the Preview & review step - duplicates already in your logbook and duplicates within the file are marked - then import. If the file records no role for some rows, Role not recorded asks you to pick one, and the import button reads "Choose a role to import" until you do or untick those rows. Nothing is written until you confirm, and a failed import writes nothing. Each import leaves a receipt under Import receipts on the same page: what it wrote, and how its totals reconcile with the file's own columns.
• Build from duties. On the same page, click Build from duties. Draft entries are built from the duties you keep in Duty & FTL: block times come from the schedule, positioning sectors and flights already in your logbook are skipped, and you review the drafts before anything is added. The preview names the role every draft will carry - your logbook default - and pilot flying, landings and approaches are never filled from a roster. Confirm the actual times and add the aircraft afterwards.

On iPhone and iPad

The phone keeps the same record and the same rules, without the desk surfaces: there is no bulk-edit grid, no Insights desk and no health console layout, and the free tier caps logging at 300 logged hours. Recently deleted - the 30-day recovery list for deleted entries - sits on the phone's logbook menu; the desk's menu has no such row, so use the five-second Undo after a delete, or press Cmd+K and type "deleted entries" to open the same page. Logbook on iPhone covers all of it.

Troubleshooting

The table shows fewer columns than I expected. Empty columns are hidden by default; the status line under the table says how many. Click Show all 25 columns there.

A chip or sort I set is gone after sharing the link. The chip, page, sort and columns ride the URL only while they are set; the link you copied may have been taken before you set them. Set them again and copy the address bar.

Bulk edit skipped some rows. They are locked. Open the entry, remove or pause its signature, and it becomes editable again.

A rule shows lapsed but I flew recently. Check the entries carry the evidence the rule needs: pilot flying (not pilot monitoring) set on the entry for the landing rules, night full-stop landings for the FAA night rule, approaches for the instrument rule. Carry-forward totals never count toward currency.

The PDF export reported only that the dialog opened. That is all the browser can tell the app. If you cancelled the dialog, nothing was saved; run Export PDF again and choose Save as PDF.

Where next

• Duty & FTL - the duties that Build from duties turns into draft entries.
• Keyboard and command deck - Cmd+N, Cmd+3 and the grid keys alongside every other shortcut.
• Settings and sync - Auto-sync, credentials, and the export and import pages.
• Logbook on iPhone - the same record on the phone.