Skip to main content
By the end of this guide, you will have reviewed flight logbook entries, filtered by aircraft or date range, added new entries, and exported records for regulatory compliance.
The Operations module must be enabled for your workspace. You also need the appropriate operations permissions. Contact your workspace administrator if you cannot access these features.
You need the crew_personal.read permission. To add or edit entries you also need crew_personal.update.

Prerequisites

  • Your workspace must have the Operations module enabled.
  • At least one crew logbook entry must exist. Entries are created manually from the Logbook page or automatically when trips are completed.
Open the Operations sidebar and click Logbooks under the Crew group. The page loads with the breadcrumb path Ops > Logbooks. You can also reach an individual crew member’s logbook entries from the Logbook tab on the crew detail page.

Summary stat cards

Four stat cards appear above the table and update in real time as you apply filters:
CardWhat it shows
Total Flight HoursSum of all Total time entries matching the current filter.
PICAccumulated Pilot in Command hours for filtered entries.
NightTotal night flight hours for filtered entries.
Cross-CountryTotal cross-country time for filtered entries.
All values are displayed to one decimal place in hours.

Filter toolbar

The toolbar above the table provides four controls:
  • Search — Free-text search against route (origin/destination) and tail number. Clears to page one automatically.
  • From / To — Date range pickers. Enter both dates to narrow results to a specific period (useful for recency checks or certificate renewal reviews).
  • Aircraft — Dropdown populated from your workspace fleet. Defaults to All Aircraft. Select a tail number and model to show only entries for that aircraft.
Filters are cumulative — you can combine date range and aircraft selection at the same time. The table, running totals footer, and stat cards all reflect the filtered result set.

Table columns

The logbook table is sortable by clicking any column header:
ColumnDescription
DateFlight date, displayed as Mon DD, YY. Sorted descending by default.
RouteOrigin and destination in ICAO format separated by an arrow (e.g., KTEB → KPBI).
AircraftTail number in bold with aircraft model as a caption beneath.
TotalTotal flight time for the entry in hours (one decimal).
PICPilot in Command time in hours. Displays a dash if zero.
SICSecond in Command time in hours. Displays a dash if zero.
NightNight flight time in hours. Displays a dash if zero.
XCCross-country time in hours. Displays a dash if zero.
InstrumentActual instrument time in hours. Displays a dash if zero.
LandingsDay and night landing counts formatted as D:n / N:n.
RemarksFree-text notes field, truncated to 200 characters in the table view.
Click any column header to sort ascending; click again to sort descending. When at least one entry is visible, a Totals row appears at the bottom of the table body. It sums every numeric column across the entire filtered result set — not just the current page. This means you can set a date range, select an aircraft, and immediately read the accumulated hours for that subset without exporting. The landings cell in the totals row shows combined day and night counts formatted as D:n / N:n.
To check a pilot’s recency for a specific aircraft, set the From date to 90 days ago, select the tail number in the Aircraft filter, and read the Night and Instrument totals directly from the footer row.

Add a logbook entry

1
Step 1: Open the New Entry form
2
Click New Entry in the page header.
3
Step 2: Fill in required fields
4
FieldRequiredDescriptionCrew MemberYesSelect the pilot or crew member from the dropdown.DateYesFlight date.OriginYesDeparture airport ICAO code.DestinationYesArrival airport ICAO code.Flight TimeYesTotal flight time in decimal hours. Must be greater than zero.
5
Step 3: Fill in time categories
6
Enter decimal hours for each applicable category:
7
FieldDescriptionPIC TimeTime as Pilot in Command.SIC TimeTime as Second in Command.Night TimeTime flown during night conditions.Instrument TimeActual instrument meteorological conditions.Cross-Country TimeFlights meeting 14 CFR 61.1(b)(3) cross-country criteria.Dual TimeTime received under the supervision of an instructor.
8
Step 4: Add landing counts and remarks
9
Enter day and night landing counts. Add any free-text remarks in the Notes field (approach types, weather encountered, training events).
10
Step 5: Save the entry
11
Click Save. The entry appears in the table immediately and all totals update.

Edit an entry

To correct an existing logbook entry, click the row to open the edit form. All fields are editable. Click Save when finished.
Logbook edits are recorded in the workspace audit log with the user who made the change and the timestamp. Corrections to regulatory records should include a note explaining the reason for the change in the Remarks field.

Export records

Click Export in the table toolbar to download the current filtered result set. The export honors all active filters — if you have a date range and aircraft selected, only those rows are included.

CSV export

FormatUse case
CSVImport into third-party logbook software or spreadsheet analysis.
The CSV file is named logbook-YYYY-MM-DD.csv using today’s date. Headers match the table column names (Date, Route, Aircraft, Total, PIC, SIC, Night, XC, Instrument, Day Ldg, Night Ldg, Remarks).

PDF logbook export

Click Export PDF (or select PDF Logbook from the Export dropdown) to generate a formatted PDF logbook for the selected crew member and date range. Two formats are available:
FormatDescriptionUse case
CondensedOne row per flight. Mirrors the ForeFlight condensed logbook report format. Includes running totals at the bottom.Quick review, regulatory checkrides, sharing with check airmen.
CompleteFull per-flight detail with remarks. Mirrors the ForeFlight complete logbook report format.Comprehensive audit trail, legal records, FAA certificate applications.
The PDF is generated from your workspace’s logbook data and includes the crew member’s name, date range, all applicable time categories, and cumulative totals.
PDF logbook exports reference 14 CFR 61.51 as the basis for the record format. The export is a useful supplement to a pilot’s personal logbook but does not replace it — pilots remain responsible for maintaining personal records under 14 CFR 61.51.

FAA experience report export

Click Experience Report (or select FAA Experience Report from the Export dropdown) to generate a PDF that maps logbook entries to FAA certificate aeronautical experience requirements. Three report types are available:
ReportRegulatory basis
Private Pilot ASEL14 CFR 61.109(a)
Commercial Pilot ASEL14 CFR 61.129(a)
Instrument Rating — Airplane14 CFR 61.65(d)
Each report shows the minimum required hours in each category alongside the pilot’s logged hours, so deficiencies are immediately visible. Useful for student pilots tracking progress toward checkrides and for CFIs reviewing training records.

Upload flight logs

Click Upload Flight Logs in the page header to navigate to the SmartScore upload page, where you can bulk-import FOQA data and flight records from avionics exports.

Offline behavior

If the app cannot reach the server, a yellow banner reads You are viewing cached data. The table and totals reflect the last loaded data. Refresh the page when connectivity is restored to see current records.
PlaneConnection records flight time against crew profiles, but the system does not replace a pilot’s personal logbook required under 14 CFR 61.51. Pilots should reconcile workspace records with their personal logbooks regularly.

Manage Crew

Add crew members and manage certifications before logbook entries are created.

Crew Roles

How currency calculations use logbook data for scheduling validation.

Create a Trip

Trip completion automatically generates logbook entries for assigned crew.

Reports: Crew

Crew scheduling, duty time, and flight time summary reports.
Last modified on April 11, 2026