FAA PROFESSIONAL PILOT LOGBOOK

Boeing 737-800 · FAA Professional Pilot Logbook V2.1.1 · Clean Start · Stable Calculation & Persistent Storage · UTC

Logbook overview · Dates UTC / Flight-time totals UTC

Imported role rule: SIC through 15 Feb 2026; PIC from 19 Feb 2026. Total time is entered as day + night duration. Actual instrument is treated as a subset, not added again.
0Flight entries
00:00Total logged flight time (UTC)
00:00PIC time (UTC)
00:00SIC time (UTC)

Import flight records · TXT / PDF / Excel / CSV

Choose a text file, searchable PDF, Excel workbook (.xlsx/.xls), or CSV. The app reads common flight-log column headings, previews the rows, then adds them to this browser's logbook. Existing entries are kept; exact duplicates are skipped.

No file selected.
Role assignment follows your standing instruction: entries dated through 15 Feb 2026 are assigned 100% SIC; entries dated from 19 Feb 2026 onward are assigned 100% PIC. Dates and durations are treated as UTC. Scanned/image-only PDFs need OCR first; this importer reads selectable PDF text.

New flight / lesson entry

Enter duration totals in UTC HH:MM. The calendar date is the UTC date written in the source logbook. If a flight crosses UTC midnight, preserve the UTC date rollover. Block off/on and duty timestamps are labeled by their own timezone fields. FAA loggable categories must reflect the capacity and conditions actually met under 14 CFR §61.51. Airline block time and duty time are kept separate from FAA flight time.

1 · General FAA logbook entry — §61.51(b)(1)

2 · Type of pilot experience / training — §61.51(b)(2)

3 · Conditions of flight — §61.51(b)(3)

4 · Takeoffs & landings / recent experience

5 · Airline operational record (additional, not a substitute for FAA fields)

Images are resized before local browser storage. Keep original photos separately as source evidence.

Regulatory notes

Date convention: logbook dates are UTC dates, not local dates. When a flight crosses UTC midnight, record the UTC date rollover (for example, 07/08 means UTC date 7 to UTC date 8). All flight-time durations and cumulative hour categories are also UTC. Photo attachments are stored with each entry in browser storage (subject to browser storage limits). This application is structured around 14 CFR §61.51. Required general fields include date, total flight/lesson time, departure and arrival locations, aircraft/device type and identification, and safety-pilot name when required. It separates pilot-experience categories and flight conditions. Additional fields support airline records and currency tracking. Logging eligibility depends on the applicable FAA rule and the facts of each operation; this software does not decide legal eligibility.

Source-page monthly totals transcribed separately: January 2026 handwritten total = 50:21; February 2026 handwritten total = 25:34. All 18 source flight-time totals are entered and assigned by the pilot's date-based role instruction: SIC through 15 February 2026, PIC from 19 February 2026. This is a private recordkeeping tool, not an FAA-issued or FAA-approved electronic logbook. Retain original supporting records and verify entries before relying on them for certificate, rating, or recency requirements.