Uncategorized

Southwest 737s nearly collide at Nashville after ATC error, missing separation by 500 feet

Air traffic control at Nashville International Airport directed a Southwest Airlines flight performing a go-around into the departure path of another Southwest jet on April 18, 2026, triggering cockpit collision warnings in both aircraft. The two Boeing 737s passed within approximately 500 feet vertically — half the FAA’s minimum separation standard — before onboard systems and crew intervention prevented a mid-air collision. Flight WN-507 from Myrtle Beach and Flight WN-1152 departing for Knoxville both received TCAS resolution advisories commanding evasive maneuvers.

The FAA classifies vertical separation below 1,000 feet as a serious near mid-air collision, triggering mandatory investigation. Southwest operates over 200 daily flights at Nashville, where the incident occurred on parallel runways during gusty wind conditions.

Controller error puts two jets on collision course

Flight WN-507 was landing on runway 2L when gusty winds forced the crew to abort and go around. The Nashville tower controller instructed the aircraft to turn right and maintain an altitude — a directive that placed it directly in the path of WN-1152, which was departing from parallel runway 2R just to the east.

The controller attempted to correct the conflict by ordering WN-507 to climb while instructing WN-1152 to hold at a lower altitude. WN-1152 responded that it had already passed that altitude. The controller then reversed the instruction, telling WN-507 to descend back down.

Both cockpits received TCAS resolution advisories — automated collision warnings that override controller instructions and command immediate evasive action. The crews complied, and the aircraft passed with vertical separation of around 500 feet, confirmed by ADS-B tracking data.

The FAA requires 1,000 feet of vertical separation for aircraft below 10,000 feet altitude. This incident fell 500 feet short of that standard — a breach that qualifies as a Level 1 near mid-air collision under FAA air traffic control procedures.

Nashville near-miss incident details, April 18, 2026
Flight Route Runway Action taken
WN-507 Myrtle Beach to Nashville 2L (landing) Go-around, TCAS descent
WN-1152 Nashville to Knoxville 2R (departure) TCAS climb advisory
Separation Approximately 500 feet Both runways FAA minimum: 1,000 feet

How Nashville tower operates under FAA oversight

The FAA certifies and oversees all US air traffic control facilities, including the Nashville tower. Controllers undergo annual ramp inspections and quarterly safety audits under FAA Order 1100.161, which establishes operational standards for separation minima and conflict resolution.

When vertical separation falls below the required 1,000 feet, the FAA classifies the event as a near mid-air collision and mandates reporting to the Aviation Safety Reporting System database. The NTSB investigates incidents where aircraft come within 500 feet of each other, as occurred here.

Southwest Airlines operates Nashville as a focus city, accounting for roughly 60 percent of the airport’s traffic with over 200 daily flights. American Airlines and Delta Air Lines maintain secondary operations with hub feed from Dallas/Fort Worth and Atlanta respectively.

The FAA has documented multiple near mid-air collisions at Nashville tower in recent years, including a 2024 incident involving a Southwest 737 go-around that conflicted with a departing regional jet at 700 feet separation. That event prompted an FAA operational review but resulted in no suspensions — Southwest resumed normal operations within 24 hours.

What to do if you have a Nashville flight booked

The FAA investigation may result in temporary operational changes at Nashville’s parallel runways, particularly during gusty wind conditions when go-arounds become more frequent.

  • Monitor flight status starting two hours before departure via southwest.com or the airline’s mobile app — look specifically for go-around notifications or altitude hold instructions that may add 10–30 minutes to your arrival time.
  • Check real-time radar at flightaware.com/live/airport/KBNA to see if Nashville tower is issuing multiple go-arounds on runways 2L and 2R — a pattern that signals heightened ATC scrutiny and potential delays.
  • Build connection buffers if you’re connecting through Nashville in the next two weeks — the FAA typically issues operational guidance within 72 hours of a serious near mid-air collision, which may temporarily increase spacing between departures and arrivals.
  • Track the NTSB docket at ntsb.gov if you’re a frequent Nashville traveler — the preliminary report, expected within 30 days, will reveal whether controller error triggers broader procedural changes at the tower.

Watch: The FAA Safety Alert for Controllers, expected by April 23, will indicate whether Nashville implements immediate go-around protocol changes affecting Southwest operations.

What is TCAS and how did it prevent a collision?

TCAS (Traffic Collision Avoidance System) is an onboard system that monitors nearby aircraft and issues resolution advisories when a collision risk is detected. In this incident, TCAS commanded one crew to climb and the other to descend, overriding the controller’s instructions and creating the 500 feet of separation that prevented a mid-air collision.

Will this incident affect Southwest operations at Nashville?

No cancellations have been announced, but the FAA investigation may result in temporary holds or additional spacing requirements on runways 2L and 2R, particularly during gusty wind conditions. Travelers should monitor flight status for potential 10–30 minute delays over the next two weeks as the FAA reviews tower procedures.

How common are near mid-air collisions at US airports?

The FAA investigates dozens of near mid-air collisions annually, though most involve general aviation rather than commercial jets. Nashville tower has documented multiple incidents in recent years, including a 2024 event with 700 feet of separation. The 500-foot separation in this case qualifies as a serious Level 1 event requiring mandatory NTSB investigation.

What happens to the air traffic controller involved?

The FAA will review the controller’s actions as part of its investigation. Depending on findings, outcomes range from additional training to temporary reassignment. The agency prioritizes systemic fixes over individual discipline, focusing on procedural changes that prevent recurrence across the national airspace system.

Related Articles

Back to top button