The Runway Safety Bill, the Surface Incursion Problem, and What Capitol Hill Just Did About the Most Dangerous Fifty Feet in Aviation

The Senate Commerce Committee has cleared a bipartisan runway safety bill directing the FAA to accelerate deployment of surface detection technology and strengthen training standards for surface operations. The legislation responds directly to a string of high-profile near-collisions in 2023 that exposed systemic gaps in how the U.S. aviation system manages the most dangerous fifty feet in flight: the crossing of an active runway.

What the Senate Runway Safety Bill Does

The bill, reported by Flying Magazine following the committee markup, targets two core areas. First, it pushes for broader deployment of surface detection and alerting technology - specifically systems like Airport Surface Detection Equipment Model X (ASDE-X) and the Runway Status Lights (RWSL) system - which are currently concentrated at the busiest commercial airports. Second, it directs attention to pilot and controller training standards for surface operations, where the majority of incursions actually originate.

The legislation passed with bipartisan support. That consensus signals something important: runway safety is an engineering and human factors problem, not a political one.

The 2023 Near-Misses That Sent This to Congress

Three serious runway incursion events unfolded in early 2023, all within weeks of each other, at three different airports.

Austin-Bergstrom International Airport, February 2023: A FedEx Boeing 757 on approach to Runway 18L descended through 400 feet while a Southwest Boeing 737 held for takeoff clearance on the same runway. The 757 closed to within 100 feet vertically and 900 feet horizontally before executing a go-around. The NTSB later found the controller had cleared Southwest onto the runway before the FedEx arrival had safely passed.

John F. Kennedy International Airport, January 2023: A Delta Air Lines Airbus A321 crossed Runway 4L while an American Airlines Boeing 777 was rolling for takeoff. The 777 crew rejected the takeoff at 133 knots - decision speed on a heavy jet - after visually acquiring the Delta aircraft on the runway ahead.

Sarasota-Bradenton International Airport, February 2023: A Cessna Citation crossed an active runway in front of a Republic Airways Embraer 175 on short final. The Embraer crew executed a go-around. The Citation crew did not know how close the margin had been until afterward.

Three Category A or B events in a matter of weeks. All different airports. All different contributing factors. All survivable by seconds or feet.

How the FAA Classifies Runway Incursions

The FAA tracks runway incursions in four severity categories. Category A is a collision narrowly avoided. Category B is a significant potential for collision. These are not “close calls” in a casual sense - they are events where the only thing that didn’t happen was the thing that could have. The Austin, JFK, and Sarasota events fall into these top categories.

Why This Matters for General Aviation Pilots

The near-misses that made national news involved commercial airliners, but the problem is not confined to airline operations.

Runway incursions occur at general aviation airports at a rate that rarely draws headlines, because the aircraft are smaller and the traffic less dense. But the physics are identical. A Cessna 172 crossing a runway in front of a turboprop on short final is not in a better position by virtue of its weight - the margin for error is actually tighter, because lighter aircraft have less energy to maneuver and less structural protection if that margin runs out.

FAA runway safety program data shows that pilot deviations - entering or crossing a runway without a clearance - account for the majority of incursions across all airport categories. A significant portion involve general aviation pilots, not due to lack of discipline, but because the population is large and surface operations training is often less rigorous than airborne training.

At non-towered airports - where there is no ground control, no ASDE-X, and no Runway Status Lights - the discipline has to be entirely internal. CTAF calls and self-announce procedures are the only shared infrastructure. That places the entire burden of runway safety on pilot habit and situational awareness.

What the Runway Status Lights System Does - And What It Doesn’t

Where the Runway Status Lights (RWSL) system is installed, it displays a red light at the hold short line whenever the runway is active. Red means stop, independent of any ATC clearance. The system is designed as a last line of defense, not a replacement for proper procedure.

At most airports in the U.S., RWSL is not installed. At those airports, process and judgment are the only safeguards.

Pilot Actions That Reduce Incursion Risk

Read back surface clearances completely. Not just the runway designator - the full instruction. The readback creates a closed loop between pilot and controller. If there’s a mismatch in what was said versus what was heard, that exchange is where the error gets caught before it becomes an incursion.

Look before you cross. In a busy cockpit at an unfamiliar airport, the instinct to begin rolling on clearance is strong. Pause. Look left. Look right. Confirm the runway is clear. Then go.

Slow down at night, in low visibility, and at unfamiliar airports. Request progressive taxi instructions if needed. Controllers prefer answering a position question to filing an incident report.

If you’re unsure of your position on the surface, stop and say so. That transmission is not an embarrassment. It is the correct call.

If you’ve made an error, report it. The Aviation Safety Reporting System (ASRS) - the NASA reporting system - offers meaningful immunity protections. The data submitted helps the system identify where failure points cluster. The Aviation Safety Action Program (ASAP) exists because aviation recognized that a pilot who conceals an error is more dangerous than one who reports it.

What Happens Next With the Bill

Clearing the Senate Commerce Committee is a meaningful step, and bipartisan support at the committee level is not trivial. But the path from committee markup to signed legislation is long, and runway safety bills have been introduced in prior sessions without reaching the floor for a vote.

The bill will need to move to the full Senate and require a companion House bill to advance. The industry and the NTSB - which has included runway incursion prevention on its Most Wanted List of Transportation Safety Improvements through multiple cycles - will be watching that process closely.

The NTSB’s Most Wanted List is not a wish list. It documents patterns of preventable events that repeat. The Austin and JFK incidents are now case studies on that list. When the agency publishes that list, it is signaling that systemic change - not individual incident investigation - is required.

Key Takeaways

The Senate Commerce Committee cleared a bipartisan runway safety bill directing the FAA to expand surface detection technology and strengthen surface operations training.
Three Category A/B runway incursion events occurred in early 2023 - at Austin-Bergstrom, JFK, and Sarasota-Bradenton - within weeks of each other, demonstrating that the problem is systemic.
Pilot deviations (entering or crossing a runway without clearance) account for the majority of incursions across all airport types, including general aviation.
Technology like ASDE-X and Runway Status Lights provides a last line of defense - but most airports don’t have it, and no system substitutes for readback discipline and a deliberate pre-crossing scan.
At non-towered airports, runway safety is entirely pilot-driven. Make position calls, listen for traffic, and verify the runway is clear before every crossing - every time, not most of the time.