Nashville International Airport officials confirmed on April 21, 2026, that a Federal Aviation Administration probe is underway after two Southwest Airlines jets nearly collided during a botched landing sequence. Southwest Flight 507 was attempting to land Saturday evening when gusty winds forced the pilots to execute a go-around maneuver. Air traffic controllers in the Nashville tower then issued instructions that steered the climbing aircraft directly into the departure path of Southwest Flight 1152. Both aircraft were Boeing 737 models, which constitute the entirety of the Southwest Airlines short-haul fleet.
Preliminary reports indicate the conflict occurred at approximately 5:30 p.m. local time on Saturday. Seconds separated the two aircraft from a potential catastrophe. Data from flight tracking software shows the two jets converged within hundreds of feet before pilots took evasive action.
Nashville Controller Error Details
Flight 507 initiated its climb from the runway threshold just as Flight 1152 received clearance to begin its takeoff roll on a parallel strip. Controllers failed to maintain vertical or lateral separation between the two planes as the arriving jet crossed into the departure corridor. This specific lapse in oversight forced both flight crews to rely on their primary cockpit safety instruments. Pilots on both flight decks received Traffic Collision Avoidance System alerts, which provide automated resolution advisories to prevent midair collisions.
These systems operate independently of ground-based radar and serve as a final layer of protection when human oversight fails. The Federal Aviation Administration noted that the information is preliminary and subject to change as the investigation continues. Radar logs show Flight 507 was climbing through 1,500 feet when the proximity warning triggered. Discrepancies between air traffic control recordings and pilot statements are currently the primary focus of federal investigators. One investigator noted that the instructions given to Flight 507 appeared to contradict standard separation protocols for parallel runway operations at Nashville International Airport.
Technical reviews of the incident suggest the controller may have misjudged the rate of climb for Flight 507 during the go-around. Wind gusts at the time were clocked at 28 miles per hour, complicating the aerodynamic profile of the aircraft. Pilots must manage engine thrust and flap settings carefully during a missed approach to avoid stalling or overshooting their designated altitude. Flight 507 followed the standard instrument departure path until the tower intervened with a manual heading change. Conflict detection software in the tower should have alerted the ground crew to the intersecting paths, yet the manual override took precedence.
Documentation from the National Air Traffic Controllers Association highlights the increasing complexity of managing dual-runway operations during inclement weather. Nashville handles over 500 daily operations, making it one of the busiest secondary hubs in the Southeastern United States.
Southwest Flight Crew Safety Responses
Crew members for Flight 507 eventually landed the plane without further incident in Nashville. Passengers on Flight 1152 reached their destination in Knoxville, Tennessee, unaware of the narrow margin of safety they had just navigated. Professionalism among the pilots likely prevented a tragedy that the current air traffic control infrastructure could not stop. Southwest described the maneuver as precautionary and said the pilots were responding to weather conditions at the time. Flight data recorders will reveal the exact timing of the pilot inputs relative to the automated alerts. Standard operating procedures require pilots to prioritize automated resolution advisories over verbal instructions from the tower when a collision is imminent.
"While on approach during gusty winds at Nashville International Airport, the pilots of Southwest Flight 507 executed a precautionary go-around," Southwest Airlines said in a statement.
Safety persists as a metric of pilot reaction time in these high-pressure scenarios. Pilots are trained to treat every go-around as a critical phase of flight requiring total focus. Wind shear at lower altitudes often requires these sudden climbs to ensure the aircraft remains within a safe operating envelope. Southwest Flight 1152 was already at rotation speed when the conflict became apparent on the flight deck. Cockpit voice recorders will capture the communication between the captain and the first officer during the critical ten-second window. Ground crews at Nashville reported no unusual mechanical issues with either aircraft following the event.
Federal officials have grounded the controller involved in the incident pending a full psychological and performance review. Southwest Airlines is cooperating with the FAA but insists its pilots followed every regulation during the emergency climb.
Federal Aviation Administration Safety Standards
Staffing shortages in towers across the United States have forced controllers to work extended shifts, leading to documented cases of fatigue. Nashville International Airport has seen a rapid increase in traffic volume, straining the local control infrastructure. Records show a UPS plane recently aborted a landing at the same airport to avoid a similar conflict. Current safety audits suggest that the rapid growth of secondary hubs like Nashville outpaces the implementation of modern radar upgrades. Budgetary constraints within the Department of Transportation often delay the rollout of NextGen tracking technology. Systemic failures in communication protocols often precede these physical near-misses.
Investigators are now reviewing the transcript of the Saturday exchange to determine if the controller was distracted or overwhelmed by the traffic load. FAA safety inspectors arrived in Tennessee on Monday to begin interviewing the tower staff and the four pilots involved. The agency has launched a broader inquiry into the runway configuration at Nashville following this second major close call in six months.
National aviation records indicate that near-misses have increased by 12 percent over the last decade. Modern jetliners are equipped with sophisticated electronics, yet the human element in the control tower remains the most vulnerable point in the chain. Southwest Airlines maintains a rigorous training program for its 737 crews, emphasizing the importance of the go-around maneuver. Internal company memos suggest that pilots are encouraged to abort landings whenever a stable approach cannot be maintained. This culture of safety was put to the test when the tower directed Flight 507 into the path of an accelerating jet.
Aviation experts believe the integration of more automated ground-control systems could reduce the frequency of such errors. Current FAA regulations rely heavily on verbal hand-offs between different sectors of the airport environment. Each hand-off presents an opportunity for a miscommunication that can lead to a loss of separation.
The Elite Tribune Strategic Analysis
How many near-misses must occur before the Department of Transportation admits the American air traffic control system is structurally broken? The evidence shows a slow-motion collapse of safety standards driven by a desperate need to maintain high-frequency flight schedules in understaffed towers. The FAA continues to treat these incidents as isolated human errors when they are clearly symptoms of a systemic failure. Nashville is no longer a sleepy regional strip, yet it is being managed with outdated protocols that cannot handle the density of a modern Southwest hub.
Relying on TCAS to save hundreds of lives in the final seconds is not a safety strategy; it is a failure of governance. Pilots are doing the job that the ground infrastructure is failing to provide, acting as the last line of defense against bureaucratic inertia and staffing deficits. If the federal government does not fast-track radar modernization and controller recruitment, a midair collision over a major US city is an inevitability. The industry prioritizes throughput over the razor-thin margins of error that currently define our skies.
It is time to stop celebrating the miracle of TCAS and start questioning why it was needed in the first place.