Codify — Article

WING Act of 2025 creates NWS RDT&E program to tackle radar obstructions

Directs the National Weather Service to test technologies and data strategies to reduce radar degradation from wind turbines and buildings—potentially reshaping radar procurement and data-sharing with private providers.

The Brief

The bill directs the National Weather Service to establish a Research, Development, Test, and Evaluation (RDT&E) Program to study how physical obstructions in radar lines of sight—explicitly including wind turbines and buildings—affect radar detection and forecasting, and to develop commercially viable mitigation solutions. The statute requires coordination with the Assistant Administrator for Oceanic and Atmospheric Research and consultation with the Interagency Council for Advancing Meteorological Services, and it encourages partnerships with industry, academia, and state and local governments.

This matters because degraded radar returns can compromise short-term forecasts, public warnings, and aviation safety, while disputes over radar interference have increasingly arisen around wind energy deployment and local development. By prioritizing technology testing and commercial pathways, the bill aims to produce practical fixes (from algorithms to sensors) that federal and private actors can adopt, and to produce a formal recommendation on whether further field research is warranted.

At a Glance

What It Does

Creates a time‑limited NWS RDT&E Program that identifies, tests, and develops mitigation technologies and data strategies to overcome radar beam blockage and false returns caused by physical obstructions, and charges the Director with moving promising solutions toward commercial viability.

Who It Affects

Directly affects the National Weather Service and NOAA research arms, radar manufacturers and vendors, private meteorological data providers, wind energy developers and operators, state/local emergency managers, and companies operating meteorological towers or ground sensors that could feed radar gaps.

Why It Matters

The Program could change how operational meteorology combines federal and private data, influence procurement choices (for example, between phased‑array upgrades and distributed sensors), and provide technical evidence that informs wind‑farm siting and mitigation conversations between developers and communities.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

The bill sets a focused research program inside the National Weather Service with the explicit goal of finding technical and data-driven fixes for radar problems caused by obstructions. Rather than prescribing one technological path, it charges the NWS to evaluate existing or near-commercial offerings, develop new signal‑processing and short‑term forecasting approaches, and push viable options toward commercial use so operators can adopt them outside the laboratory.

Implementation emphasizes partnerships: the NWS must work with the Office of Oceanic and Atmospheric Research and consult the Interagency Council for Advancing Meteorological Services, and it is expected to bring in industry, academia, and state and local partners for testing and data exchange. The statute frames the work as practical and operational—field testing, cross‑validation with non‑radar sensors, and demonstrations that show how a mitigation would integrate into a local forecaster’s workflow.Practically speaking, the Program is structured to explore both software and hardware paths.

Software approaches include advanced signal processing and short‑term forecasting to fill or correct contaminated returns. Hardware and deployment approaches rely on alternative data streams—commercial radars, private meteorological towers, and in situ gauges—and on ways to make those streams available to local systems (for instance, by mapping wind‑farm footprints on forecasting displays).

The bill stops short of mandating remediation by private developers; it sponsors the evidence base that policymakers and operators can use to decide next steps.Because the statute ties the Program to commercial viability, the NWS will need to evaluate cost, integration complexity, and maintainability as part of each test. That creates a practical pipeline: identify candidate technology, test accuracy and operational fit, and assess whether vendors or partners can deliver it at scale so that weather services and local stakeholders can adopt it without ongoing federal support.

The Five Things You Need to Know

1

The Director must submit an implementation report to Congress not later than two years after enactment and then annually until the Program terminates.

2

Within five years the Director must deliver a final recommendation on whether additional RDT&E is needed and whether to cease field research, effectively forcing a decision point on continuation.

3

The Program’s authority expires on the earlier of September 30, 2030, or one year after the Director submits the final recommendation to Congress.

4

The statute defines “obstruction” to include wind turbines and buildings and creates operational definitions for “beam blockage” and “ghost echo.”, Subsection (c) lists prioritized mitigation approaches for study, naming multifunction phased‑array radar, replacing contaminated data with commercial radar sources, use of private meteorological towers, displaying wind‑farm boundaries in local forecast systems, and installing/providing access to rain gauges.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section 1

Short title

Establishes the Act’s name: the Weather Innovation for the Next Generation Act of 2025 (WING Act). This is purely nominal but useful when tracking follow‑on appropriations or cross‑referencing in policy documents.

Section 2(a)

Program establishment at NWS

Gives the Director of the National Weather Service explicit authority to stand up an RDT&E Program and requires coordination with NOAA’s research arm (the Assistant Administrator for Oceanic and Atmospheric Research). That placement keeps operational radar expertise inside NWS while tying in scientific R&D capacity from OAR, which matters for test design and evaluation standards.

Section 2(b)

Scope and partnership requirements

