Public sample · No signup or payment required
See what an audit actually shows you.
Before you spend $149, inspect a finding, trace it to its source records, and see what needs clarification. This example uses FlightVerify’s audit engine and report format with five fictional entries.
Three issues you can inspect
A flag explains what was found and what to review. It does not automatically remove an entry or award flight-time credit.
Potential exact duplicates — source evidence insufficientPotential Conflict · DATA-001
2 flight records share a normalized fingerprint (date, aircraft, route, times, landings) but no preserved source evidence is available to confirm they are identical. These are potential duplicates, not confirmed.
Why it matters: Normalized fingerprints match, but without preserved source rows FlightVerify cannot prove the records are identical. These are flagged for review, not as confirmed duplicates.
Next step: Review each potential match in the Flight Table. Source evidence is insufficient to confirm; treat as review only.
| Row | Date | Aircraft | Route | Total h |
|---|---|---|---|---|
| 2 | 2026-08-01 | SAMPLE-A | KAPA → KCOS | 1.2 |
| 3 | 2026-08-01 | SAMPLE-A | KAPA → KCOS | 1.2 |
Night exceeds total timeDeterministic Conflict · TIME-005
1 flight record(s) log night greater than the flight's total time.
Why it matters: A single flight cannot include more night than total time. This is a deterministic arithmetic conflict.
Next step: Correct the logged value or the total time in the source file and re-import.
| Row | Date | Aircraft | Route | Total h |
|---|---|---|---|---|
| 4 | 2026-08-02 | SAMPLE-A | KAPA → KCOS | 1.2 |
Aircraft or training-device type needs clarificationClarification Required · ACFT-005
Aircraft or training-device type is not established for some records. Confirm the equipment type in your source logbook and re-upload it. FlightVerify will not infer aircraft credit from a model, engine or represented aircraft class.
Why it matters: Model, engine and represented class do not establish physical aircraft time.
Next step: Aircraft or training-device type is not established for some records. Confirm the equipment type in your source logbook and re-upload it. FlightVerify will not infer aircraft credit from a model, engine or represented aircraft class.
| Row | Date | Aircraft | Route | Total h |
|---|---|---|---|---|
| 5 | 2026-08-03 | SAMPLE-B | KAPA → KCOS | 1.2 |
When the record doesn’t establish the answer, we ask.
Was SAMPLE-B a physical aircraft or a training device? Provide the equipment type and supporting source details before equipment-dependent credit is determined.
Equipment-dependent totals remain incomplete while this is unresolved. A known subtotal is not a complete verified total.
Inspect the sample report
View the full report generated for these five fictional entries, including the remaining findings, methodology and limitations.
Bring this level of scrutiny to your own logbook.
A self-service logbook software audit with discrepancy explanations and clarification of ambiguous entries. $149 once includes 30 days of re-uploads, audit reruns and downloadable reports.
Supported electronic exports: ForeFlight, LogTen and MyFlightbook. Your original logbook is never modified.
Start My Audit — $149