- Potential benefitIncreases privacy protections for pilots and aircraft owners by limiting commercial use of ADS‑B data to identify aircr…
- Potential benefitPreserves ADS‑B use for air traffic control and safety while requiring Secretary of Transportation approval and public…
- StudentsAdds transparency and constraints on airport fees for general aviation by requiring airports to publish cost estimates,…
PAPA Act of 2025
Referred to the Subcommittee on Aviation.
The Pilot and Aircraft Privacy Act of 2025 restricts how data from automatic dependent surveillance–broadcast (ADS–B) can be used, mainly forbidding use of ADS–B data to identify aircraft for the purpose of obtaining revenue from owners or operators without their consent. It affirms ADS–B use for air traffic controllers for tracking and safety and requires the Secretary of Transportation to publish notice and allow public comment before permitting other uses.
Privacy vs. public-interest data uses: liberals and centrists worry about hampering safety, law enforcement, and environmental monitoring; conservatives emphasize privacy and limits on revenue extraction.
Relative to its intended legislative type, this bill establishes substantive legal limits on ADS–B data use and prescribes procedural and substantive conditions for imposition and use of fees on general aviation, but the text contains drafting ambiguities and lacks comprehensive implementation, enforcement, and fiscal detail.
The Pilot and Aircraft Privacy Act of 2025 restricts how data from automatic dependent surveillance–broadcast (ADS–B) can be used, mainly forbidding use of ADS–B data to identify aircraft for the purpose of obtaining revenue from owners or operators without their consent.
It affirms ADS–B use for air traffic controllers for tracking and safety and requires the Secretary of Transportation to publish notice and allow public comment before permitting other uses.
The bill also amends Title 49 to prohibit Federal, State, local, territorial, or Tribal officials from certain uses of ADS–B data (language in the amendment is intended to broadly limit officials’ use).
On content alone, the bill is plausible as a law because it is limited in scope, not a dramatic regulatory expansion, and contains administrative carve-outs and FAA rulemaking authority. However, it constrains local revenue practices and limits some uses of government-held surveillance data, raising predictable opposition from airport operators, local governments, and potentially agencies that rely on ADS–B data. Its success would depend heavily on stakeholder negotiations and agency responses; absent broad stakeholder buy‑in, progress beyond the House committee stage into the full Senate and enactment is uncertain.
Relative to its intended legislative type, this bill establishes substantive legal limits on ADS–B data use and prescribes procedural and substantive conditions for imposition and use of fees on general aviation, but the text contains drafting ambiguities and lacks comprehensive implementation, enforcement, and fiscal detail.
Privacy vs. public-interest data uses: liberals and centrists worry about hampering safety, law enforcement, and environmental monitoring; conservatives emphasize privacy and limits on revenue extraction.
Who stands to gain, and who may push back.
These are examples from the analysis, not a ranked list of the most-affected groups.
- Potential burdenCould impede non‑safety uses of ADS‑B data that some officials or private services currently rely on for investigations…
- Local governmentsMay constrain airports’ ability to raise revenue from general aviation through landing or takeoff fees, increasing fisc…
- Local governmentsImposes new administrative and compliance burdens on public‑use airports (preparation and publication of disclosures an…
Why the argument around this bill splits.
Privacy vs. public-interest data uses: liberals and centrists worry about hampering safety, law enforcement, and environmental monitoring; conservatives emphasize privacy and limits on revenue extraction.
A mainstream progressive would likely view the bill as offering useful privacy protections for individual pilots and small operators, and as supporting small-scale general aviation (flight training, nonprofits).
They would welcome restrictions on using surveillance data for revenue extraction without consent but would be attentive to whether the bill unintentionally restricts legitimate public-interest uses of ADS–B data (for safety, law enforcement, environmental monitoring, or investigations).
The requirement that airports disclose plans and restrict fee uses is appealing from a transparency and small-actor protection perspective, but progressives may worry that constraining fee uses could limit funding for broader community or environmental mitigation projects.
A pragmatic moderate would see the bill as a targeted privacy and transparency measure that balances pilot privacy and airport financial transparency with continued air traffic safety uses.
They would appreciate the built-in process (Secretary’s notice and comment) for expanding ADS–B uses, but would want clearer definitions and predictable procedures to avoid administrative confusion.
On fees, they would favor the transparency and restrictions to ensure fees are used for safety, while also wanting flexibility so airports can meet legitimate funding needs.
A mainstream conservative would likely view the bill favorably as a protection against government overreach and as a defense of private citizens, small-business pilots, and general aviation hobbyists from surveillance-based monetization and local fee burdens.
The bill’s limits on officials using ADS–B data and the restriction that fee proceeds be used only for airside safety align with skepticism of expansive government use of data and of local authorities imposing fees on private aviators.
Some conservatives could object to federal restrictions on local airport authority, but many would prioritize privacy protections and limits on new revenue mechanisms targeted at general aviation.
The path through Congress.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
On content alone, the bill is plausible as a law because it is limited in scope, not a dramatic regulatory expansion, and contains administrative carve-outs and FAA rulemaking authority. However, it constrains local revenue practices and limits some uses of government-held surveillance data, raising predictable opposition from airport operators, local governments, and potentially agencies that rely on ADS–B data. Its success would depend heavily on stakeholder negotiations and agency responses; absent broad stakeholder buy‑in, progress beyond the House committee stage into the full Senate and enactment is uncertain.
- The bill text contains at least one unclear drafting point (the amendment to 49 U.S.C. 46101(c) is syntactically confusing), which could affect interpretation and implementation and invite technical corrections or litigation.
- The bill does not include a Congressional Budget Office cost estimate or analysis of administrative burdens; unknown fiscal and compliance impacts could affect committee and floor support.
Recent votes on the bill.
No vote history yet
The bill has not accumulated any surfaced votes yet.
Go deeper than the headline read.
Privacy vs. public-interest data uses: liberals and centrists worry about hampering safety, law enforcement, and environmental monitoring;…
On content alone, the bill is plausible as a law because it is limited in scope, not a dramatic regulatory expansion, and contains administ…
Relative to its intended legislative type, this bill establishes substantive legal limits on ADS–B data use and prescribes procedural and substantive conditions for imposition and use of fees on general aviation, but th…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.