Direct Answer
A NASA ASRS report protects you in two distinct ways. Under 14 CFR 91.25, the FAA will not use a report you submitted to NASA's Aviation Safety Reporting System — or information derived from it — in any enforcement action, except for accidents or criminal offenses, which are wholly excluded. Separately, FAA guidance AC 00-46 provides a limited waiver of sanction: if you committed an inadvertent violation, the FAA will generally not impose a civil penalty or certificate suspension when four conditions are all met.
The four conditions: the violation was inadvertent and not deliberate; it did not involve an accident or criminal offense (or a qualification/competency action under 49 U.S.C. 44709); you have no prior FAA enforcement finding in the preceding 5 years; and you filed within 10 days of the event (or of becoming aware of it). All four must be satisfied.
The nuance almost everyone misses: the waiver waives the sanction, not the finding. AC 00-46 says a finding of violation may still be made — the report stops the civil penalty or certificate suspension, but it is not an eraser. It is not blanket immunity, and it is not a substitute for an aviation attorney.
The “NASA Form,” Demystified
Ask a hangar full of pilots about the “NASA form” and you will hear a comfortable myth: file it after any screw-up and you are off the hook. That belief is half right and dangerously incomplete. The NASA form is the Aviation Safety Reporting System (ASRS) report, and it does carry meaningful protection — but the protection is two separate mechanisms with different triggers, the waiver has strict conditions, and even at its strongest it does not make a violation vanish from your record.
This page is the dedicated deep dive on the enforcement-protection mechanics — specifically the waiver of sanction. If what you actually want is the three-way comparison of the voluntary programs — how ASRS stacks up against ASAP and VDRP and which to file — that lives in a separate guide: ASAP vs VDRP vs ASRS: which one to file. Here, we go one level deeper on the single question pilots search most: does a NASA report actually protect me, and exactly how?
One framing point before the details. The ASRS enforcement protection is the only piece of this anchored in a regulation — 14 CFR 91.25. The waiver of sanction itself is described in FAA guidance (Advisory Circular AC 00-46), not in the CFR. That distinction matters: the waiver is an FAA enforcement policy, applied at the agency's discretion under the stated conditions, not a regulatory entitlement. For how the FAA chooses between handling a problem cooperatively and escalating it, see FAA compliance action vs. enforcement.
“Protected” is not the same as “immune”
The ASRS report reduces your exposure under specific conditions — it does not erase the underlying event. The waiver waives the sanction, but a finding of violation can still appear on the airman's record. Accidents and criminal offenses are excluded entirely. Deliberate conduct is not protected. Treat the precise scope as a legal question for an aviation attorney.
Two Different Protections — Don't Confuse Them
The single biggest source of confusion about the NASA form is that people collapse two separate protections into one vague idea of “immunity.” They are not the same, they come from different sources, and they have different triggers. Understanding which is which is the whole game.
1. The non-use rule
14 CFR 91.25 (regulation)
The regulation states that the FAA “will not use reports submitted to” NASA under the program, “or information derived therefrom,” in any enforcement action — except information concerning accidents or criminal offenses, which are wholly excluded.
Trigger: simply having filed the report. This protection does not depend on the 10-day clock or the four conditions. It is about keeping the report itself out of the FAA's enforcement case.
2. The waiver of sanction
AC 00-46 (FAA guidance)
Even if you did commit an inadvertent violation, the FAA will generally not impose a civil penalty or certificate suspension — provided all four conditions are met. A finding of violation may still be made; the sanction is what is waived.
Trigger: all four conditions, including filing within 10 days. This is the part that requires the clock, the clean record, and the inadvertent-and-not-an-accident nature of the event.
Why the distinction is practical, not academic: Suppose the FAA learns about an event from a ramp check, not from your report. The non-use rule still keeps your NASA report out of the enforcement case. But whether your penalty goes away depends entirely on whether you can show the four waiver conditions — most critically, that you filed within 10 days. That is why the disciplined answer to “should I file?” is almost always yes, promptly, and keep the dated proof.
The exact text of the rule is short and worth reading once: 14 CFR 91.25 on the Cornell Legal Information Institute. The waiver-of-sanction conditions are found in FAA Advisory Circular AC 00-46 (currently AC 00-46F), which is FAA guidance describing the agency's enforcement policy for ASRS filers — not a section of the CFR.
The Four Conditions for the Waiver of Sanction
This is the heart of it. For the FAA to waive the civil penalty or certificate suspension under AC 00-46, all four of the following must be true. Miss any one and the waiver of sanction does not apply — though, as above, the underlying 14 CFR 91.25 non-use protection may still keep your report out of the case.
Inadvertent — not deliberate
The violation must have been inadvertent and not deliberate. The waiver is built for honest mistakes — a momentary altitude bust, an inadvertent airspace entry — not knowing or intentional noncompliance.
No criminal offense or accident
The event must not involve a criminal offense or an accident, and must not be an action under 49 U.S.C. 44709 that discloses a lack of qualification or competency. These categories are wholly excluded from the program.
No prior violation in 5 years
You must not have been found, in any prior FAA enforcement action, to have committed a violation in the 5 years before the date of the occurrence. A clean recent record is part of the bargain.
Filed within 10 days
A written report must be filed with NASA within 10 days of the violation — or within 10 days of when you became aware, or should have become aware, of it. Keep the dated NASA identification strip as proof.
The 10-day clock is the condition you control completely
You usually cannot change whether an event was inadvertent, whether it involved an accident, or your prior-violation history. The one condition entirely within your control is timeliness — so the safe habit is to file promptly any time you think you may have had an inadvertent deviation, and to keep the dated NASA identification strip. The clock runs from the violation, or from when you became aware (or should have become aware) of it.
A subtle point on the 5-year condition: it looks back at prior FAA enforcement findings, not at prior reports you filed. Filing ASRS reports does not count against you — quite the opposite, the program is designed to encourage reporting. Knowing your own enforcement history with confidence, however, requires having those records organized and retrievable, which is exactly the kind of question that gets answered from a clean document trail rather than memory under pressure.
What the NASA Report Does NOT Do
The reason “get-out-of-jail-free” is a dangerous shorthand is that it papers over four hard limits. Each one is where pilots get surprised. Read these as carefully as the conditions.
It waives the sanction, not the finding
Even when all four conditions are met, AC 00-46 provides that a finding of violation may still be made — but no civil penalty and no certificate suspension will be imposed. The FAA can still conclude a regulation was violated; the ASRS report stops the punishment, not the finding.
Accidents and criminal offenses are out
Information concerning accidents or criminal offenses is wholly excluded from the program — 14 CFR 91.25 says so explicitly. If an event is a reportable accident, a separate NTSB Part 830 notification can be required on its own immediate timeline, and a NASA report does nothing to change that.
Deliberate conduct is not protected
The waiver is for inadvertent violations. Knowing, intentional, or reckless noncompliance falls outside it. And falsifying a record to make an event look cleaner is itself a serious violation that no voluntary program protects.
It is not a substitute for legal advice
Whether the conditions are met, whether to file, and what a finding of violation means for a specific airman are fact-intensive questions with real consequences. The waiver has strict conditions — work through them with an aviation attorney.
Never fabricate, backdate, or alter a record to make a report look cleaner
Falsifying a maintenance record is itself a serious violation — and it converts a recoverable inadvertent mistake into intentional misconduct that no voluntary program protects. The honest, dated, complete record is the one that helps you. The legitimate way to fix a flawed entry is its own discipline: how to correct a maintenance logbook entry.
The exclusions also interact with mandatory obligations. A NASA report is a voluntary filing; it does not replace any report you are independently required to make. If an event is a reportable accident or serious incident, an NTSB notification under 49 CFR Part 830 can be required on its own immediate timeline — and accidents are excluded from ASRS protection anyway. And if the FAA already has the event from surveillance or a ramp check, the calculus shifts, which is why understanding the FAA's grey-charter and illegal-charter scrutiny and how to prepare for a Part 135 surveillance audit matters alongside any voluntary filing.
For operators, there is a parallel question of where individual reporting ends and the company's own safety obligations begin. The accountable executive and the safety program sit at the operator level — see the Part 135 accountable executive, the director of safety and SMS requirement, and the required management personnel qualifications. The single SMS compliance date for Part 135 is May 28, 2027, and an individual's ASRS protection is separate from the operator's SMS obligations.
The waiver turns on dates and records you can actually prove.
The 10-day filing, the clean 5-year record, the qualification picture behind an “inadvertent” event — every one of them is answered from documents. FileFlo classifies and indexes those records, ties them to aircraft and dates, alerts on expirations, and assembles an audit-ready binder on demand. 600+ document types. Starter at $89/mo, Professional at $299/mo. 5-day free trial, no credit card required.
How to File the NASA Form (and Keep Your Proof)
Filing is free, fast, and deliberately neutral — it goes to NASA, an independent agency, not to the FAA. Pilots file the ASRS General Report Form (historically designated NASA ARC Form 277B), and there are separate forms for air traffic controllers, mechanics, cabin crew, and drone operators. You can file electronically through the ASRS website or on paper.
File promptly — treat 10 days as the deadline
The waiver of sanction requires filing within 10 days of the violation (or of becoming aware of it). Because you rarely know in the moment whether an event will ever be questioned, the safe practice is to file any time you suspect an inadvertent deviation.
Be candid and factual
The report is for safety analysis and is de-identified by NASA. Describe what happened plainly. The non-use rule keeps the report out of FAA enforcement (except accidents/criminal), so candor carries little downside for an inadvertent event — but it is not the place for anything criminal.
Keep the dated identification strip
NASA removes the identification strip at the top of your report, date-stamps it, and returns it to you by mail as proof of submission. That dated strip is your evidence that you filed within the window. Do not lose it — file it.
Do not treat it as your only obligation
A NASA report does not satisfy any mandatory report (for example, an NTSB Part 830 accident notification). And if a matter looks like it could become enforcement, involve an aviation attorney before you rely on the waiver.
Whether the “inadvertent” condition holds often depends on what your own records showed on the date in question. See where your pilot, maintenance, and training records stand in about two minutes.
For how ASRS fits alongside the employer-level and operator-level programs — and when you might file more than one for the same event — read the companion comparison: ASAP vs VDRP vs ASRS: which one to file. And because operating structure can change what regulations even apply to a flight, two foundational reads are worth bookmarking: Part 91 vs Part 135 compensation or hire and the flight department company trap.
Why This Comes Down to Records You Can Produce
Step back and notice what the waiver actually rests on. Three of the four conditions are evidentiary: was it inadvertent (read off your qualification and procedure records), was there a prior violation in 5 years (read off your enforcement history), and did you file within 10 days (proven by the dated NASA identification strip). The pilots who benefit from this program are not the ones who never make a mistake — they are the ones who can find the relevant records, prove what happened and when, and produce a clean picture on demand.
That is a document-management capability, and it is exactly the gap FileFlo is built to close. Below is the record set that an ASRS waiver analysis typically draws on, what each one proves, and where a compliance document intelligence platform helps.
The ASRS-protection record set
The dated NASA identification strip
14 CFR 91.25 / AC 00-46Why it carries the analysis
The whole waiver turns on the 10-day window. The single most important piece of evidence is the date-stamped identification strip NASA returns to you as proof of submission. If you cannot prove when you filed, you cannot prove you met the condition.
How FileFlo helps
FileFlo stores the NASA identification strip as a dated, classified document tied to the event, so the proof of timely filing is filed the day it arrives — not hunted for months later when it matters.
Pilot qualification, currency, and medical records
14 CFR Part 61 / Part 135 Subpart EWhy it carries the analysis
When the event touches an airman — a deviation, a currency question, a medical issue — whether it was "inadvertent" and whether any qualification question arises (which would exclude it) often turns on what the records actually showed, on what date.
How FileFlo helps
FileFlo tracks pilot and medical records with expiration alerting, so a lapsing checkride or medical surfaces before it becomes an event, and the historical record is on file when a report or inquiry needs it.
The prior-enforcement / clean-record picture
AC 00-46 (5-year condition)Why it carries the analysis
The waiver requires no prior FAA enforcement finding in the preceding 5 years. Knowing your own enforcement history — and being able to document it — is part of assessing whether the waiver is even available before you rely on it.
How FileFlo helps
FileFlo keeps prior correspondence, letters of correction, and enforcement-related documents indexed and dated, so the 5-year question can be answered from records instead of memory.
Maintenance and airworthiness records
14 CFR 43.9, 43.11Why it carries the analysis
Many events that lead someone to consider a NASA report begin in the maintenance world — a missed inspection, an out-of-sequence entry. Whether the event was inadvertent, and whether it became an accident or qualification issue, is read off the records.
How FileFlo helps
FileFlo classifies maintenance entries and airworthiness documents, dates them, and tracks recurring inspection deadlines, so the maintenance picture behind an event is continuous and producible rather than reassembled.
Operations specifications and manuals
14 CFR Part 119 / Part 135Why it carries the analysis
Whether an event was a deviation at all often turns on what the OpSpecs and manuals required, and which revision was in force on the date in question. That authorization and revision history is part of the picture an inadvertent-violation analysis rests on.
How FileFlo helps
FileFlo indexes OpSpecs and manual revisions as distinct document classes and version-controls amendments, so the procedure in force on a given date is retrievable.
None of these documents is exotic — they are the same records a Part 135 operator already keeps. For the foundational records picture, see RVSM altimeter and transponder inspection records (a classic time-sensitive set where a lapse can become an inadvertent deviation) and, when international flying is involved, the aircraft international operations documents and records. How an enforcement matter is graded once it starts — a letter of correction versus a warning versus an investigation — is its own subject, covered in FAA letter of correction vs. warning vs. investigation, and what an oversight system looks at is explained in what is the FAA Safety Assurance System (SAS) and what triggers an FAA audit.
FileFlo is the proof layer — not your report, your decision, or your attorney
FileFlo is a compliance document intelligence platform. It classifies the records an ASRS waiver analysis draws on, indexes them by aircraft and date, tracks expirations on the time-sensitive ones, and stores the dated NASA identification strip so your proof of timely filing is retrievable. It does not file your NASA report, decide whether the waiver conditions are met, represent you to the FAA or NASA, give legal or tax advice, or guarantee any outcome. What it does is make sure that when you and your counsel assess a situation, you can produce and prove your records — on the clock.
Frequently Asked Questions
Does a NASA report protect you from FAA enforcement?
Partly, and in two distinct ways that people constantly blur together. First, 14 CFR 91.25 prohibits the FAA from using a report you submitted to NASA's Aviation Safety Reporting System (ASRS) — or information derived from it — in any enforcement action, except for information about accidents or criminal offenses, which are wholly excluded from the program. Second, separate FAA guidance (Advisory Circular AC 00-46) provides a limited waiver of sanction: if you did commit an inadvertent violation, the FAA will generally not impose a civil penalty or certificate suspension when four specific conditions are all met. So a NASA report is real protection — but it is not blanket immunity. It will not help with deliberate conduct, accidents, or criminal matters, and even when the waiver applies, a finding of violation can still be made.
What is the NASA form and how do I file it?
The NASA form is the Aviation Safety Reporting System (ASRS) report. NASA — not the FAA — administers the program, deliberately, so the safety data goes to a neutral third party. Pilots file the ASRS General Report Form (historically designated NASA ARC Form 277B), with separate forms for air traffic controllers, mechanics, cabin crew, and drone operators. You can file electronically or on paper. NASA de-identifies the report and removes the identification strip at the top, which it date-stamps and mails back to you as your proof of submission. Keep that dated strip — it is how you prove you filed within the window if the question ever comes up. Filing is free and takes only a few minutes.
How long do you have to file a NASA report to get protection?
For the limited waiver of sanction in FAA Advisory Circular AC 00-46, the ASRS report must be filed within 10 days after the violation — or within 10 days of when you became aware, or should have become aware, of it. That 10-day window is one of four conditions that must all be satisfied. Importantly, the separate 14 CFR 91.25 protection — that the FAA will not use the report in an enforcement action — does not depend on the 10-day clock at all. But because you usually do not know in the moment whether an event will ever be questioned, the safe discipline is to treat the 10-day window as the deadline and file promptly. Keep the dated NASA identification strip as evidence of timely filing.
What are the conditions for the ASRS waiver of sanction?
FAA Advisory Circular AC 00-46 lists four conditions, and all of them must be met. One, the violation was inadvertent and not deliberate. Two, the violation did not involve a criminal offense or an accident, and was not an action under 49 U.S.C. 44709 that discloses a lack of qualification or competency. Three, you have not been found, in any prior FAA enforcement action, to have committed a violation in the 5 years before the date of the event. Four, you filed a written report with NASA within 10 days of the violation (or of becoming aware of it). Miss any one of the four and the waiver of sanction does not apply — though the underlying 14 CFR 91.25 protection may still keep the report itself out of the enforcement case.
Does a NASA ASRS report waive the violation or just the penalty?
Just the penalty — and this is the single most misunderstood point about the program. The waiver in AC 00-46 provides that, when the conditions are met, a finding of violation may still be made, but neither a civil penalty nor a certificate suspension will be imposed. In plain terms: the FAA can still conclude that you violated a regulation, and that finding can appear on your record; what the waiver does is stop the sanction for that inadvertent, promptly-reported violation. The ASRS report is not an eraser. It is a way to avoid the punishment for an honest mistake — not a way to make the mistake disappear. That nuance is exactly why this is a question to work through with an aviation attorney, not a reflex assumption.
Does filing a NASA report increase the chance the FAA finds out?
No — and this is the worry that stops people from filing when they should. The ASRS report goes to NASA, an independent agency, which de-identifies it; under 14 CFR 91.25 the FAA cannot use that report, or information derived from it, in an enforcement action (except for accidents and criminal offenses). NASA does not forward your report to the FAA as a tip. The report is your protection, not your accuser. The realistic risk is the opposite: the FAA learns about an event from some other source — a ramp check, surveillance, an air traffic control report — and you have no timely NASA filing to support a waiver of sanction. That said, a NASA report is not a substitute for any mandatory report you are independently required to make, and accidents are excluded entirely.
What is the difference between ASRS and ASAP for enforcement protection?
They are different programs with different protections. ASRS (NASA) gives every individual airman the 14 CFR 91.25 protection plus the limited AC 00-46 waiver of sanction, and it is available to anyone, anywhere, with no employer program required. ASAP — the Aviation Safety Action Program (FAA guidance AC 120-66) — is an employer-level program that only exists where a specific operator, the FAA, and often a labor group have signed a memorandum of understanding; reports are reviewed by an Event Review Committee and the enforcement outcome turns on whether the report is sole-source. Many pilots are eligible to use both, and one event can sometimes be filed under both. For the full three-way comparison with VDRP, see our dedicated guide; this page is the deep dive on the ASRS waiver-of-sanction mechanics specifically.
Is the NASA ASRS report really a get-out-of-jail-free card?
No, and treating it that way is dangerous. The phrase gets repeated because, for a genuinely inadvertent, promptly-reported, first-in-five-years violation that is not an accident or crime, the waiver of sanction can feel like one. But the limits are real: it only waives the sanction (a finding of violation can still be made), it excludes deliberate conduct, accidents, and criminal offenses, it requires the 10-day filing and a clean 5-year prior-violation record, and it does not protect against everything an enforcement action can involve. It is a powerful incentive to report honest mistakes — not a license to cut corners. Because the conditions are strict and the consequences of getting it wrong are serious, this is a matter for an aviation attorney, not internet folklore.
More on FAA Enforcement & Problem-Recovery
The NASA waiver protects honest mistakes — but only when you can prove your records and your filing date.
FileFlo classifies and indexes the documents an ASRS waiver analysis rests on — pilot and training records, maintenance entries, OpSpecs and manuals, prior correspondence, and the dated NASA identification strip — with AI classification across 600+ document types, expiration tracking, and an audit-ready binder on demand. Starter at $89/mo, Professional at $299/mo. No credit card required for the 5-day free trial.
5-day free trial · No credit card required · Cancel anytime
Reviewed by Chad Griffith, Founder, FileFlo — compliance document intelligence — June 15, 2026. The ASRS enforcement protection is the regulation 14 CFR 91.25 (the FAA will not use a report submitted to NASA under the Aviation Safety Reporting Program, or information derived from it, in any enforcement action, except information concerning accidents or criminal offenses) — verified against the Code of Federal Regulations (Cornell LII) as of publication date. The limited waiver of sanction and its four conditions (inadvertent and not deliberate; no criminal offense, accident, or 49 U.S.C. 44709 qualification action; no prior FAA enforcement finding within 5 years; written report filed with NASA within 10 days) are described in FAA Advisory Circular AC 00-46 (currently AC 00-46F) — FAA guidance, not a section of the CFR, applied at the agency's discretion. AC 00-46 provides that a finding of violation may still be made even where the sanction is waived. This article is general compliance-document information, not legal or tax advice; whether the conditions are met and whether to file are fact-specific — consult an aviation attorney, and a tax advisor for any tax question.