Template: completion of an incident report (MOR)
How to report an incident factually and in time
Incident reporting is not bureaucracy for bureaucracy's sake — it is the way the aviation industry systematically learns from near-misses before they become real accidents. Use this template next time you need to fill out an incident report.
§When should you report?
- 01You discover an incorrectly assembled part after release.
- 02You find a deviation from the procedure in already completed work
- 03You experience a near-miss even though nothing went wrong.
- 04Tools or parts have been forgotten in an open structure
- 05Documentation does not match the work performed
§The report must contain
| Field | What you write |
|---|---|
| What happened | Short factual description without judgment of guilt |
| Where and when | Plane/registration location date and time |
| Who was involved | Function/role, according to the company's reporting system |
| Immediate actions. | What was done immediately to secure the aircraft or situation |
| Your assessment | What you think contributed to the incident, if you have a guess |
§After death
- 01The case is investigated by the quality department, not by your immediate manager alone
- 02You can be contacted for follow-up questions
- 03You are in principle protected against retaliation under the Just Culture principle, unless there is gross negligence or intent
§Remember
- 01Write factually — not apologetically and not accusingly
- 02Also report when you are in doubt about whether the incident is 'serious enough'
- 03Use the same template each time so you don't forget fields under stress