Air traffic control error nearly causes Southwest midair collision at Nashville

A Controller Error Put Two Aircraft on a Collision Course

An air traffic control error at Nashville International Airport nearly caused a midair collision involving a Southwest Airlines Boeing 737. The incident, now under investigation by the National Transportation Safety Board (NTSB), occurred when a controller instruction placed the 737 on a converging path with another aircraft, breaking separation well below FAA minimums. The conflict was resolved only after the aircraft had closed to a dangerously short distance, with the Traffic Collision Avoidance System (TCAS) likely alerting the flight crew before a catastrophe unfolded.

What Happened Over Nashville?

The Southwest 737 was operating in the Nashville terminal area when a conflict developed with another aircraft. The root cause was not mechanical failure or pilot error — it was an ATC instruction that put two aircraft on converging paths.

Corrective action was taken, but only after separation had deteriorated to a point that should never occur under controlled conditions. TCAS — the last electronic safety net before see-and-avoid — appears to have played a critical role. When a controller issues a bad vector or altitude assignment, that system exists precisely because the layers before it sometimes fail.

Why Staffing Shortages Make This Worse

This incident didn’t happen in a vacuum. The FAA has been dealing with controller staffing shortages for years, and Nashville is one of the fastest-growing airports in the country. Passenger traffic has surged, and the human infrastructure — controllers in the tower and TRACON — has been under intense pressure to keep pace.

When controllers work longer shifts, cover more positions, and manage heavier traffic loads, the probability of error increases. That’s not opinion — that’s fatigue science.

The pipeline to replace controllers is slow. It takes 18 months to three years to fully certify a controller at a busy facility. Trainees don’t walk out of the FAA Academy in Oklahoma City and start working Class Bravo arrivals the next week. There’s facility-specific training and certification on each position. While hiring numbers are improving on paper, the experienced controller shortage at high-density facilities won’t resolve quickly.

What Pilots Should Do Differently

Maintain your own situational awareness, even under radar vectors. If a controller gives you a heading and something feels wrong — if you see traffic on ADS-B that doesn’t match what you’ve been told — speak up. You are not just allowed to question a clearance. You are expected to. The Aeronautical Information Manual makes clear that the pilot in command has final authority for safe operation of the aircraft under FAR 91.3.

A simple call — “Confirm heading 270? We’re showing traffic at our eleven o’clock” — could prevent a disaster.

Use ADS-B In actively. Whether panel-mounted or a portable receiver feeding a tablet, don’t let traffic targets passively populate your screen. Scan that display the same way you scan outside the windshield. In terminal airspace, where closure rates are high, that electronic traffic picture is essential.

Treat TCAS resolution advisories as commands, not suggestions. Airline crews train to follow TCAS RAs immediately, even when they contradict ATC instructions. That protocol exists because of the 2002 Überlingen midair collision over Germany, where a crew followed ATC instead of their TCAS RA, contributing to a catastrophic outcome. For GA pilots without TCAS, this reinforces why ADS-B traffic awareness and ATC advisories are your primary electronic defense.

Nashville Is Part of a Broader Trend

This is not an isolated event. Over the past several years, the FAA and NTSB have flagged a concerning trend in runway incursions and near-midair collisions across the national airspace system. Notable incidents have occurred at Austin-Bergstrom, JFK, and numerous smaller airports documented in the Aviation Safety Reporting System (ASRS) database.

The NTSB placed reducing runway incursion and ground collision risk on its Most Wanted List of safety improvements — a clear signal that this is a systemic issue, not a single-facility problem.

The FAA responded with a safety summit involving airlines, controllers, airport operators, and pilot groups. Outcomes included enhanced runway safety training, improved surface detection technology at major airports, and revised procedures for high-risk configurations. But progress is incremental, and traffic continues to grow.

Flying Into Nashville: What You Need to Know

Nashville sits under Class Charlie airspace with a demanding traffic mix: airline operations, corporate jets, military flights from the Tennessee Air National Guard, and general aviation. Approach corridors get congested during peak pushes.

VFR pilots should be certain they understand the airspace boundaries, have current ATIS information, and are ready to comply with instructions quickly. IFR pilots should not assume that being on a clearance means all surrounding traffic has been accounted for. Keep scanning.

The Right Way to Think About These Incidents

Incidents like this generate discussion about blame — controller fault, pilot responsibility, systemic failure. The more productive approach is the one aviation safety culture was built on: analyze failures honestly, without assigning punishment as the primary goal.

The NASA ASRS exists to encourage honest reporting without fear of retribution. The NTSB investigates to find causes, not fault. That culture of open, non-punitive analysis is one of the core reasons aviation maintains its safety record. When people stop reporting because they fear consequences, accident rates climb.

Key Takeaways

An ATC error at Nashville put a Southwest 737 on a collision course with another aircraft, with TCAS likely providing the last line of electronic defense
FAA controller staffing shortages are a systemic safety factor — Nashville’s rapid growth has outpaced the human infrastructure needed to manage it safely
Controlled airspace is a layer of protection, not a guarantee — pilots must maintain independent situational awareness even when being radar-vectored
Always question a clearance that doesn’t seem right — PIC authority under FAR 91.3 doesn’t disappear when you check in with approach control
Use ADS-B In traffic displays actively, scanning them with the same discipline you apply to looking outside the windshield