Learn how to report an aircraft accident or incident, including what we investigate, how we handle public reports and how to raise a drone product safety issue
Who should report—and why speed matters
When something goes wrong, the value of a report fades fast. Memories blur, recordings get overwritten, and physical evidence can be altered or lost. A prompt, accurate account protects people, preserves crucial evidence and gives investigators the details they need to stop the same thing from happening again.
Regulators, operators and maintenance teams rely on timely submissions to decide whether an immediate fix, a formal inquiry, or broader safety action is needed.
Who must submit a report
Some reports aren’t optional. Certified operators, licensed maintenance personnel and designated safety officers are required by law to notify authorities when events meet statutory thresholds.
Pilots, controllers and other aviation professionals should default to reporting if they have any doubt. Members of the public and other witnesses can also file voluntary reports—those reports often provide the missing piece that points investigators to a wider problem.
Types of reports and when to use them
Reports are not one‑size‑fits‑all. Mandatory Occurrence Reports (MORs) are triggered by specific legal thresholds—serious injury, accident or major equipment failure—and usually prompt regulatory follow‑up. Voluntary safety reports capture near misses and procedural lapses and feed trend analysis that prevents future incidents. Immediate notifications are for ongoing hazards or significant deviations needing swift attention, while standard occurrence reports provide a fuller account for later review.
How reports are processed
When a report arrives it’s triaged. High‑severity events trigger urgent steps to preserve perishable evidence and a fast investigation. Lower‑severity and voluntary submissions are incorporated into safety databases and used for long‑term risk reduction. Correct classification matters: routing the information to the right specialists speeds the response and ensures meaningful follow‑through.
What to include for parts, components and actionable evidence
When suspect parts or unserviceable critical components are involved, detail is everything. Record serial numbers, supplier and batch information, and chain‑of‑custody notes. Photographs, test results and maintenance records help confirm provenance and reveal patterns across multiple units. The more concrete the initial submission, the quicker investigators can act and the less time is wasted chasing clarifications.
Reporting drone product safety issues
For hardware faults, errant firmware behavior or misleading performance claims, use the dedicated drone product safety channel. Provide model and revision, firmware version, a brief incident description, location and timestamps. Attach telemetry, logs, photos or video whenever available—these items cut triage time and greatly increase the chance of an effective fix or advisory.
Guidance for air traffic controllers
Follow your unit protocols: notify a supervisor, log the event and file required reports through the authorised system without delay. Stick to objective facts—call signs, positions, times (UTC if your unit uses it), weather and a concise sequence of events. Preserve electronic recordings and contemporaneous notes; those immediate entries often form the backbone of any later inquiry.
Writing the report: clarity over conjecture
Separate facts from interpretation. Use precise, plain language and avoid guessing about motives or causes. If new information appears, submit an update rather than trying to erase earlier entries. When in doubt about which form to use, alert your supervisor and file a detailed occurrence report—the cost of hesitation can be lost evidence or missed opportunities to mitigate harm.
Choosing the correct report type
Select the report that matches the incident and the regulator’s rules. MORs are for events that meet statutory thresholds; voluntary reports catch near misses and procedural lapses; parts‑related reports may lead to supply‑chain or airworthiness reviews. Picking the right category ensures the issue reaches the appropriate reviewers and that any required follow‑up happens without delay.
When you should report
If you witness, are involved in, or learn about anything that affects aviation safety—no matter how small it seems—report it. Early notification preserves voice recordings, radar tracks and surveillance video that might otherwise be overwritten. Speed keeps investigative options open and preserves the integrity of the account.
Who must submit a report
Some reports aren’t optional. Certified operators, licensed maintenance personnel and designated safety officers are required by law to notify authorities when events meet statutory thresholds. Pilots, controllers and other aviation professionals should default to reporting if they have any doubt. Members of the public and other witnesses can also file voluntary reports—those reports often provide the missing piece that points investigators to a wider problem.0
