Congress is weighing potential aviation safety upgrades after a cluster of close-call incidents drew federal attention, according to a WBFF report framed under the headline "Congress weighs aviation safety upgrades after series of close calls."

The legislative review sits at the intersection of the National Transportation Safety Board, the Federal Aviation Administration and the Senate and House committees that traditionally oversee civil aviation. WBFF's framing stops short of identifying the specific flights, airports or operators at issue, but the political trigger — repeated near-miss events — is consistent with the pattern that has repeatedly sent lawmakers back to FAA safety programs.

What triggered the review?

WBFF's "series of close calls" language points to a run of incidents serious enough to draw Capitol Hill interest, though the report does not name them. Recent publicly tracked episodes — including the 2023 runway-incursion event at Ronald Reagan Washington National involving an American Airlines regional jet cleared to cross the same runway on which a Delta Air Lines 737-800 was cleared for takeoff — have shaped that backdrop. Such events tend to produce immediate questions on separation standards, surface-alerting fidelity and controller decision support.

Lawmakers have responded to similar clustering before by pulling FAA performance metrics, asking the NTSB for accelerated recommendations and convening hearings before the Senate Commerce, Science and Transportation Committee and the House Transportation and Infrastructure Committee. Past hearings have repeatedly examined runway-status lights, terminal automation and Surface Awareness Initiative tools.

What upgrades are typically in scope?

The WBFF story does not enumerate specific legislation, but the policy menu Congress historically presses after near-miss episodes is well-defined:

• Retrofit of cockpit surface-alerting equipment, including ASDE-X/ASSC integration and runway-status-aural callouts
• Controller-staffing targets and academy throughput at the FAA's air traffic organization
• Terminal-radar refresh and multilateration coverage
• Crew resource-management and surface-incident-recurrent training cadence
• Safety management system adoption across Part 121 and Part 135 operators

Each item carries distinct cost implications. Ground-infrastructure mandates land almost entirely with the FAA and its procurement budget; equipment mandates affect network carriers, regional operators and fractional/Part 135 fleets through per-aircraft retrofit, simulator recalibration and recurrency-training hours.

How does the regulatory pipeline move?

Statutory direction from Congress typically reaches the FAA as legislative language requiring rulemaking, with the Aircraft Certification Service or Flight Standards Service running the technical review. Mandates affecting transport-category operations require Federal Register notice-and-comment, a process that historically runs 18 months to several years depending on complexity, technical readiness and industry pushback. RTCA, Inc. consensus standards often serve as the technical baseline for cockpit and ground systems.

NTSB recommendations that survive the agency's weighting exercise and reach the FAA carry a separate but parallel urgency. The board's Most Wanted List has repeatedly flagged runway incursions, safety management systems and general aviation oversight — three areas where close-call data concentrate.

What to watch next

Without specific bill text or hearing schedules in the WBFF report, the cleanest near-term signals will be committee statements, posted witness lists and FAA briefing requests to Congress. Trade associations representing mainline carriers, regional partners and business aviation typically file comment letters when formal rulemaking opens, and those filings are the earliest reliable read on cost and timeline pressure across the operator base.

The decisive political question — whether the review produces binding mandates or a softer direction to the FAA — will likely turn on how many of the recent events qualify as "serious incidents" under 49 CFR 830.5 and whether NTSB recommendations land before the next FAA reauthorization cycle. That calculation runs against an industry still absorbing prior safety directives and a controller workforce whose hiring pipeline has lagged operational demand for several years.