Study guide
14.5 Accident and Incident Reporting to the ATSB
CASA Remote Pilot Licence RePL
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 About the RePL Exam 1.2 How to Use This Guide & Build a Study Plan
2 RPA Air Law: Regulatory Framework & Standard Operating Conditions
2.1 CASR Part 101 and the Manual of Standards 2.2 Standard Operating Conditions (SOC) 2.3 The 120 m (400 ft) AGL Height Limit 2.4 VLOS, Daylight, Visibility and the One-RPA Rule
3 RPA Air Law: Licensing, Categories & Approvals
3.1 RePL vs ReOC: Pilot Licence vs Operator Certificate 3.2 Excluded Categories and Operator Accreditation 3.3 RPA Weight Categories and Registration 3.4 Operating Beyond the SOC: Approvals and the ReB1
4 Basic Aviation Knowledge (RBAK)
4.1 Direction, Wind Velocity and Aviation Time 4.2 Units of Measurement: Height, Altitude and Elevation 4.3 Aerodynamics: Lift, Drag, Thrust, Weight and Energy 4.4 Weight and Balance: Terms and Limits 4.5 Propellers and Rotors 4.6 Axes, Attitude and Flight Control Principles 4.7 The Remote Pilot Station
5 RPAS Systems: Platforms, C2 Link & Power
5.1 Multirotor vs Fixed-Wing Characteristics 5.2 Command-and-Control Link and Failsafes 5.3 Lithium-Polymer Battery Management and Safety
6 RPAS Systems: Sensors, Payload & Preflight
6.1 GNSS, Compass, IMU and Geofencing 6.2 Payload, Centre of Gravity and Pre-Flight Checks 6.3 Automated Flight Management Systems (RAFM)
7 Electrical & Electronic Systems (REES)
7.1 Electrical Terms and RPAS Electrical Components 7.2 Electric Motors, Kv and Current Draw 7.3 Battery Types, Specifications and Dangerous Goods 7.4 Charging, Discharging, Balancing and Battery Limitations 7.5 Radio Waves, Frequency Bands and Propagation 7.6 GPS Components, Errors and Electromagnetic Hazards
8 Multirotor Aerodynamics & Performance (RBKM)
8.1 Multirotor Airframe and Component Layout 8.2 Rotor Aerodynamics: Blade Design, Thrust, Drag and Torque 8.3 Hovering: Ground Effect, Recirculation and Translational Lift 8.4 Multirotor Flight Controls, Stabilisation and GPS Hold 8.5 Motor Failure, Rotor Direction and Abnormal Aerodynamics 8.6 Weight, Power, Wind and Climb Performance 8.7 Descent, Vortex Ring State and Landing
9 Navigation & Charts
9.1 Chart Fundamentals: Latitude, Longitude, Variation and Distance 9.2 Visual Terminal Charts and Visual Navigation Charts 9.3 Airspace Classes, Control Zones and CTA Steps 9.4 Restricted, Danger and Prohibited Areas and Obstacles 9.5 NOTAMs, the AIP and Chart Currency
10 Meteorology
10.1 Wind, Sea Breezes and Local Effects 10.2 Turbulence, Orographic Effects and Terrain 10.3 Thunderstorms, Fronts and Fog 10.4 Density Altitude, METAR/TAF and BoM Forecasts 10.5 Weather Observations: Reading the Sky and the Site
11 Human Factors
11.1 IMSAFE, Fatigue and Complacency 11.2 Situational Awareness, Fixation and External Pressure 11.3 Alcohol, Drugs and Crew Resource Management 11.4 Vision, Visual Limitations and Illusions 11.5 Stress and Stress Management 11.6 Threat and Error Management
12 Radio & AROC
12.1 Phonetic Alphabet, Phraseology and CTAF 12.2 The 121.5 MHz Emergency Frequency, Transponder Codes and the AROC
13 Risk & Operational Procedures
13.1 Job Safety Assessment, Risk Assessment and the Hierarchy of Controls 13.2 Site Survey, Bystander Management, Emergencies and Giving Way
14 Operations, Airworthiness & Reporting (RKOP)
14.1 Remote Pilot Responsibilities, Crew Briefing and Ground Operations 14.2 Operational, Remote Pilot and Technical Logs 14.3 Airworthiness, Serviceability and Defect Reporting 14.4 Role Equipment, Sensors and Payload Implications 14.5 Accident and Incident Reporting to the ATSB 14.6 Abnormal Operations, Fail-Safes and Flight Termination 14.7 Operating Near Aerodromes and Above 400 ft AGL
14.5 Accident and Incident Reporting to the ATSB
Key Takeaways Explain This Topic AI
Reporting is required under the Transport Safety Investigation Regulations 2021, which replaced the 2003 regulations, and reports go to the ATSB rather than to CASA.
Type 1 RPA are type-certified, large (over 150 kg) or medium (over 25 kg to 150 kg); Type 2 RPA are everything else that is not an excluded or micro RPA.
Immediately reportable matters are phoned to the ATSB as soon as reasonably practicable, with a written report within 72 hours; routine reportable matters are reported within 72 hours.
The ATSB is a no-blame safety investigator: its function is to improve safety, not to apportion fault or take enforcement action.
Last updated: August 2026
Two Regulators, Two Jobs
Australian aviation safety has two federal bodies and remote pilots must not confuse them.
The Civil Aviation Safety Authority (CASA) writes and enforces the rules. It issues licences and certificates, conducts surveillance and audits, and takes enforcement action where the rules are breached.
The Australian Transport Safety Bureau (ATSB) investigates occurrences to improve safety. It collects, analyses and disseminates information about accidents and incidents. Critically, the ATSB does not apportion blame — it is a no-blame safety investigator, and its reports are not used for enforcement.
Occurrence reporting goes to the ATSB , under the Transport Safety Investigation Regulations 2021 , which repealed and replaced the 2003 regulations and introduced updated requirements for RPA operators.
Accident and Incident
Schedule 4 topic 5(a) asks for the definitions.
An accident is an occurrence associated with the operation of an aircraft in which a person is killed or seriously injured, the aircraft sustains serious damage, or the aircraft is destroyed or missing.
An incident is an occurrence, other than an accident, associated with the operation of an aircraft that affects or could affect the safety of operations. A serious incident is one where an accident nearly occurred.
For RPA the regulations translate these into two reporting classes:
Immediately reportable matters (IRM) — serious safety matters. Death, serious injury, significant damage to the RPA, collision with another aircraft including another RPA, or any matter where the ATSB may need to attend the site promptly to collect evidence.
Routine reportable matters (RRM) — occurrences that did not have a serious outcome but could have affected aviation safety. A non-serious injury, a near-miss with another aircraft including another RPA, a loss of control, or non-serious damage to the RPA.
Type 1 and Type 2 RPA
The 2021 regulations set different thresholds for two classes of aircraft, and this distinction is examinable.
Class Definition
Type 1 RPA Type-certified RPA; large RPA (more than 150 kg); or medium RPA (more than 25 kg but not more than 150 kg)
Type 2 RPA RPA that are not Type 1 and are not an excluded or micro (250 g or less) RPA
Type 1 operators must immediately report occurrences involving:
- death or serious injury
- accidents
- loss of a separation standard with an aircraft
- serious damage to property
Less serious incidents and occurrences involving a Type 1 RPA must be reported within 72 hours .
Type 2 operators must immediately report occurrences involving death or serious injury . Less serious incidents and damage to the RPA are reported within 72 hours .
The pattern is straightforward: the heavier and more capable the aircraft, the wider the list of things that must be reported immediately.
Timeframes and Method
For an immediately reportable matter :
Complete your emergency actions first. Secure the site, render assistance, and notify emergency services if required. "As soon as reasonably practicable" means at the first opportunity after those things are done — not instead of them.
Telephone the ATSB as soon as reasonably practicable.
Submit a written report within 72 hours.
For a routine reportable matter , submit the written report to the ATSB within 72 hours .
Reporting must be in accordance with ATSB requirements; the ATSB website carries the current forms and contact details.
Preserving evidence
Where the ATSB may investigate, do not disturb the site or the wreckage beyond what is needed to make it safe and to help anyone injured. Photograph the scene, the aircraft position, the damage and the surrounding hazards before anything is moved. Preserve the flight logs, the telemetry files, the controller logs and the battery data — these are the equivalent of a flight data recorder for an RPA and they are frequently the only objective record of what happened.
What Else Happens Alongside an ATSB Report
An ATSB report is not the only obligation an occurrence triggers:
The operator's internal report under the DPP, and the technical log entry for the aircraft.
Insurance notification , usually within a period specified in the policy.
CASA , where the occurrence involves a possible breach of the regulations or where an approval condition requires it. CASA and the ATSB have different roles and a report to one is not a report to the other.
The landowner or client , where property was damaged.
State or territory authorities , where the occurrence involved injury at a workplace, chemical release, or damage to protected areas.
Why Reporting Is in the Pilot's Interest
Remote pilots sometimes hesitate to report, fearing enforcement. Three points are worth understanding:
The ATSB does not apportion blame. Its statutory purpose is to improve safety by understanding why occurrences happen. Its investigation reports are not enforcement instruments.
Reporting is a legal obligation , not a discretionary courtesy. Failing to report a reportable matter is itself a breach.
The data is the whole point. Australia's understanding of where RPA risk actually sits — how often links are lost, how often flyaways occur, what fails and when — is assembled from these reports. An unreported near-miss with a crewed aircraft is an early warning that nobody receives.
A worked scenario
A 12 kg small RPA operating under a ReOC suffers a motor failure at 90 m and descends into a paddock, damaging the airframe. No one is hurt and no other aircraft is involved.
The aircraft is Type 2 — it is not type-certified, not large, not medium, and it is neither an excluded nor a micro operation.
There is no death or serious injury , so it is not immediately reportable.
There is damage to the RPA, which is a routine reportable matter: report to the ATSB within 72 hours .
In parallel: photograph the site, preserve the flight and controller logs, enter the defect in the technical log, notify the maintenance controller, ground the aircraft, notify the insurer, and inform the landowner.
Change one fact — a bystander is struck and seriously injured — and the same occurrence becomes immediately reportable : phone the ATSB as soon as reasonably practicable after emergency actions, then submit the written report within 72 hours.