Flight-Data Review Sheet
Record the question, population and exclusions before interpreting a percentage. The exercise below uses fictional flight summaries.
Print with your browser or save as PDF. Fill in by hand; no information is submitted.
Define the analysis
| Question / period / fleet or sample | |
|---|---|
| Data source / format / units / version | |
| Duplicate key / completeness rule / flag meaning |
Keep the denominator visible
| Count | Fictional example | Your analysis |
|---|---|---|
| Received records | 12 | |
| Unique flights | 11; F07 duplicated | |
| Usable flights | 10; F11 incomplete | |
| Flagged usable flights | 2; F03 and F08 | |
| Flagged / usable × 100 | 2 / 10 × 100 = 20% |
Exercise rule: retain one record per flight_id, then require all 60 expected samples. F11 has 42. Dividing 2 by all 12 received records gives 16.7%, using the wrong population for this question. The flag has no aircraft-safety meaning.
Review and follow-through
| Exclusion reasons / quality concerns | |
|---|---|
| Context needed / reviewer / decision | |
| Action owner / expected effect / next review |
Sample and field definitions: yenra.com/flight-data/fictional-monitoring-sample.json. Open JSON in a text editor or analysis tool.
Prepared September 11, 2026. Conceptual background: FAA AC 120-82. Apply your authorized program’s rules to real data.
Guide: yenra.com/flight-data/