Congress mandates shark-attack alerts on your phone

What it does

This bill requires the FCC to allow wireless emergency alerts (the system that sends urgent messages to cell phones) to be used for shark attack warnings within 180 days of enactment. The bill is named after Lulu, apparently a shark attack victim, and would expand the types of emergencies that trigger automatic public alerts to include shark attacks.

Why we flagged it

The bill's sole operative mechanism is a mandate to the FCC to add shark attacks to the list of events triggering wireless emergency alerts. It is a narrow, single-purpose expansion of an existing public-safety system.

What the text implies

• Bill does not specify alert thresholds, geographic scope, or confirmation protocols—FCC has discretion to define 'shark attack' and alert criteria, potentially creating system-wide alert fatigue if alerts are triggered for minor incidents.
• Wireless emergency alert system is designed for mass-casualty, imminent-threat scenarios (hurricanes, active shooters, tsunamis); adding low-frequency events may degrade public attention to high-severity alerts.
• No appropriations or funding mechanism specified; implementation cost and resource allocation to FCC are undefined.
• Bill does not address liability or false-alarm consequences if alerts are issued in error or for non-threatening shark sightings.

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

Who it affects

Shark attack alerts could provide real-time safety information to beachgoers in affected areas, potentially saving lives through rapid warning. However, the bill's actual public-health benefit is unclear—shark attacks are extremely rare (fewer than 50 per year in the U.S.), and the cost-benefit of system-wide alert infrastructure expansion for such low-frequency events is uncertain. The bill does not specify alert criteria, frequency limits, or false-alarm protocols, creating risk of alert fatig

Named in the bill

Federal Communications Commission (FCC), Wireless Emergency Alert System, 47 CFR 10.10(a)

Where it stands

3 cosponsors: 3 Democrats.

• Mar 11, 2025 — Introduced · Congress.gov: “Introduced in House”
• Mar 11, 2025 — Referred to House Committee on Energy and Commerce · 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”
• Apr 9, 2026 — Reported out of committee · Congress.gov: “Placed on the Union Calendar, Calendar No. 518”

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