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.

At a glance

The module, on one sheet.

Suite
Safety Management | Safety Governance
Records
SMS-FDMEvents, de-identified at import.
Stages
01Detected02Review03Assessed04Closure
Four stages, from Detected to Closure.
Event levels
Level 1Level 2Level 3
Level 1, 2 or 3, kept apart from the ICAO severity a person sets
Regulatory basis
ICAO Doc 9859EASA ORO.AOC.130
ICAO Doc 9859 FDM programme, EASA ORO.AOC.130
Works with
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.

On the record
VRTG-TD | vertical acceleration at touchdown | level 2 of 3
The event code, its level, and the recorded and threshold values.
The review
DispositionValid event
Crew reportSMS-OCC-2026-0412
Gusts of 27 kt on the approach. Matches the crew report filed the same day.
The review disposition and its notes.
On the record
RequestedObtainedDeclinedNot applicable
Only the named gatekeeper records the outcome. No field holds a crew identity.
The crew contact.
Drawn from the record | 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.

GatekeeperRecords the outcome of a crew contactde-identified
AdministratorCannot record it
Questions buyers ask

Short answers.

A buyerDo FDM events count as occurrences?

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

A buyerCan we see who flew?

eAvioraNo. The import refuses crew identity columns. When a crew must be contacted, the gatekeeper does it outside eAviora and records a de-identified outcome.

A buyerWhat do we import?

eAvioraThe exceedances your flight data programme already exports: event code, level, parameter, recorded and threshold values, flight phase, date and registration.

See Flight Data Monitoring on your own records.

A walkthrough with the people who build eAviora.

Cookies on eAvioraWe use a small set of cookies to keep the site working and your session signed in. Analytics stays off unless you turn it on. Read the cookie notice.