How to Identify, Classify and Respond to Safety Occurrences
Why Incident Classification Matters
When something goes wrong, the first question is:
What type of event is this?
Correct classification determines:
- whether it is reportable
- who it must be reported to
- how quickly action must be taken
- what level of response is required
Incorrect classification can result in:
- under-reporting (regulatory risk)
- over-reporting (administrative burden)
- poor safety decisions
The Four Core Categories
In RPAS operations, safety occurrences can be broadly classified into:
- Accident
- Serious Incident (IRM)
- Incident (RRM)
- Near Miss / Hazard (Internal Reporting)
Each category has different implications.
1. Accident
Definition
An accident is an occurrence involving an aircraft where:
- a person is killed or seriously injured, or
- the aircraft sustains major damage or is destroyed
RPAS Examples
- drone strikes a person causing serious injury
- aircraft crashes into infrastructure causing major damage
- catastrophic structural failure in flight
Reporting Requirement
Immediately Reportable Matter (IRM)
- immediate notification required
- written report within 72 hours
2. Serious Incident (IRM)
Definition
A serious incident is an event that:
could have resulted in an accident under slightly different circumstances
RPAS Examples
- loss of separation with crewed aircraft
- flyaway with significant risk to people or property
- major system failure affecting control
- collision with bird causing loss of control
- high-risk near collision
Reporting Requirement
Immediately Reportable Matter (IRM)
- report immediately (phone)
- written report within 72 hours
3. Incident (RRM)
Definition
An incident is an occurrence that:
affects or could affect the safety of the operation but is not immediately critical
RPAS Examples
- minor collision with object
- temporary loss of control
- airspace breach without immediate danger
- equipment malfunction affecting operation
- minor property damage
Reporting Requirement
Routinely Reportable Matter (RRM)
4. Near Miss / Hazard (Internal Reporting)
Definition
An event where:
no damage or injury occurred, but there was clear potential for it
RPAS Examples
- near collision with obstacle or aircraft
- incorrect flight planning identified before take-off
- loss of situational awareness corrected in time
- weather conditions deteriorating during operation
Reporting Requirement
Internal reporting only (unless thresholds are met)
These events are critical for:
- identifying trends
- improving procedures
- strengthening safety systems
IRM vs RRM — Quick Comparison
| Category | Severity | Examples | Reporting Timeframe |
| Accident | Very high | Injury, major damage | Immediate + 72 hrs |
| Serious Incident (IRM) | High | Near collision, flyaway risk | Immediate + 72 hrs |
| Incident (RRM) | Moderate | Malfunctions, breaches | Within 72 hrs |
| Near Miss | Low–Moderate | No damage, high potential | Internal only |
Key Decision Question
When assessing an event, ask:
“Could this have reasonably resulted in serious injury or major damage?”
If the answer is:
- Yes → IRM
- No, but still safety-relevant → RRM
- Low consequence → Internal reporting
Common Classification Scenarios
Scenario 1 — Flyaway Over Open Area
- Aircraft loses link but crashes in empty paddock
- No injury or damage
✔ Likely classification:
RRM (or internal depending on context)
Scenario 2 — Loss of Separation with Helicopter
- Drone observed within close proximity to crewed aircraft
✔ Likely classification:
IRM
Scenario 3 — Minor Tree Strike
- Aircraft clips tree branch, minor damage
✔ Likely classification:
RRM
Scenario 4 — Near Collision Avoided
- Pilot takes action to avoid collision
✔ Likely classification:
IRM (if high risk) or internal if low risk
Scenario 5 — Battery Failure on Ground
✔ Likely classification:
Internal reporting
Who Makes the Classification?
Within a ReOC operation:
Remote Pilot / Crew
- identify and report the event
Chief Remote Pilot (CRP)
- determines classification
- decides if reportable
- submits ATSB report
The CRP holds accountability for correct classification
Link to Safety Systems
Incident classification feeds directly into:
- Safety Management System (SMS)
- Risk Register updates
- Corrective actions
- Due Diligence Index (DDI) monitoring
It ensures:
events are not just recorded — they are understood and acted on
Common Mistakes
We frequently see:
- treating all events as minor
- misunderstanding IRM thresholds
- failing to report near misses internally
- inconsistent classification between pilots
- over-reliance on “no damage = no issue”
CRP Assessment Focus
Candidates are expected to:
- correctly classify events
- justify their classification
- explain reporting obligations
- link events to operational risk
This is commonly tested through:
scenario-based questioning
Practical Classification Framework
Use this simple process:
- What happened?
- What was the outcome?
- What could have happened?
- Was there a realistic risk of serious harm?
- Apply classification (Accident / IRM / RRM / Internal)
- Report accordingly
How Uncrewed Approvals Can Help
We support operators to:
- develop clear classification frameworks
- train pilots and CRPs
- integrate classification into SMS and DDI systems
- prepare for audits and regulatory review
We help operators move from:
uncertain judgement → consistent, defensible decisions
Frequently Asked Questions
What if I am unsure whether it is IRM or RRM?
Treat it as IRM and seek clarification.
Do near misses really matter?
Yes — they are often the most valuable safety data.
Who is responsible for reporting?
Does “no damage” mean no reporting?
No — risk and potential outcome are key factors.
Classify Early. Report Correctly. Learn Continuously.
Strong operators do not guess.
They:
- classify consistently
- report appropriately
- learn from every event
Good classification is the foundation of effective safety management
