How to Monitor and Triage Events

Browse detected safety events, filter by phase or rule, tag them, and control which events feed your operation's reports and flag analytics — all within Safety Hub.

Overview

The Events page lists all safety events (exceedances) automatically detected by the system during flight data processing. Events are generated by Event Definition Sets — configurable collections of exceedance rules that your administrator defines. Each event represents a flight parameter that exceeded a configured threshold, such as low altitude, excessive roll angle, high G-forces, or excessive descent rate.

When events are detected, FDM sends notifications to configured recipients through email, SMS, or both — so the right people know within minutes, not days.

The Events List

Select Events in the FDM left sidebar.

The FDM Events page — the active Definition Set picker and draft banner at the top, the flight-phase context tabs, the rules table with per-rule event counts, and the events table below with each row showing a condition expression, a phase badge, and an Add tag action

At the top of the page, the active Definition Set appears in a picker with an Active badge (for example, "G1000 Legacy · Active"), alongside Manage Set and New Set. A draft banner summarizes the set's state — for example, "v43 pending · v42 live · 58 rules" — with controls to view History, View Live (v42) (open the currently published version), Discard Draft, and Publish Rules. See the "Configure Event Definition Sets" article for authoring rules.

Below the definition-set header, the events table displays detected events in reverse chronological order with the following columns:


Column	Description
Date	Date and time the event occurred, with the flight time shown below.
Event	Event name plus a condition expression and a phase badge — e.g., "Possible Wake Turbulence · WakeTurbulence = DETECTED · on-ground", or "TrafficLateral < 2500ft AND TrafficVertical < 500ft".
Priority	Priority level — P1 — Safety Critical, P2 — Operational, or P3 — Training.
Pilot	Pilot name if the flight was matched to an FSP record. Displays "—" when unmatched.
Aircraft	Aircraft tail number.
Route	Airport identifiers for the flight route.
Tags	The Add tag action (Tag button) plus any tags applied to the event.
Value (Actual / Threshold)	The recorded value versus the threshold that was exceeded (e.g., "1,320 / 2,500"). Shows "— / —" when a threshold does not apply, such as a detection-only rule.

The total event count is displayed in the pagination footer below the table (e.g., "Showing 1-25 of 19318 · Page 1 of 773").

The Rules Table

Above the events table, the rules for the selected flight-phase tab are listed with a per-rule event count in the Events column. Each rule shows its priority and a condition shorthand (for example, "GS > 20kts • 6s • Taxi"). On each rule you can:

Filter events to this rule — narrow the events table to only the events that rule generated.
Remove rule — delete the rule from the draft set (requires the Manage Event Definitions permission).

Use Add Rule to add a new exceedance rule to the current phase.

Understanding Priority Levels

Each exceedance rule in an Event Definition Set is assigned one of three priority levels:

P1 — Safety Critical — The highest priority. Events at this level indicate conditions that warrant immediate attention and review.
P2 — Operational — Mid-level priority. Events at this level are significant but not immediately critical. This is the default priority for new rules.
P3 — Training — Lower priority. Events at this level are typically used to flag training observations rather than safety emergencies.

Your administrator configures which rules map to which priority when building Event Definition Sets.

Understanding Event Types

Events are generated by exceedance rules configured in your organization's Event Definition Sets. The rule builder supports 36 parameters across all flight phases. Common event types include:


Event Type	Parameter	What It Monitors
Low Altitude AGL	Altitude AGL	Aircraft altitude above ground level dropped below the configured threshold.
LOC-I Indicators via Roll	Roll Angle	Roll angle indicators associated with loss of control — in-flight (LOC-I).
Excessive Positive G	Normal Acceleration (G)	G-force exceeded the configured positive G limit.
Sustained High G	Normal Acceleration (G)	G-forces remained above the threshold for an extended duration.
Excessive Descent Rate	Vertical Speed	Descent rate exceeded the configured threshold.
Overspeed	Indicated Airspeed	Airspeed exceeded the aircraft's Vne or Vno value.
Excessive Bank Angle	Roll Angle	Bank angle exceeded the threshold, often filtered to specific phases of flight.
Unstable Approach	Multiple	Airspeed, descent rate, or glidepath deviation during the approach phase.
Airspace Violation	Airspace Class	Aircraft entered an airspace class that triggered a configured rule.
Engine Over-Temp	Cylinder Head Temp / EGT	Engine temperature parameter exceeded the configured limit.
Wake Turbulence Risk	Wake Turbulence Risk	Proximity conditions associated with wake turbulence exposure.
ADS-B Emergency	Emergency State (ADS-B)	Aircraft broadcasting an ADS-B emergency squawk code.

