INVInvestigationsSafety Management
Aviation safety investigations, from mandate to approved report.
In 50 words
A safety investigation establishes what happened, why it happened, and what must change so it does not happen again. In eAviora an investigation moves from its mandate through fact finding, analysis, findings and reporting, its recommendations become tracked actions, and its report is approved by someone other than the lead investigator.
- Overview
- Workflow
- Linked
- Discussion
- History
An investigation, in analysis
01, done02, done03, current04, not reached05, not reached06, not reached07, not reached
Linked toOCC | HAZ | CAP | GOV
At a glance
The module, on one sheet.
Module sheet | INV
SuiteSafety Management | Safety Operations
ICAO Annex 19Component 2, safety risk management. FAA Part 5 uses the same component.
RecordsINV investigations, linked to the occurrence they examine
Stages
01Mandate02Fact finding03Analysis04Findings05Reporting06Review and approval07Closure
Methods5-Why, bow-tie, fishbone, HFACS, SHELL, MEDA, REDA, PEAR and the Dirty Dozen
5-WhyBow-tieFishboneHFACSSHELLMEDAREDAPEARDirty Dozen
What it does
Four things, done on the record.
5-Why, hard landing on runway 24R
The eventHard landing, 2.1 g
Why 1The flare started late
Why 2Gust response replaced the flare cue
Why 3, root causeNo gust margin applies below the limit
Findings, with their evidence
FactualTouchdown at 2.1 g after a late flareQAR extract, flight 412.csv
SafetyNo gust margin applies below the crosswind limitCrew statement.pdf
01A mandate firstThe scope, what the investigation does not cover and its independence are set before fact finding.
02Depth that fits the eventLight, standard or deep: the depth sets which checks apply, and a deep review rates every barrier.
03Findings with their evidenceFactual and safety findings each cite the evidence that supports them.
04Recommendations become actionsEach recommendation names the department it is addressed to, and raises an action or links one that exists.
In the product
An investigation, in analysis.
- Overview
- Workflow
- Linked
- Discussion
- History
On the recordThe root cause, the contributing factors and the just culture outcome.
Root causeNo gust margin applies below the crosswind limitrecorded 2026-11-09 by S. Okafor
ContributingGust response replaced the flare cuegusts of 27 kt on the approach
Just cultureHuman errorconsole and support, review the system factors
On the recordThe barriers the event challenged, and the ones that failed.
PreventiveStable approach calloutsfailed | ineffective
PreventiveCrosswind operational limitweak | partially effective, proposed
RecoveryHard landing inspectionheld | effective
On the recordThe occurrence it examines, and the actions its recommendations raised.
The rule it holds
The lead investigator does not approve their own report.
- The lead signs the report off and someone else approves it, unless the lead is the accountable manager.InvestigationsHolds
LeadS. Okafor signs the report off
ApproverSomeone else approves itunless the lead is the accountable manager
On the graph
What it links to.
OCC | Linked recordOccurrencesThe event the investigation examines.
- From
- OCC
- To
- INV
- From
- HAZ
- To
- INV
- From
- CAP
- To
- INV
- From
- GOV
- To
- INV
Also in Safety OperationsOccurrencesHazardsFlight Risk AssessmentAerodrome Risk AssessmentThe Safety Management suite
Questions buyers ask
Short answers.
Nine: 5-Why, bow-tie, fishbone, HFACS, SHELL, MEDA, REDA, PEAR and the Dirty Dozen. The investigation records which one it used.
No. The lead signs it off, then someone else approves it. The one exception is an accountable manager leading the investigation.
Yes. Before the report is finished, the investigation records whether it is reportable to the authority.
Reading | SMS fundamentalsThe Investigation Methods Most Tools Document, eAviora ComputesReading | SMS fundamentalsJust Culture in Five QuestionsReading | SMS fundamentalsWhat Happens After an Occurrence Report: The Six Stages
All of SMS fundamentalsSee Investigations on your own records.
A walkthrough with the people who build eAviora.