Electronic Pilot Logbook
Paste or open your logbook as a table, check every row, compare the totals with the old logbook, then download a clean CSV or add the rows to the web logbook.
Free · runs in your browser · nothing is uploaded
An electronic pilot logbook starts with moving the records you already have into it, and this page does that step: it takes a logbook you keep as a table and checks it before anything is saved. Paste the table or open a CSV file. The tool matches each column to a logbook field, reads every row, and lists each row it cannot read with its row number and the reason. You can then compare the column totals from the old logbook with what the rows add up to.
The result is a clean Winghours CSV, or the readable rows added to the web logbook on the home page, which uses the same browser storage. Nothing is uploaded.
How to bring your logbook in
- Paste a table or open a CSV file. The first row must hold the column names.
- Check the column list (step 2 on the page). Any column marked Check this guess should be confirmed or changed there.
- Read the preview. It counts rows, readable rows, rows with errors and possible duplicates.
- Type the column totals printed in the old logbook. The tool shows what the imported rows add up to and the difference for each column.
- Choose Download clean CSV to get a clean Winghours CSV.
- Or choose Add entries to my logbook to add the readable rows in this browser. Possible duplicates are skipped while the Skip the rows that look like duplicates checkbox is ticked.
If a column was not matched, pick its field from the Winghours field list in step 2 before you read the preview; the list holds every column the logbook stores. Columns you leave on Ignore this column are not imported.
The clean CSV has a header row and writes every time as h:mm. Keep your original file as the record. For a paper logbook, type the rows into a spreadsheet first, then save it as CSV. Compare the totals row against your old logbook before you rely on the import.
How are my columns matched?
The tool compares each header by its letters and digits only, ignoring case, so Date and Flight Date both match the date field. A field uses the first matching column only, and unknown columns are ignored.
“Landings” is read as day landings, and “IFR” and “Instrument” are read as actual instrument. Because these headers mean different things in different logbooks, they are marked Check this guess. Confirm the choice in the column list or change it.
Which duration formats are read?
The tool reads 1:30, 01:30 and 1:30:00, hour words such as 1h30 and 1h 30m, decimal hours such as 1.5 or 1,5, and minute counts such as 90m. The same time written as 1:30, 1h30, 1.5 or 90m is read as 1:30 in every case. Blank counts as 0.
Decimal hours are rounded to the nearest minute, so 0.33 h becomes 0:20. A plain number such as 90 is read as hours by default, so it is an error for being over 24 hours, unless a switch reads it as minutes. Negative time and text such as 1:75 are errors.
How are day-month and month-day dates decided?
For numeric dates like 03/04/2026 the tool looks at the whole column. If any date has a first number above 12, such as 15/04/2026, every date is read day first. If any has a second number above 12, such as 04/25/2026, every date is read month first.
When every date has both numbers 12 or below, both orders are valid, so those rows are errors until you pick day first or month first with the switch. The tool shows both readings of the first such date: 03/04/2026 is 2026-04-03 day first, or 2026-03-04 month first. Impossible dates such as 31/04/2026 are errors.
How does the totals check work?
Type the column totals from the old logbook. The tool shows what the imported rows add up to and the difference for each column. Only rows without errors are counted, so a skipped row appears as a difference.
The made-up example has four rows: 1.5, 1:15, 1h30 and 45m, where the last row is on the impossible date 31/04/2026. Three rows are readable, and the error reads “Row 5, Date: This is not a valid date” (row 1 is the header line, so the fourth flight is row 5). The imported total is 4:15, which is 255 minutes. If the old logbook says 5:00, the difference is -0:45, the same 45 minutes as the skipped row.
What is not supported or not verified?
The tool reads CSV, TSV and pasted tables only. Excel date serial numbers, PDF files and photos of paper pages are not read. It was not tested against any named logbook product’s exports, so no export is promised to map cleanly.
The tool is not certified by any authority. Whether an authority or employer accepts a converted logbook is their decision. 14 CFR 61.51(a) requires experience to be recorded “in a manner acceptable to the Administrator” and does not mention electronic logbooks. Keep the original paper or file.
Sources
14 CFR 61.51(a), eCFR, text as of 2026-10-20 (read 2026-10-25). Parsing rules are the tool’s own and are covered by its test suite.
Questions from readers
What is the best way to digitize a pilot logbook?
Copy each flight from the original into a table, one row per flight, with the column names in the first row. Bring that table here to read every row and check the totals, then download a clean CSV or add the readable rows to the web logbook.
Is there a digital logbook for pilots I can start with today?
The web logbook on the home page can be used at the moment without an account, and the readable rows from this tool can be added to it.
Do airlines accept digital logbooks?
This tool cannot say. An airline, employer or authority decides whether an electronic or converted logbook is accepted, and 14 CFR 61.51(a) does not mention electronic logbooks. Keep your originals and exports.
What file types work?
CSV, TSV and tables pasted from a spreadsheet work, as long as the first row holds the column names. Separators comma, semicolon, tab and vertical bar are detected. Excel date serial numbers, PDF files and photos of paper pages are not read.
What happens to rows with errors?
The preview lists each error with its row number, column and a message. Rows with errors are not counted in the totals check, so they appear as a difference. Fix them in your table and paste it again.
How are duplicates found?
A row is a possible duplicate when its date, registration, from, to, total time and simulator time match another row, in the same file or in the logbook already in this browser. Those rows are skipped by default. Untick the skip-duplicates checkbox to keep them.
Is anything uploaded?
No. Nothing is uploaded, and the table is read in your browser. The web logbook on the home page uses the same browser storage, so rows added from this tool appear there.
Related tools
- Pilot logbook: use it to keep the flights the readable rows are added to.
- Pilot logbook template: use it when you want printable layouts to write on by hand.
- Pilot currency checker: use it to check currency once your flights are in order.
- Night time calculator: use it to work out night hours for a flight.
- Flight time calculator: use it to work out the time between airports for the total time column.
- Zulu time converter: use it to convert logbook times between local time and UTC.
- Logbook tools: use it to see every logbook tool on one page.