Your administrator can define rules for any of the 36 supported parameters — the types above are examples of common configurations.

How Event Detection Works

Each exceedance rule can be configured with several parameters that control when it triggers:

Flight context — Rules apply only during specific phases of flight (On Ground, On Takeoff, In Flight, On Approach, At Touchdown, or Anytime). For example, a bank angle rule might only monitor during the approach phase.
Maneuver filtering — Rules can be scoped to include or exclude specific maneuvers (e.g., steep turns, slow flight, stalls). This lets your administrator target detection precisely.
Priority levels — Each rule has a priority (P1 Safety Critical, P2 Operational, P3 Training) that helps your team triage which detected events to investigate first.
Duration — Some rules require the condition to persist for a minimum duration before triggering (e.g., sustained high G for more than 5 seconds). A duration of 0 means the rule fires instantly.

Searching Events

Use the search bar above the events table to search events by keyword — pilot name, aircraft tail number, or event type.

Filtering by Flight Phase

A row of context tabs sits above the tables: On Ground, On Takeoff, In Flight, On Approach, At Touchdown, and Anytime. Select a tab to show only the rules and events for that phase of flight.

Filtering Events

Click the Filters button above the events table.
The Filters panel provides options such as Pilot, Aircraft, Priority, and Date range.
Adjust filters as needed. The events list updates automatically.

To narrow the list to a single exceedance rule, use Filter events to this rule on any rule in the rules table above. The active Definition Set and version also scope which events are displayed.

Exporting Events

Click the Export button above the events table (it has a dropdown chevron) to download the current event list. The export honors whatever phase tab, filters, and search term are active, so you can export a targeted slice — for example, all P1 events for one aircraft over the last 30 days. Choose a format from the Export menu:

CSV — tabular data for spreadsheets or further analysis.
PDF — a formatted report suitable for offline review or sharing with auditors and regulators.

Reviewing an Event

Select any event row to open the event detail drawer on the right.

The event detail drawer for a Possible Wake Turbulence event — a mini 3D map at the top, then Conditions, Event Details (Detected and Flight Time), Location, Contexts, a Report Inclusion section with Included/Exclude controls, and a Tags section with Add tag

The drawer shows the full context for the event:

Conditions — the rule expression that fired (e.g., "WakeTurbulence = DETECTED").
Event Details — when the event was Detected and the Flight Time it occurred.
Location — latitude, longitude, and altitude (MSL and AGL) of the event.
Contexts — the flight-phase badge(s) (e.g., "on-ground").
Flight Info — the aircraft and route for the source flight.

Report Inclusion

Detected events feed your operation's reports and flag analytics only when they are included. The Report Inclusion section of the event detail drawer controls this:

Included in reports (with a green check) means the event counts toward your Reports (flag analytics) and is protected against deletion when flight data is reprocessed.
Click Exclude to keep the event out of reports and analytics; click again to include it.

The drawer records who set the inclusion and when — shown as "Included by {name} on {date}". Your default include/exclude behavior is configured in Settings → Reporting (auto-include vs. require human review).

Note: Report inclusion — not tags — is what protects an event from deletion on reprocess. Tag an event to organize or label it, but include it in reports to make it durable.

See the "Using FDM Reports" material for how included events roll up into flag analytics (by flag type, instructor, student/pilot, aircraft, and approach limits).

Tagging an Event

Each event row and the event detail drawer expose an Add tag action. Tags let your team label and group events — for example, to mark events reviewed by an instructor or grouped by campaign. Tagging does not change an event's report inclusion.

Escalating an Event to a Safety Report

When an event warrants formal follow-up, use Create Safety Report to escalate it into Safety Hub. This action is available in the event detail drawer and on the Flight Detail view. Escalating carries the event's context into a new safety report so your Safety Team can investigate and track it through to resolution.

Pagination

The list displays 25 events per page. Use the Previous and Next buttons at the bottom to navigate between pages. The current page and total are displayed (e.g., "Page 1 of 773").