Directs the Director, in consultation with the Interagency Council for Advancing Meteorological Services, to partner with industry, academia, and government entities to identify and test candidate technologies and to research algorithmic and data‑replacement solutions. The provision is broad about partners—permitting private vendors to participate—and it requires the Program to pursue both existing/near‑commercial tech and new research avenues.

4 more sections
Section 2(c)

Priority mitigation technologies

Specifies a prioritized list of technology‑based mitigations the Director must consider, including multifunction phased‑array radar, integrating commercial radar data to replace contaminated returns, tapping private meteorological towers, displaying consolidated wind‑farm footprints on local tools, and installing rain gauges. By enumerating these items the bill nudges the Program toward certain operational paths and gives Congress a lens to evaluate progress.

Section 2(d)

Sunset of authority

Places a clear planning horizon on the Program: authority terminates either on September 30, 2030, or one year after the Director’s final recommendation. That deadline forces prioritization of near‑term, actionable tests and signals to potential partners that the window for federally led field work is finite.

Section 2(e)

Reporting and final recommendation

Requires an initial report to Congress not later than two years after enactment and annual reporting thereafter until termination, with a required final recommendation at the five‑year mark on whether to continue RDT&E. Reports must evaluate each prioritized mitigation, which sets an evidentiary standard for congressional oversight and any subsequent policy choices.

Section 2(f)

Operational definitions

Defines core terms—beam blockage, ghost echo, Director, and obstruction (including wind turbines and buildings). These definitions narrow interpretive disputes about what the Program must study and provide a foundation for consistent test metrics across sites and vendors.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Science across all five countries.

Explore Science in Codify Search →

Who Benefits and Who Bears the Cost

Every bill creates winners and losers. Here's who stands to gain and who bears the cost.

Who Benefits

  • National Weather Service and NOAA research programs — gain a formal, resourced mandate to test practical fixes and access to private and academic partners to validate operationally relevant solutions.
  • Operational forecasters and emergency managers — stand to get improved short‑term radar products or complementary data streams that reduce false echoes and uncovered gaps, improving warning lead time and local situational awareness.
  • Private meteorological data providers and radar manufacturers — the Program’s commercialization focus creates market opportunities for vendors that can field validated, operationally integrated mitigation products.
  • Wind‑energy developers and local planners — benefit from clearer technical pathways to mitigate radar interference; validated solutions could reduce conflict over siting and provide predictable mitigation options.
  • Commercial and academic research groups — receive funding and partnership opportunities to move prototype algorithms and sensors through field validation to operational use.

Who Bears the Cost

  • National Oceanic and Atmospheric Administration (NOAA) and NWS — must allocate staff time, lab and field resources, and likely appropriated funding to run multi‑site tests and evaluations over several years.
  • State and local governments or utilities — may be asked to host tests, share data from towers or gauges, or assist with permitting for sensor installations, creating in‑kind or direct costs.
  • Private partners — vendors and data providers will need to commit engineering, data access, and possibly hardware to demonstrate commercial viability, which can be expensive and risky if a product fails tests.
  • Wind developers and building owners — while not directly required by the bill, they may incur retrofit or mitigation costs if the Program’s recommendations identify practical fixes that regulators or communities adopt.
  • Future federal purchasers — if the Program recommends hardware upgrades (for example, phased‑array radars), future acquisition budgets could be affected by expensive procurement choices.

Key Issues

The Core Tension

At its core the bill confronts a classic trade‑off: invest limited federal resources in rapid, commercially adoptable fixes that reduce immediate radar degradation, or fund longer‑term, capital‑intensive infrastructure changes that could eliminate the problem more completely; choosing the former speeds near‑term benefits and favors marketable solutions, while the latter demands sustained funding and creates a bigger public procurement question—especially when those choices intersect with wind‑energy siting and private data access.

The statute sets a pragmatic, short‑horizon RDT&E effort, but that design creates trade‑offs. A five‑year decision point and a statutory sunset favor near‑term, demonstrable fixes over long‑lead infrastructure upgrades.

That increases the chance the Program will prioritize low‑cost, rapidly deployable options (data fusion, gauges, algorithms) over capital‑intensive replacements (widespread phased‑array deployments), even where the latter may deliver superior long‑term performance.

The bill steers the Program toward commercial viability, which is sensible for adoption but introduces potential bias: technologies that are easiest to commercialize or that fit existing vendor business models may get priority over approaches that are scientifically optimal but harder to monetize. The reliance on private data streams raises practical questions about data access agreements, costs, quality control, latency, and sustained availability—issues the statute does not resolve and that can undermine operational integration if not addressed in contracts and tests.

Finally, the law frames obstructions to include wind turbines and buildings, which places the Program at the intersection of meteorology and land‑use/energy policy. Producing technical mitigation options will not by itself resolve siting disputes; it may, however, shift negotiations toward technical fixes that impose costs on developers or operators.

The bill gives NWS authority to test solutions but leaves open how those results translate into regulatory expectations or funding commitments for expensive hardware upgrades.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.