Analyses / Impact Analysis / 119 · HR 5200 Impact Analysis

119-HR-5200 Data-Driven Journalist Impact Analysis

119 · HR 5200 Emergency Reporting Act

science Science, Technology, Communications
Emergency Reporting ActThis bill requires the Federal Communications Commission (FCC) to investigate and report on emergency communications outages (e.g., 9-1-1 outages).Specifically, the FCC must...
Bottom-line assessment
Analytical stance (not advocacy).
House vote (Apr 20, 2026)
386yeas (7 nays)
Senate placement
375Calendar No.
DIRS hearing coverage threshold
7days of activation
Post‑hearing report deadline
120days after hearing
Published
24 Apr 2026
Updated
24 Apr 2026
Tags
impact-analysis · telecom · public-safety
Unvetted
01 · Section

Summary

What it does and why it matters

Scope and mechanisms. The bill requires the FCC to (a) hold at least one public hearing each year on disasters where the Disaster Information Reporting System (DIRS) was active for ≥7 days, and (b) publish a report within 120 days quantifying broadband, VoIP, and mobile outages; users/infrastructure affected; 911 center impairments; and resiliency recommendations. It also mandates a one‑year study on improving 911 outage notifications, including the value of adding visual information (e.g., maps) and estimating the volume of outages that fall below current reporting thresholds. (congress.gov)

Status as of April 24, 2026. The House passed H.R. 5200 on April 20, 2026 by 386–7; it was received in the Senate on April 21 and placed on the Legislative Calendar under General Orders (Calendar No. 375). (govinfo.gov)

House vote (Apr 20, 2026)
386yeas (7 nays)
Senate placement
375Calendar No.
DIRS hearing coverage threshold
7days of activation
Post‑hearing report deadline
120days after hearing
FCC outage‑notification study deadline
1year from enactment
Current practice: DIRS reporting
1mandatory for cable, wireline, wireless, VoIP when activated

Data context. DIRS provides incident‑time network status (e.g., cell sites out, PSAP impacts) that complement the Commission’s outage rules and the 2024 move to mandate DIRS reporting for core provider categories—while preserving confidentiality and controlled data sharing. The bill channels those data into public hearings and after‑action reports to surface systemic lessons. (docs.fcc.gov)

Deliverable Timeline Responsible party
Annual public hearing covering disasters with ≥7‑day DIRS activation Within 1 year of enactment and annually thereafter FCC
After‑action report (outages, affected users/infrastructure, PSAP effects, recommendations) Within 120 days after each hearing FCC
Study report on 911 outage notifications (value of visual info; under‑reporting; recommended rule changes) Within 1 year of enactment FCC
02 · Section

Economic Effects

Costs and benefits for providers, markets, and the public sector; methods emphasize existing FCC filings, enforcement records, and prior cost estimates.

  • Administrative costs to FCC. New hearings and reports impose modest agency workload but leverage existing DIRS/NORS datasets and confidentiality framework; no new technical system is required by statute. (congress.gov)
  • Provider reporting burden. For many providers, DIRS reporting is already mandatory when activated (cable, wireline, wireless, interconnected VoIP), limiting incremental costs from the bill’s analytic/reporting overlay. The DIRS regime emphasizes daily situation updates during activations. (docs.fcc.gov)
  • Potential future compliance costs if outage‑reporting rules evolve. FCC analyses show that expanding outage reporting (e.g., to additional sectors or richer content) can be material—for example, staff estimated broadcaster compliance at ~$33.5M/year for NORS and ~$0.21M/year for DIRS under a considered expansion. These figures illustrate potential upper‑bound burdens if requirements broaden. (docs.fcc.gov)
  • Burden‑reduction offset during disasters. When DIRS is activated, the FCC typically waives overlapping NORS obligations within the activation area for participating providers—reducing duplicative reporting. (docs.fcc.gov)
  • Risk‑management and enforcement externalities. Clearer, standardized after‑action expectations—and the study on outage notifications—can reduce costly compliance failures. Recent consent decrees (e.g., Charter’s $15M settlement over outage/911 reporting lapses) highlight the financial stakes of inadequate processes. (docs.fcc.gov)
  • Macroeconomic resilience channel (inference). Faster situational awareness and better outage data can shorten restoration times and reduce business interruption, particularly in disasters where comms and energy are interdependent lifelines; GAO has documented sharp growth in physically caused wireless outages, supporting the need for improved monitoring. (gao.gov)
03 · Section

Social Effects

