Download the examples
These files are not real flight records. Do not import them into ForeFlight.
- Five-flight example — 5 included rows, 8.7 hours, No issues found, with two landing-column names the checker does not treat the same
- Findings example — 5 included rows, 7.6 hours and 8 possible issues, including four excluded rows and one invalid PIC cell
Aircraft SYN-EX1 / SYN-EX2 and airports XXAA / XXBB / XXCC are labels. After download, drop the file on the checker in this browser, or add the rows in a spreadsheet.
ForeFlight’s export help describes a CSV export from ForeFlight on the Web: Logbook → Export tab → Export. Use that article for current menus. You need ForeFlight’s on-screen figure, the CSV as text, and — if you want flags — the checker report for the same file.
Five flights that add to 8.7
Independent addition of TotalTime matches the checker: 8.7 hours.
| Line | Date | TotalTime | Hours |
|---|---|---|---|
| 8 | 2024-03-02 | 1.2 | 1.2 |
| 9 | 2024-03-09 | 1.5 | 1.5 |
| 10 | 2024-03-16 | 2.1 | 2.1 |
| 11 | 2024-03-23 | 3:06 | 3.1 |
| 12 | 2024-04-06 | 0.8 | 0.8 |
1.2 + 1.5 + 2.1 + 3.1 + 0.8 = 8.7.
| Category | Sum in this file |
|---|---|
| PIC | 7.7 |
| Dual received | 2.3 |
| Cross country | 7.9 |
| Night | 1.6 |
| Solo | 0.8 |
| Day landings (mapped name) | 6 |
| Night landings (mapped name) | 1 |
| All landings (mapped name) | 7 |
| Landing column | Sum | In the checker? |
|---|---|---|
DayLandingsFullStop | 6 | Yes — this is the day-landing total |
Landing Full-Stop Day | 7 | No — listed under Not checked |
The banner is No issues found (5 rows, 8.7 h, 2024-03-02 → 2024-04-06). Not checked: Route, DualGiven, Landing Full-Stop Day, Approach1, PilotComments. Dual given 0.8 in the file never entered dual received: DualReceived is summed, DualGiven is not.
If your app says 9.1 against 8.7, the gap is 0.4. That is a comparison, not a diagnosis of why the two figures differ. Compare ForeFlight’s total time with TotalTime, and ForeFlight’s day landings with the landing column the checker actually mapped.
Line 9 has total 1.5, PIC 0.5, dual received 1.5, cross country 1.5, and night 0.4. Each mapped column is added on its own. Whether a flight may carry more than one of those categories is a question for the original record and the rules that apply to it — not for this checker.
Aircraft Table rows sit above the Flights header and are not counted as flights.
When you drop this file on the checker, confirm 5 included rows and 8.7 hours before you trust a green banner. The unchecked landing column still holds 7, which never entered the day-landing total of 6.
A second file with planted problems
This generic CSV has no blank lines, so file line = report line. Five rows are included. Their totals: 1.2 + 1.2 + 2.0 + 1.8 + 1.4 = 7.6.
| Line | Date | Total | What happens |
|---|---|---|---|
| 2 | 2024-05-02 | 1.2 | Included. First copy |
| 3 | 2024-05-02 | 1.2 | Included. Possible duplicate of line 2. Still in 7.6 |
| 4 | 2024-05-09 | x1.5 | Unreadable total. Listed. Left out |
| 5 | zz-not-a-date | not-a-time | Both unreadable. Listed and excluded |
| 6 | 03/04/2024 | 1.0 | Ambiguous date. Listed. Left out |
| 7 | 2024-05-16 | 2.0 | Included. PIC −0.5 stays in the CSV PIC; review PIC omits it |
| 8 | 2031-08-01 | 1.8 | Included. Future count +1. The future check does not print this line |
| 9 | 2024-05-23 | 1:75 | Invalid total: minutes must be 00–59. Listed and excluded |
| 10 | 2024-05-30 | 1.4 | Included. PIC oops is listed as an unreadable cell and excluded from PIC only. Night 0.3 is added |
PIC CSV 3.7. PIC review 4.2. Night 0.3. Cross country 1.8. Day landings 6. Banner 8 possible issues: four unreadable rows, one unreadable PIC cell, one possible duplicate, one negative value and one future date.
Add the included cells yourself. Then read the issue list. Then read Not checked. Type 7.6 into Your app to see a match. A figure of 8.0 shows +0.4 · review. Hours display to one decimal, so compare the cells themselves when a rounded display could hide a smaller difference.
Chase a mismatch
- Download a file above, or export your own CSV using ForeFlight’s export help.
- In a spreadsheet, add the total-time column for rows that have a readable date and total.
- Drop the same file on the checker. Confirm included rows, CSV total, Not checked, and the five issue categories.
- Type ForeFlight’s figure into Your app. A gap under 0.05 prints as a match; it is not exact to the minute.
A remaining gap can come from a different export, category or unchecked column, as well as records that need closer inspection. A green banner does not identify the cause.
ForeFlight’s auto-export article describes the CSV format as excluding signatures, endorsements, photos, and track logs. A CSV and its numeric totals cannot prove that attached items in the original records are preserved; verify those separately.
What to inspect yourself
Same checker as /checker. Limits that often explain a surprise total:
- At least three recognized column names in the first 2,000 physical file lines, plus a Date column and a total-time column.
- Rows where either or both date and total fail are excluded and listed with their physical source line.
- Empty optional cells stay missing. Non-empty invalid values in mapped columns are listed separately and excluded from that category only.
h:mmrequires minutes 00–59. Landings require whole-number counts; time notation and fractional counts are rejected.- Quoted line breaks and escaped quotes stay in one CSV record. Line numbers refer to its first physical file line. Named table sections and explicit totals or note footers bound the flight table; unfamiliar layouts may still need review.
- Possible duplicates stay in the sum. Review total only drops negatives.
The on-page sample on the checker is a separate fictional 11.7-hour table.
Once the checker page has loaded, reading a file already on the device does not need a network. Downloading these examples the first time does. The checker does not change the CSV. Privacy.