Read twice and referred to the Committee on Commerce, Science, and Transportation.
The Pilot and Aircraft Privacy Act prohibits using automatic dependent surveillance–broadcast (ADS–B) data to identify aircraft for the purpose of assessing a fee or otherwise charging an aircraft owner or operator. It restricts how air traffic controllers and, more broadly, government and non-government actors may use ADS–B data to tracking and safety purposes, with any additional uses subject to Department of Transportation rulemaking and public notice-and-comment.
Whether limits on ADS–B use will impair law enforcement and safety oversight (liberal concerned, conservative less worried).
Relative to its intended legislative type, this bill is a substantive statutory change that establishes new prohibitions on use of ADS–B data and new disclosure and funding restrictions related to fees on general aviation aircraft.
The Pilot and Aircraft Privacy Act prohibits using automatic dependent surveillance–broadcast (ADS–B) data to identify aircraft for the purpose of assessing a fee or otherwise charging an aircraft owner or operator.
It restricts how air traffic controllers and, more broadly, government and non-government actors may use ADS–B data to tracking and safety purposes, with any additional uses subject to Department of Transportation rulemaking and public notice-and-comment.
The bill also adds limits on airports’ imposition of landing/takeoff fees on general aviation aircraft: before imposing such fees airports must publicly disclose cost and revenue information and assess impacts on general aviation, and any revenues from those fees must be used only for airside safety projects.
On content alone, the bill is a focused, technically oriented measure that could earn support from privacy advocates and general aviation interests, which improves its prospects relative to sweeping or costly proposals. However, it also directly limits government investigatory tools and local airport revenue options, inviting pushback from airports, public‑safety entities, and possibly the FAA. The bill is short and implementable in principle, but drafting imprecision in places and the lack of compromise features (sunset, pilots, offsetting measures) lower its odds of clearing both chambers and resolving intergovernmental objections.
Relative to its intended legislative type, this bill is a substantive statutory change that establishes new prohibitions on use of ADS–B data and new disclosure and funding restrictions related to fees on general aviation aircraft. It identifies responsible actors and grants regulatory authority but lacks detailed implementation, enforcement, and fiscal scaffolding.
Whether limits on ADS–B use will impair law enforcement and safety oversight (liberal concerned, conservative less worried).
These are examples from the analysis, not a ranked list of the most-affected groups.
Whether limits on ADS–B use will impair law enforcement and safety oversight (liberal concerned, conservative less worried).
A liberal/left-leaning observer would see elements they like (privacy protections for private pilots) but also significant concerns.
They would worry that broad limits on ADS–B use could impede investigations of criminal or safety incidents and reduce regulators’ ability to monitor unsafe operations.
The restrictions on airport fee use and the requirement to limit fee revenues to airside safety projects could constrain airport financing for other community-serving projects; this raises equity and infrastructure funding concerns.
A centrist/ pragmatic observer would view the bill as a mix of reasonable privacy and transparency measures plus potentially problematic restrictions that could affect enforcement and airport finances.
They would appreciate disclosure requirements and limiting arbitrary fee imposition on general aviation, but want clarity about how the ADS–B limits interact with public safety, law enforcement, and FAA oversight.
They would likely favor amendments or regulatory detail that preserve safety/ investigatory uses while protecting pilots from fee-targeting and revenue abuse by airports.
A mainstream conservative observer would likely view the bill favorably as a protection of property rights, privacy, and limits on government and local authorities extracting fees from general aviation.
They would welcome prohibitions on using ADS–B data to impose charges and the constraint that fee revenue be used only for airside safety projects.
They would also see the transparency requirements for airports as reasonable checks on fee implementation.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
On content alone, the bill is a focused, technically oriented measure that could earn support from privacy advocates and general aviation interests, which improves its prospects relative to sweeping or costly proposals. However, it also directly limits government investigatory tools and local airport revenue options, inviting pushback from airports, public‑safety entities, and possibly the FAA. The bill is short and implementable in principle, but drafting imprecision in places and the lack of compromise features (sunset, pilots, offsetting measures) lower its odds of clearing both chambers and resolving intergovernmental objections.
The bill has not accumulated any surfaced votes yet.
Whether limits on ADS–B use will impair law enforcement and safety oversight (liberal concerned, conservative less worried).
On content alone, the bill is a focused, technically oriented measure that could earn support from privacy advocates and general aviation i…
Relative to its intended legislative type, this bill is a substantive statutory change that establishes new prohibitions on use of ADS–B data and new disclosure and funding restrictions related to fees on general aviati…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.