Military ADS–B Out Loophole Act
HB7240, the “Military ADS–B Out Loophole Act,” would direct the Federal Aviation Administration to tighten and clarify the regulatory exception that allows aircraft to turn off ADS-B Out transmissions during certain “sensitive government missions.” The bill requires the FAA to narrowly construe that exception and limit it to only the portion of a flight when sensitive activities are actually being carried out. It also requires the FAA to update its regulations and any related interagency agreements within one year of enactment.
The bill adds a substantial reporting and oversight framework. Federal, state, local, and tribal agencies using the exception would have to submit regular attestations and detailed flight-by-flight reports to the FAA, and the FAA would have to provide periodic reports to Congress on how often the exception is used, by whom, and whether particular uses jeopardize aviation safety. The Government Accountability Office would review compliance and compare use of the exception before and after the rule change, and the Department of Transportation Inspector General would begin annual audits of FAA oversight three years after enactment.
In practical terms, the bill would affect FAA regulations under 14 C.F.R. § 91.225(f)(1) and related memoranda of agreement with other government entities. It would not create a new aviation technology requirement, but it would significantly constrain when ADS-B Out can be disabled for government operations and increase transparency around military and other sensitive flights. Agencies found to be noncompliant could face additional scrutiny and possible limits on continued use of the exception.
The available context shows little recorded debate or voting history, so overall sentiment cannot be measured from committee transcripts or floor votes. Based on the bill text and title, the measure appears intended to close what sponsors characterize as a loophole and to improve accountability and aviation safety. The likely support base is among lawmakers concerned with transparency and airspace safety, while potential opposition would most likely come from defense or public-safety operators who rely on the exception for classified or sensitive missions and may view the reporting requirements as burdensome or operationally restrictive.
The main point of contention is the balance between aviation transparency/safety and operational secrecy or flexibility for government aircraft. The bill narrows the exception, requires detailed reporting of mission type, location, and timing, and authorizes congressional oversight, which could raise concerns about exposing sensitive operational patterns. At the same time, supporters would likely argue that the current exception is too broad and that stronger oversight is needed to ensure ADS-B Out is used consistently and safely.
The bill would amend the FAA’s implementation of ADS-B Out exception rules under 14 C.F.R. § 91.225(f)(1), requiring the agency to narrow the definition of “sensitive government mission,” revise related regulations and interagency agreements, and establish recurring reporting, GAO review, and Inspector General audits. It would directly affect federal, state, local, and tribal agencies that conduct sensitive operations, as well as any other operators eligible for the exception, by increasing compliance obligations and congressional oversight.
No committee transcript or vote data is provided, so there is no recorded legislative sentiment to measure from debate or roll calls. From the bill text and title, the measure appears to be framed positively by its sponsor as a safety-and-accountability reform aimed at closing a perceived loophole. The likely general sentiment is supportive among aviation-safety and oversight advocates, with possible reservations from defense and law-enforcement stakeholders who may prefer broader discretion and less public reporting.
The central contention is whether the ADS-B Out exception for sensitive government missions is too broad and insufficiently monitored. Supporters of the bill would likely argue that the exception should be narrowly limited to actual sensitive portions of flights and that agencies should be accountable for repeated or improper use. Opponents or cautious stakeholders would likely focus on operational security, mission confidentiality, and the administrative burden of detailed reporting, especially for military and other sensitive government flights.