ASRS Reports After a Pilot Deviation: What Flight Schools Should Decide Before the Phone Number

A student and a CFI step out of the airplane on a Tuesday afternoon, both quiet. They had clipped the corner of a Class D on the way back from the practice area, twelve seconds of incursion before the frequency change happened, and the tower had asked the student to call a phone number after landing. The dispatcher sees them walk in, sees the number on the kneeboard, and asks the question nobody at the school has a written answer to: are we filing the NASA report.

The decision to file an Aviation Safety Reporting System report should not happen in the briefing room twenty minutes after the event. The chief instructor's policy on it should already exist, on paper, where every CFI can find it without asking. What it covers, when it triggers, who fills the form, and what the filing actually protects are the four questions the school answers on a Wednesday morning, not on the walk back from the ramp.

What ASRS Is Actually For

The Aviation Safety Reporting System is operated by NASA on behalf of the FAA. Its purpose is data collection. Pilots, controllers, mechanics, and dispatchers file confidential reports of anything safety-relevant that happened in the system, and NASA aggregates the de-identified data so the FAA, the airlines, the manufacturers, and the schools can see where the system is breaking. The reports themselves are kept confidential, identifying information is stripped, and a dated strip-off receipt is returned to the reporter as proof the report was filed.

A flight school's instructors and renters can file an ASRS report at any time. The reports are short, free, and submitted online through the NASA ASRS web portal. The school cannot see them. The FAA cannot see the original. An insurer cannot subpoena them. That confidentiality is the structural reason the data submitted is honest.

Where the Enforcement Immunity Comes In

The piece that matters operationally to a flight school is the limited enforcement immunity that comes with filing. The regulatory backstop is 14 CFR 91.25, which prohibits the FAA from using ASRS reports for enforcement purposes. The policy framework on top of that is FAA Advisory Circular 00-46, currently revision F, which sets out the four conditions under which the FAA will waive a civil penalty or certificate suspension for an inadvertent violation, even when it learns about the violation through other channels.

The violation has to have been inadvertent and not deliberate. It has to have not involved a criminal offense, an accident, or conduct that disclosed a lack of qualification or competency. The reporter has to not have been found, in any prior FAA enforcement action, to have committed a violation in the five years preceding the event. And the reporter has to deliver a written report to NASA within ten days of the incident.

The protection is real and the conditions are narrow. A CFI who knowingly buzzes a friend's house has filed nothing the FAA is required to honor. A student whose attention slipped and let the airplane drift into Class D without a clearance, who reports inside ten days and meets the other conditions, has bought the school and the student a structurally cleaner enforcement conversation. The deviation is still on the record at the FSDO, and the controller's report and the radar tape still exist, but the certificate is no longer at risk in the same way.

The Phone Number Is the Trigger, Not the Verdict

When a controller gives a pilot a phone number after a possible pilot deviation, the pilot is not in violation yet. The phone call is the FSDO inspector trying to understand what happened. The pilot can call back, explain, and in many cases the matter closes there with no enforcement action and no certificate consequence. That call is not the place to admit anything the pilot does not know to be true, but it is also not the place to refuse to engage.

The ASRS filing is independent of the phone call. The school's policy should be that the ten-day clock starts the moment the deviation happens, not the moment the phone call is returned. The CFI on the flight files their own report alongside the pilot if they were giving instruction at the time, and the same time-stamped strip-off receipt protects each filer separately. The school cannot file on a pilot's behalf, but it can make the link, the form structure, and the deadline visible the same day.

Who Files What

The pilot in command files an ASRS report for themselves. The CFI giving instruction, if they were acting as PIC for any portion of the flight or if their own conduct contributed to the deviation, files their own. The chief instructor does not file for either of them. The dispatcher does not file. A school whose policy turns this into a centralized form drains the immunity, because the protection lives with the reporter who lived the event.

The school's contribution is procedural. A printed reference at the dispatch desk that says, after any controller phone number, runway incursion, deviation from clearance, near-collision, or unintentional Class B, C, or D bust, the involved pilots will file ASRS within seventy-two hours. The form is at asrs.arc.nasa.gov. A copy of the dated receipt goes to the chief instructor for the school's own learning record. The contents of the report do not. The school never asks to read the report, because the confidentiality of the contents is what gives the system its data.

Where ASRS Fits the Safety Culture

The school whose only ASRS reports get filed under threat is the school whose data is going to be wrong. The wider point of the system, beyond the immunity, is that the school learns from events that did not produce a phone number. A student vectored into wake turbulence on final, a CFI noticing a frequency-congestion pattern at a busy non-towered field, an instructor catching a fuel-quantity discrepancy that turned out to be a gauge problem: those events feed the NASA database whether or not the school encourages the filing, and they pull a learning conversation back into the staff room.

The same calibration that runs through a CFI standardization meeting belongs in the safety-reporting conversation. If two instructors observe the same incursion pattern at the same intersection at the same field, the school's non-towered airport brief needs to change, and a chief instructor who learned about the pattern through ASRS receipts before it ever produced a phone call is a chief instructor who can change the SOP cheaply.

The Tie to the School's Own Records

An ASRS report is confidential to NASA. The school's internal record of what happened is not. The squawk write-up, the safety event log, the stage check a student takes after a near-miss to demonstrate the lesson was absorbed, all live in the school's own files. The discipline that makes squawk tracking reliable applies to safety events the same way: open a record, attach the date, the airplane, the pilots involved, the outcome, and what changed in the syllabus, the stage check structure, or the briefing as a result. The NASA report stays at NASA and the receipt comes back to the pilot. The school's internal record is what the chief instructor reads when deciding whether the standardization meeting needs a new agenda item next month. Confusing the two is the mistake that either breaks the immunity or buries the learning.

What the Policy Should Say Before the Phone Rings

A working ASRS policy at a flight school fits on one page. It defines the trigger events that require a filing. It states who files. It states the deadline against the deviation date, not the phone-call date. It names the receipt-storage location. It commits the school to never asking to see the contents of the report itself. And it makes the form link and the chief instructor's contact available to every CFI without a door to knock on.

The schools whose enforcement events get smaller over time are not the ones whose pilots make fewer mistakes. They are the ones whose pilots, controllers, and instructors are talking about the mistakes inside a system designed to learn from them, and whose chief instructor wrote the ASRS policy on a Wednesday morning instead of after the phone number was already on the kneeboard.