Wireless carriers get broad immunity for satellite alerts and data sharing

What it does

This bill allows wireless carriers to voluntarily transmit emergency alerts (like tornado warnings or Amber Alerts) via satellite to their customers' phones, in addition to existing ground-based alert systems. Carriers must file an election with the FCC within 60 days of the final rule, cannot charge extra for satellite alerts, must respect customer opt-outs, and are shielded from lawsuits for any failures or harms related to satellite alert transmission or the release of subscriber information to emergency responders.

Why we flagged it

The bill's core function is enabling satellite-based emergency alerts—a public-safety infrastructure goal. However, the operative mechanism includes a sweeping liability immunity for carriers that extends beyond alert transmission to cover subscriber data disclosure, which is a private-interest carve-out embedded in a public-safety frame.

What the text implies

• The liability shield covers not only failures to transmit alerts but also the release of subscriber information (location, phone number, device type) to government agencies and emergency responders, removing the primary legal remedy if carriers disclose data without proper safeguards or audit trails.
• The bill makes satellite alert transmission voluntary, meaning carriers can elect not to participate; those that do gain immunity, creating a two-tier system where some regions may have redundant alert coverage while others do not, with no obligation to ensure equitable geographic coverage.
• The FCC has 18 months to issue final rules, but the effective date is delayed until 36 months after publication OR 12 months after DHS/FEMA implement their own standards—whichever is later. This creates a 3–4 year implementation window during which carriers face regulatory uncertainty and may delay investment.
• Carriers are shielded from liability for 'any act or omission' related to satellite alerts, including negligence in system design, maintenance, or testing. This is broader than Good Samaritan protections and may insulate carriers from accountability for preventable failures.
• The bill does not require carriers to disclose to customers what subscriber data is being shared with government agencies in connection with emergency alerts, potentially creating a hidden data-sharing pathway.

Section numbers refer to the bill text the analysis read — linked under Primary records below.

Who it affects

Citizens gain a redundant emergency alert pathway that could reach people in areas with poor ground coverage, improving public safety in remote or disaster-affected regions. However, the broad liability shield for carriers—covering not just alert transmission but also release of subscriber data to government—removes a key legal remedy if carriers mishandle personal information or fail to transmit alerts, shifting risk from private companies to individuals.

Who stands to gain

• satellite communications providers (Viasat, Iridium, Intelsat, Globalstar)
• wireless carriers with satellite infrastructure (Verizon, AT&T, T-Mobile, Comcast/Xfinity Mobile)
• device manufacturers with satellite-capable phones (Apple, Samsung, Google)

Named in the bill

Federal Communications Commission (FCC), Department of Homeland Security (DHS), Federal Emergency Management Agency (FEMA), covered service providers (wireless carriers), Warning, Alert, and Response Network Act (WARN Act), Viasat (VSNT), Sirius XM (SIRI), Fox Corporation (FWONK), Comcast (CMCSA), News Corp (NWSA)

Where it stands

4 cosponsors: 2 Democrats, 2 Republicans.

• Jan 12, 2026 — Introduced · Congress.gov: “Introduced in House”
• Jan 12, 2026 — Referred to House Committee on Energy and Commerce and Senate Committee on Commerce, Science, and Transportation · Congress.gov: “Referred to the Subcommittee on Communications and Technology”
• Jan 15, 2026 — Markup held in committee · Congress.gov: “Subcommittee Consideration and Mark-up Session Held”
• Mar 25, 2026 — Reported out of committee · Congress.gov: “Ordered to be Reported (Amended) by the Yeas and Nays: 52 - 0”
• Apr 20, 2026 — Passed the House · Congress.gov: “On motion to suspend the rules and pass the bill, as amended Agreed to by voice vote. (text: CR H2970)”
• Apr 20, 2026 — Floor vote scheduled · Congress.gov: “Mr. Allen moved to suspend the rules and pass the bill, as amended”
• Sep 30, 2026 — Passed both chambers · Congress.gov: “Passed Senate without amendment by Unanimous Consent”
• Oct 15, 2026 — Sent to president · Congress.gov: “Presented to President”

Dates and quoted wording are Congress.gov's action record; the timeline shows status changes, not every procedural step.

Money around this bill

3 lobbying clients named this bill on 3 disclosure filings across 1 quarter, Jun 2026 to Jun 2026. Those filings disclosed $6,740,000 in lobbying spend. A filing names 26 bills on average, so that figure is what each filing reported, not a share belonging to this bill.

More lobbying clients named this bill than 61% of bills with at least one filing.

August Pfluger, the sponsor, reported $1,070,325 in PAC receipts in the 2026 cycle.

• Ctia-the Wireless Association — $3,640,000 on 1 filing
• Verizon Communications Inc and Various Subsidiaries — $3,050,000 on 1 filing
• Peace Officers Research Association of California — $50,000 on 1 filing

Lobbying Disclosure Act filings through Jul 20, 2026. A filing shows who paid to lobby on a bill it names, not what changed.