Skip to content
FRSign inBook a walkthrough
FDMFlight Data MonitoringSafety Management

Flight data monitoring, kept apart from your occurrence numbers.

In 50 words

Flight data monitoring reviews recorded flight data for exceedances, such as an unstable approach or a hard landing, so trends are seen before they cause harm. In eAviora imported exceedances are their own records, kept out of occurrence counts, matched to the crew reports that describe them, and followed up with crews through a named gatekeeper.

Case file | SMS-FDM-2026-0311Stage 2 of 4, Review
  • Overview
  • Workflow
  • Linked
  • Discussion
  • History
An FDM event, in review
01Detected, done02Review, current03Assessed, not reached04Closure, not reached
Linked toOCC | GOV | CAP
Sample data | Northwind Air, a fictional airline
At a glance

The module, on one sheet.

Module sheet | FDM
SuiteSafety Management | Safety Governance
Regulatory basisICAO Doc 9859 FDM program, EASA ORO.AOC.130
ICAO Doc 9859EASA ORO.AOC.130
RecordsSMS-FDM events, de-identified at import
Stages
01Detected02Review03Assessed04Closure
Event levelsLevel 1, 2 or 3, kept apart from the ICAO severity a person sets
Level 1Level 2Level 3
What it does

Four things, done on the record.

Exceedances, 12 monthsRate per 1,000 flights | Dec 2025 to Nov 2026 | 2.4 in November | not counted as occurrences
FDM events, 12 monthsDe-identified at import | Sample data | Northwind Air, a fictional airline
01De-identified at the doorThe import refuses any column that looks like a crew identity, so none is ever stored.
02Matched to the crew reporteAviora proposes the report that describes the same event, and a person accepts the link.
03The report nobody filedA level 2 or 3 event with no matching report after the reporting window is raised for review.
04Crew contact through a gatekeeperOne named gatekeeper contacts the crew and records only a de-identified outcome.
In the product

An FDM event, in review.

Case file | SMS-FDM-2026-0311Stage 2 of 4, Review
  • Overview
  • Workflow
  • Linked
  • Discussion
  • History
On the recordThe event code, its level, and the recorded and threshold values.
VRTG-TD | vertical acceleration at touchdown | level 2 of 3
The reviewThe review disposition and its notes.
DispositionValid eventCrew reportSMS-OCC-2026-0412
Gusts of 27 kt on the approach. Matches the crew report filed the same day.
On the recordThe crew contact.
RequestedObtainedDeclinedNot applicable
Only the named gatekeeper records the outcome. No field holds a crew identity.
Sample data | Northwind Air, a fictional airline
The rule it holds

Only the gatekeeper closes a crew contact.

  • Not even an administrator can record the outcome of a crew contact; only the named gatekeeper can, and no field holds a crew identity.Flight Data MonitoringHolds
GatekeeperRecords the outcome of a crew contactde-identified
AdministratorCannot record it
Questions buyers ask

Short answers.

No. They are their own record type, so they never enter an occurrence list, count or reporting rate.

Reading | Risk and intelligenceWeak Signals in Aviation Safety: Seeing Risk Before It Becomes an OccurrenceReading | Risk and intelligenceOperational Drift: The Risk Nobody ReportsReading | Risk and intelligenceLeading Indicators vs Lagging Indicators in Aviation Safety
All of Risk and intelligence

See Flight Data Monitoring on your own records.

A walkthrough with the people who build eAviora.