A drone returns with a scuffed propeller. A helicopter passed closer than expected. A lost link ended without injury, but only because the aircraft landed in an empty patch of ground. The immediate temptation is relief—then silence.

That silence protects nobody from the next occurrence. In the United States, drone pilots and crew members have access to a system designed to collect precisely these uncomfortable stories without turning them into public confessions: NASA’s Aviation Safety Reporting System, or ASRS.

The NASA ASRS drone-reporting page welcomes reports about close calls, collisions, lost links, flyaways, uncontrolled descents, airspace incursions, equipment problems, environmental hazards, miscommunication, procedural issues and human error. Recreational flyers, Part 107 crews, public operators and Part 135 operators are all shown as potential participants.

But two ideas are often blurred together: confidentiality and protection from an FAA sanction. They are related, not identical. A report is not a magic eraser for a violation, and some events do not belong in ASRS at all.

Why NASA receives the report instead of the FAA

The FAA created the Aviation Safety Reporting Program to encourage people using the National Airspace System to reveal safety deficiencies that might otherwise stay hidden. NASA acts as the third party that receives, processes and de-identifies the raw reports.

The current FAA Advisory Circular 00-46F, listed as active and issued on 2 April 2021, expressly includes unmanned-aircraft operations. It explains that the value of the programme depends on a free flow of information and that the resulting data can help identify defects, support corrective action and inform future system design.

NASA says its analysts remove identifying details and generalise personal references, dates, times and locations before safety information is shared. The identification strip containing the reporter’s contact details is returned as a receipt. Except for excluded accident and criminal reports, NASA says it does not keep a copy of that identifying strip.

This architecture is the point: people are more likely to describe a mistake honestly when a safety analyst, rather than the enforcement agency, receives the identifiable account.

Confidential does not mean consequence-free

The FAA policy draws two separate lines.

First, the FAA says it will not use an ASRS report—or information derived from it—in an enforcement action, apart from information about accidents or criminal offences. That restriction concerns the report itself. It does not prevent the FAA from acting when it learns about the same event from another source.

Second, filing may support a waiver of a civil penalty or certificate suspension, but only when every condition is met. According to the official ASRS explanation of AC 00-46F:

• the violation must have been inadvertent, not deliberate;
• it must not involve a criminal offence, an accident or an action revealing a lack of qualification or competency under the cited statute;
• the person must not have been found to have committed an FAA violation during the preceding five years; and
• the report must be completed and delivered or mailed within ten days of the event, or within ten days of when the person became aware—or should have become aware—of it.

Even then, the policy says a finding of violation may still be made. The potential waiver concerns the imposition of a civil penalty or certificate suspension. Calling this blanket “immunity” would therefore overstate the protection.

Some events must go somewhere else

NASA is explicit that accidents and criminal activity should not be reported through ASRS. Its processing rules say accident information is referred to the National Transportation Safety Board and FAA, while information about criminal offences is referred to the Department of Justice and FAA. Those reports are not de-identified before referral.

ASRS also is not an emergency channel. NASA tells people seeking immediate action on unsafe or unauthorised drone operations to contact local authorities. Nor does filing an ASRS report replace any accident notification, operational report or other form required by a regulation, authorisation, employer or agency.

These distinctions matter after a stressful event. “Tell NASA” may be one appropriate step; it is not a universal answer to every incident.

What makes a useful drone safety report

A report becomes valuable when it reveals how a system failed, not merely that something frightening happened. NASA’s UAS guidance asks reporters to cover who was involved, what happened, where and when it occurred, why they think it happened, and how recurrence might be prevented.

For a drone occurrence, a useful narrative might include:

• the reporter’s role, such as remote pilot in command, person manipulating the controls or visual observer;
• the operating rule, relevant authorisation and type of airspace;
• aircraft make and model, without inserting a registration or serial number in a public-facing narrative;
• weather, light, visibility and surrounding obstacles;
• the flight phase and sequence of alerts or control inputs;
• software or firmware state, command-and-control link conditions and navigation status;
• what the crew expected the automation to do, and what it actually did;
• the recovery action, outcome and proposed corrective measure.

The aim is not literary drama. It is enough operational context for an analyst to see whether the event reflects a recurring equipment, software, training, communication or procedural hazard.

A near miss is data, not proof

ASRS reports are personal accounts. NASA’s publication guidance says it does not verify or validate every report. A single narrative can expose a plausible hazard, but it cannot by itself establish a failure rate, prove that a model is defective or show that one factor caused the event.

That limitation is a strength when it is stated clearly. The database is a signal-detection and learning resource, not a controlled experiment or a court finding. Patterns across many de-identified reports may point investigators, manufacturers, operators and regulators toward questions that deserve deeper analysis.

For journalists and researchers, the same rule applies: quote a report as an account, not as independently established fact. For operators, use a report to improve a checklist or briefing, not to diagnose another crew from a distance.

A practical response after a non-accident occurrence

1. Make the scene safe. Recover people and equipment without creating a second hazard. Use emergency or local-authority channels if immediate action is needed.
2. Preserve records. Keep flight logs, controller messages, authorisations, weather information, maintenance history and crew notes. Do not edit the story to make it look cleaner.
3. Determine which reports are required. Check the applicable FAA, NTSB, operational-authorisation and organisational rules. ASRS does not replace them.
4. Use the official ASRS form if the event fits. File electronically through NASA’s secure system or use the official paper form. Do not email a report.
5. Respect the ten-day condition. If FAA sanction-waiver eligibility may matter, the official policy ties it to timely filing and other conditions. Do not wait for an internal investigation to consume the window.
6. Keep the returned receipt. NASA identifies it as proof that a report was filed.
7. Turn the event into a control. Update training, crew calls, route design, maintenance, software-change procedures or abort criteria according to what the evidence supports.

The safety system needs the story people would rather forget

Aviation improves when uneventful recoveries are studied before they become accidents. Drones make that principle more urgent, not less. A small aircraft may leave little physical evidence, and a software alert can disappear as soon as the app closes. Without a report, the lesson may live only in one pilot’s memory.

ASRS offers a structured way to preserve that lesson while protecting identity within defined boundaries. The honest summary is neither “reporting will get you punished” nor “filing makes the violation disappear.” It is this: a timely, accurate report can contribute to safety and may qualify for specific FAA protections, but the exclusions and conditions are part of the system—not fine print to ignore.

Scope note: This article describes the United States NASA ASRS and FAA policy as checked on 17 October 2026. It is general editorial information, not legal advice. No incident, operator or product was tested or investigated for this report.