No issues found means the current checks did not fire on the rows and columns they could read. It does not mean the file holds every ForeFlight record, and it is not an FAA or EASA finding.
Try the built-in sample first
Try with sample data loads a fictional table. It is not a real logbook. Six rows are included. Their total-time cells add to 11.7 hours, which is the CSV total the report prints.
| Line | Date | Total time | In the 11.7? |
|---|---|---|---|
| 2 | 2016-03-14 | 1.2 | Yes |
| 3 | 2016-03-21 | 1.4 | Yes |
| 4 | 2017-06-02 | 2.1 | Yes — first of a repeated pair |
| 5 | 2017-06-02 | 2.1 | Yes — flagged as a possible duplicate; still in 11.7 |
| 6 | 2019-11-08 | 3:06 | Yes — 3 hours 6 minutes is 3.1 |
| 7 | 2021-04-19 | x2.9 | No — unreadable total; left out |
| 8 | 2031-01-05 | 1.8 | Yes — dated in the future; still in 11.7 |
1.2 + 1.4 + 2.1 + 2.1 + 3.1 + 1.8 = 11.7. PIC on those same six rows is also 11.7. Night 1.2. Cross country 9.1. Day landings 8. Night landings 1.
The banner is 3 possible issues found: one unreadable total, one possible duplicate, one future date. Type 12.5 next to Total time to see +0.8 · review. That 12.5 is a demonstration figure, not a reading from a real logbook. The busy line counts every non-empty CSV record, including the header — 8 records here, then 6 included flights.
How to read the report
Four figures open the report: Rows included (date and total time both readable), CSV total (that total-time column added), Date range, and Parser confidence (Tested · ForeFlight when the file looks like a ForeFlight export; otherwise experimental matching). Hours display to one decimal. Landings display as whole numbers.
Type ForeFlight’s figure into Your app:
- Blank →
enter to compare - Invalid hour input →
enter a number; invalid landing input →enter a whole number - A difference smaller than 0.05 in the column’s unit →
✓ matches. For hours, 0.05 hours is three minutes.11.72against11.7matches.3:06against3.1matches. - A larger gap →
+0.8 · reviewor-1 · review
Review total is the CSV sum with negative cells left out. It is not a de-duplicated total. Possible duplicates stay in both columns. If CSV total and review total disagree, a negative value is in the file.
Displayed hours are rounded. 1:59 prints as 2.0. If a tenth of an hour matters, compare the cells in the file.
The issue banner counts unreadable rows, unreadable cells in included rows, possible duplicates, negative values, and future dates. Columns the checker did not recognize are not in that count. A file can show No issues found while landings or dual given sit under Not checked.
Rows with an unreadable date or total time are listed and excluded, including rows where both fail. Invalid values in other mapped numeric columns are listed separately; only that cell is excluded, while the row’s other valid values remain included. Slash dates such as 03/04/2024 are called ambiguous and excluded; YYYY-MM-DD is unambiguous. A possible duplicate is the same date, aircraft, route, and duration after ordinary cleanup (N172SP matches n172sp). Both rows remain in the CSV total. Future dates stay in the totals; the report prints a count, not each line — that is why the sample range ends in 2031.
Mapped versus Not checked is a coverage list, not a second green light. Total Time / TotalTime, PIC, night, cross country, dual received, and names such as DayLandingsFullStop are recognized. Landing Full-Stop Day and DualGiven are not. Worked files for those names are in the CSV totals guide.
What to inspect yourself
The checker does not rewrite your file. Limits of this recount:
- A header is accepted only when at least three recognized column names appear in the first 2,000 physical file lines. Date and total time alone are not enough.
- A row enters the totals only when both date and total time can be read. If either or both fail, the row is excluded and listed with its source line.
- Empty cells in other columns (PIC, night, landings) stay missing. Non-empty invalid values are flagged under Unreadable cells and omitted only from that category.
- Times written
h:mmrequire minutes from 00 to 59. Landing counts must be whole numbers; time notation and fractional counts are rejected. An integer written as1.0is accepted. - Quoted line breaks, escaped quotes, commas, tabs and semicolon delimiters are supported. Report lines identify the physical file line where a CSV record begins; a quoted multi-line record may occupy more than one line.
- If the file names a Flights Table, the header must be inside that section and within the first 2,000 physical lines. A later named table cannot replace it. Without that section marker, the checker uses experimental column matching.
- A following named table or an explicit note footer ends the flight section. In a Date-first layout, a standalone Summary/Total label or a numeric aggregate row can also end it. Those words in a Notes column do not end the table. Unclear non-empty rows, including damaged aggregate-looking rows, are reported instead of silently discarded. This is not a guarantee that every exporter’s layout is supported.
A match within this tolerance is not exact to the minute. A CSV and its numeric totals cannot prove that attached items in the original logbook are preserved; verify those records separately. ForeFlight documents how to export logbook data from ForeFlight on the Web.
Once this page has loaded, you can disconnect and read a file already on the device. That does not apply to downloading a new file. How the checker handles the selected file is on the privacy page.
If the on-screen ForeFlight total and this CSV total still disagree, use the CSV totals guide.