This bill directs the FAA to narrow the scope of the “sensitive government mission” exception in 14 C.F.R. §91.225(f) so that it applies only during the specific portion of a flight when sensitive activities occur. It requires the FAA to complete a rulemaking within one year, revise memoranda of agreement with other agencies, and put in place new reporting and oversight: quarterly attestations and flight‑level disclosures from agencies using the exception, biannual reports to Congress (with a possible classified annex), a GAO utilization review after two years, and annual DOT Inspector General audits beginning three years after enactment.
The bill matters because it replaces a broad and often‑criticized de‑facto exemption with a structured, documented process intended to balance operational secrecy with aviation safety and transparency. It creates concrete deadlines, reporting thresholds (including a 5‑times‑per‑month flag), and enforcement triggers that could change how the Department of Defense, federal law enforcement, and state/local agencies plan and document missions that stop ADS‑B transmissions.
At a Glance
What It Does
The bill mandates that the FAA construe and rewrite the ADS‑B Out "sensitive government mission" exception narrowly and limit non‑transmission to the exact flight segments performing sensitive activities. It requires new rulemaking and MOA revisions, routine reporting by agencies that disable ADS‑B Out, a GAO usage review, and recurring IG audits of FAA oversight.
Who It Affects
Primary targets are Department of Defense aircraft and any Federal, State, local, or Tribal agency that has used the ADS‑B Out exception — plus the FAA, which must conduct rulemaking and expand oversight. Commercial operators and air traffic control benefit indirectly from clearer situational awareness rules.
Why It Matters
This bill converts an operationally broad exception into a regulated, auditable process with specific timelines and reporting obligations, increasing congressional visibility into how often ADS‑B is turned off and creating formal consequences for recurring or undocumented use.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill rewrites how the FAA must treat the ADS‑B Out exception for "sensitive government missions." Rather than allowing open-ended or flight‑long non‑transmission, it forces a narrow reading: agencies may stop broadcasting only during the portion of a flight when sensitive activity actually occurs. That means mission planning will need to identify and document precise segments where non‑transmission is asserted.
To get there the FAA must finish a rulemaking within one year to update 14 C.F.R. §91.225(f) and must also revise any memoranda of agreement with other agencies so those MOAs match the new rule. If the FAA misses the one‑year deadline the Administrator must report to the relevant congressional committees within 30 days explaining why.
After revised regs are in place, the GAO will examine, within two years, how agencies used the exception before and after the change and report those findings back to the FAA and Congress.The bill creates a steady stream of oversight and data collection. Agencies performing "sensitive government missions" must send the FAA quarterly reports attesting that their operations regularly transmit ADS‑B Out except where appropriate, and provide a flight‑level list for each non‑transmitting operation (airport or airspace, date, time, duration, mission type).
The FAA will aggregate that data into biannual reports to Congress, assess whether each non‑transmitting operation jeopardized aviation safety, and may include a classified annex if needed. A special notification rule forces the FAA to alert Congress within 14 days if any agency uses an exception five or more times in a calendar month or fails to provide the required attestation.Finally, starting three years after enactment the DOT Inspector General must perform annual audits of FAA oversight over these exceptions, focusing on whether exceptions are used strictly as allowed, whether noncompliant operators are identified and engaged, and any other oversight gaps the IG finds.
Those audit results will be briefed to Congress annually. Altogether the bill replaces discretionary, informal practice with deadlines, flight‑level reporting, external review, and predictable audit cycles.
The Five Things You Need to Know
The FAA must complete a rulemaking to revise 14 C.F.R. §91.225(f) within 1 year of enactment and revise any related memoranda of agreement.
Agencies must submit quarterly reports to the FAA that include an attestation about ADS‑B Out use and a flight‑by‑flight list (airport/airspace, date, time, duration, mission type) for each instance ADS‑B Out was off.
If an agency uses the ADS‑B Out exception 5 or more times in a calendar month, or fails to submit the required attestation, the FAA must notify the appropriate congressional committees within 14 days.
The Government Accountability Office must review exception utilization and compare before‑and‑after usage within 2 years of enactment and report findings to the FAA and Congress.
Beginning 3 years after enactment the DOT Inspector General must conduct annual audits of FAA oversight of these exceptions and brief Congress on audit results.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Designates the bill as the "Military ADS‑B Out Loophole Act." This is purely titular but signals congressional intent to focus on perceived gaps in ADS‑B Out exception usage for government missions.
Narrow construction of 'sensitive government mission'
Requires the term "sensitive government mission" in 14 C.F.R. §91.225(f)(1) to be narrowly construed and limited to the specific portion of a flight during which sensitive activities occur. Practically, operators must identify and justify the precise flight segment for non‑broadcasting rather than claiming it for entire flights; this changes operational planning and documentation expectations for agencies that previously used a blanket approach.
Rulemaking deadline and MOA updates
Compels the FAA to issue or revise regulations to update §91.225(f) within one year and to revise any memoranda of agreement between the FAA and other federal, state, local, or Tribal agencies to conform to the new rule. If the Administrator misses the deadline, they must report to the appropriate congressional committees within 30 days explaining the delay — creating an enforceable timetable and a documentary trail for compliance or noncompliance.
GAO utilization review and comparison
Directs the Comptroller General to review how exceptions were used and whether agencies complied with laws and regulations, and to compare usage before and after the FAA rule revisions. The GAO review is intended both to measure the impact of the rule change and to identify systemic misuse or patterns of frequent non‑broadcasting that merit further action.
FAA review and congressional briefing on noncompliance
After the GAO report the FAA must decide whether any agency found noncompliant should continue to use the exception and must brief the appropriate congressional committees within 30 days of the GAO report. This creates a near‑term administrative decision point about whether to suspend exception privileges for particular operators.
Agency reporting requirements and congressional reports
Requires each Federal, State, local, and Tribal agency performing sensitive missions to send the FAA quarterly attestations that they normally transmit ADS‑B Out and a flight‑by‑flight list of operations in which ADS‑B Out was off (including airport/airspace, date, time, duration, and mission type). The FAA must produce biannual reports to Congress with aggregated data and safety determinations, and may include a classified annex. A special notification rule triggers a congressional alert if an agency uses the exception five or more times in a calendar month or fails to submit the attestation.
Annual DOT Inspector General audits
Requires the DOT Inspector General, starting three years after enactment, to conduct annual audits of FAA oversight of all operations that use the exception (including federal agency flights). Audits must assess whether exceptions are strictly used as allowed, whether noncompliant operators are identified and engaged, and any other oversight weaknesses; the IG must brief Congress annually on findings.
Definitions and committee list
Defines terms used in the section — Administrator, ADS‑B Out, FAA — and lists the 'appropriate committees of Congress' to receive reports (House Transportation & Infrastructure, House Armed Services, Senate Commerce, Senate Armed Services), clarifying which congressional offices will get the new data and briefings.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Commercial airlines and pilots — they gain clearer, enforceable limits on when government aircraft can stop broadcasting, reducing unexpected blind spots in surveillance and improving operational predictability for ATC.
- FAA and congressional oversight committees — the bill supplies routine, flight‑level data, formal decision points, and audit authority that strengthen oversight and make it easier to detect misuse or systemic patterns.
- General aviation and airspace users — more consistent ADS‑B visibility across the NAS should improve situational awareness and reduce collision risk from non‑broadcasting flights.
Who Bears the Cost
- Department of Defense and other government operators — they must document precise segments for non‑broadcasting, submit quarterly flight‑level reports, and potentially face restrictions or loss of exception privileges if flagged, adding administrative burden and operational friction.
- FAA — the agency must run a rulemaking on a short timetable, revise MOAs, process quarterly data from multiple agencies, and absorb additional oversight and enforcement workload, requiring staff time and possibly new IT/reporting capacity.
- State, local, and Tribal agencies — smaller agencies with limited aviation staff will incur compliance costs to assemble attestations and detailed flight logs and may have to change mission procedures to stay within the narrowed exception.
Key Issues
The Core Tension
The central dilemma is balancing aviation safety and public transparency against legitimate operational secrecy and mission effectiveness: the bill presses for narrower, auditable exceptions to protect the national airspace system, but doing so risks exposing or disrupting truly sensitive government missions unless regulators design an implementable, secure, and well‑resourced process.
The bill tightens oversight and creates a strong paper trail, but it leaves significant implementation questions unresolved. "Narrowly construing" a "sensitive government mission" sounds clear in principle but requires a technical regulatory definition and operational guidance: who decides what counts as "sensitive," how narrowly must a flight segment be drawn, and what evidence must an agency keep to substantiate a claim? The one‑year rulemaking window forces the FAA to act quickly, but producing granular operational guidance and MOA revisions across multiple agencies in that time could be procedurally and diplomatically difficult.
The reporting regime increases transparency but raises tradeoffs. Flight‑level reporting (airport/airspace, date, time, duration, mission type) improves oversight but may conflict with legitimate operational security needs; the bill allows a classified annex, yet classified handling adds administrative friction and may limit the utility of aggregated public data.
The 5‑times‑per‑month trigger is an enforceable bright line, but it risks either underinclusive enforcement (agencies could cluster uses just under the threshold) or overreach that penalizes routine training or expected mission patterns. Finally, the bill shifts resource burdens to FAA, the DOT IG, and agencies themselves; without dedicated funding, enforcement and meaningful audits could be uneven, turning statutory requirements into largely documentary compliance rather than operational change.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.