Reports is where Flight Data Monitoring (FDM) aggregates detected events into analytics you can read across your whole operation.
Reports summarize included, FSP-matched events only. A flight's events are counted here only when the flight is matched to FSP and the event is marked as included. Events on unmatched flights, or events excluded from reporting, do not appear in these analytics.
Open Reports
In the FDM left sidebar, select Reports. The page is titled Reports with the subtitle "Aggregated flag analytics · included, FSP-matched events only."
The page has two parts: a grid of report cards and a Flags overview widget.
Read the Flags overview
The Flags overview widget gives you the operation-wide summary at a glance:
The total included flags and the flags per flight rate (for example, 2,097 included flags at 25.27 per flight).
A severity bar breaking flags into P1, P2, P3, and Unrated.
A Most common list of the top flag types with their counts (for example, Uncoordinated Flight, Stall Approximation, Takeoff Excessive Pitch).
An Open Flags → link that takes you to the full flag list.
Use this widget to see, at a glance, how many flags your operation is generating, how they break down by severity, and which flag types are most frequent.
Choose a report
Each card opens a focused report. Select a card to open it.
Flags — all detected events by severity, type, and dimension. This is the broad view of every flag.
P1 Summary — your highest-severity events, broken down by month, aircraft, group, and airport.
Instructor-wise — flags and rates broken down per instructor.
Student / Pilot — flags and rates broken down per pilot.
Aircraft — flags, rates, and utilization by tail and group.
Approach limits — approach-context deviations treated as their own flag category.
Pick the report that matches the question you are asking — for example, use Aircraft to compare tails, Instructor-wise or Student / Pilot to compare people, and Approach limits to focus on the approach phase.
Because Reports only counts included, FSP-matched events, a report can look empty or sparse if few flights in the selected range are matched to FSP. If a report is missing expected data, confirm the underlying flights are FSP-matched and their events are included in reporting.
Troubleshooting
A report shows fewer flags than I expected. Reports count included, FSP-matched events only. Events on unmatched flights, or events excluded from reporting, are left out. Check that the flights you expect are matched to FSP.
I don't see a pilot, instructor, or aircraft I expected. People and aircraft appear in these reports only when they have included, matched flags in range. If a pilot's or aircraft's flights are unmatched, they will not show up in Instructor-wise, Student / Pilot, or Aircraft reports.
I want the raw flag list, not a summary. Use the Open Flags → link in the Flags overview, or open the Flags report card, to reach the full list of detected flags rather than the aggregated views.