Implications for emergency communications centers (PSAPs), first responders, and communities.

  • PSAP situational awareness. The bill’s focus on quantifying PSAP impairments and investigating enhanced notification content aligns with FCC’s 2022 order harmonizing 911 outage notifications across providers and exploring the utility of graphical information. Improved, standardized alerts can help PSAPs triage and message alternatives to the public. (docs.fcc.gov)
  • Inclusion and accountability. Hearings explicitly contemplate participation by residents, local/Tribal officials, infrastructure companies, and first responders—elevating on‑the‑ground experience into formal lessons‑learned. This can surface equity issues (e.g., rural backhaul dependence) that raw outage counts miss. (congress.gov)
  • Emergency response effectiveness. Reliable communications is repeatedly described by CISA as a “lifeline” function; documenting communications performance after major incidents (e.g., wildfires, hurricanes) improves preparedness and public messaging in future events. (cisa.gov)
04 · Section

Environmental Effects

Direct environmental impacts are limited; the pathway is largely indirect via disaster response efficacy.

  • No direct emissions mandates. The bill is procedural (hearings/reports/study) and does not authorize new infrastructure builds; immediate environmental footprint is minimal. (congress.gov)
  • Indirect benefits via response coordination. Post‑incident analytics that pinpoint where communications failed can guide hardening and faster restoration in future wildfires, hurricanes, and floods—potentially reducing secondary environmental harms (e.g., spill risks, fire spread). FCC DIRS reports from the 2023 Maui wildfires illustrate how status data on PSAPs, cell sites, and wireline subscribers inform tactical decisions. (docs.fcc.gov)
  • Interdependent lifelines. Because communications depend on power and other lifelines, resilience gains in networks can compound environmental response capacity (e.g., coordinated power restoration reduces generator use and truck rolls). This interdependency is recognized in CISA lifeline guidance. (cisa.gov)
05 · Section

Temporal Analysis

Short‑term implementation vs. long‑term system learning.

  • Short term (Year 1). FCC organizes at least one hearing, compiles a 120‑day after‑action report, and completes the outage‑notification study. Incremental costs center on staff time, stakeholder engagement, and synthesizing existing DIRS/NORS data. (congress.gov)
  • Medium term (1–3 years). Hearing cycles accumulate comparable datasets across disasters, enabling benchmarking of restoration timelines, PSAP impacts, and drivers (backhaul, power, access). This complements mandatory DIRS daily reporting during activations. (docs.fcc.gov)
  • Long term (multi‑year). Evidence base supports targeted rule adjustments (e.g., notification content, thresholds) and infrastructure investments; GAO‑identified trends in physical‑incident outages provide a baseline to evaluate whether reforms reduce outage frequency/duration over time. (gao.gov)
06 · Section

Unintended Consequences and Risks

Where secondary effects could emerge; emphasis on data governance and burden asymmetries.

  • Asymmetric burdens on small providers. FCC has previously deferred requiring GIS data in PSAP notifications due to IT burden and uneven PSAP capability. Any push toward richer visual content should be informed by the bill’s study and calibrated to small‑entity capacity. (docs.fcc.gov)
  • Data completeness and comparability. DIRS covers core providers mandatorily when activated, but legacy gaps for other sectors and variations in reporting cadence/quality can complicate cross‑event comparisons. The bill’s hearing record should document such limitations. (docs.fcc.gov)
  • Compliance exposure. After‑action transparency may surface process gaps; however, clearer expectations can also mitigate enforcement risk. Recent consent decrees (Charter; others) underscore that outage/PSAP‑notification obligations are actively enforced. (docs.fcc.gov)
07 · Section

Assessment

Analytical stance (not advocacy).

Overall stance: neutral. On balance, the legislation operationalizes learning loops (public hearings + structured reports) that reuse existing data systems, with limited direct costs and plausible resilience benefits. The main execution risks are data‑governance safeguards and avoiding unfunded mandates if the study leads to richer—but burdensome—notification content. If FCC follows its prior cautions on visual/GIS requirements and adheres to confidentiality protocols for DIRS/NORS, expected net effects are modestly favorable for situational awareness and public safety without material market distortion. (docs.fcc.gov)

08 · Section

Sourcing and Method Notes

Sources prioritize primary legal and administrative texts: Congress.gov bill text/status; House and Senate calendars; FCC orders, public notices, and DIRS reports; GAO oversight; and CISA lifeline guidance. All quantitative or procedural claims in this analysis trace to those documents; interpretive statements are identified as inferences (e.g., resilience channels). (congress.gov)

Discussion