Flight data monitoring, kept apart from your occurrence numbers.
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.
- Overview
- Workflow
- Linked
- Discussion
- History
The module, on one sheet.
Four things, done on the record.
An FDM event, in review.
- Overview
- Workflow
- Linked
- Discussion
- History
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
What it links to.
- From
- OCC
- To
- FDM
- From
- GOV
- To
- FDM
- From
- CAP
- To
- FDM
Short answers.
No. They are their own record type, so they never enter an occurrence list, count or reporting rate.
No. The import refuses crew identity columns. When a crew must be contacted, the gatekeeper does it outside eAviora and records a de-identified outcome.
The exceedances your flight data program 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.