Two Southwest Airlines planes came within roughly 500 feet of each other over Nashville International Airport on Saturday evening after an air traffic controller directed one of the jets into the path of the other, federal officials said. The Federal Aviation Administration confirmed it is investigating the incident, which unfolded around 5:30 p.m. amid gusty winds and ended without injuries only because pilots on both aircraft responded to their most urgent cockpit collision alarms.
The close call involved Southwest Flight 507, which was on approach to land, and Southwest Flight 1152, which was departing from a parallel runway. Both planes carried passengers. Neither Southwest nor the FAA has disclosed how many people were aboard.
What makes this incident stand out is not the weather or a mechanical failure. It is the FAA's own acknowledgment that controller instructions put the two aircraft on a collision course, and that only onboard safety systems and fast-acting pilots prevented a catastrophe.
Southwest said Flight 507's pilots were attempting to land at Nashville International when gusty conditions forced them to execute what the airline called "a precautionary go-around", a standard maneuver in which a plane aborts its landing and climbs back to altitude for another attempt. Go-arounds happen routinely at busy airports and are not, by themselves, dangerous.
What happened next was not routine. ABC News reported that during the go-around, Flight 507 "received instructions from air traffic control" that sent it directly into the path of Flight 1152, which was taking off from a parallel runway. The FAA confirmed that sequence in its own statement.
Both cockpit crews received onboard collision-avoidance alerts, the automated warnings that modern airliners carry as a last line of defense against midair collisions. The Associated Press reported that one aircraft climbed while the other descended to avoid contact. FlightRadar24 tracking data showed the two planes closed to within approximately 500 feet vertically at their nearest point.
Five hundred feet sounds like a comfortable margin to a person standing on the ground. At jet speeds, it is not. That distance can vanish in seconds.
Steve Ganyard, a retired Marine colonel and ABC News contributor, described the severity of the alarm the pilots heard:
"There are multiple alarms that can go off in the cockpit. In this case, it was the most serious of those alarms, telling those pilots, you're on a collision course, you need to move the airplane now."
Flight 507 eventually landed without further incident. Flight 1152 continued on to its destination. Fox News reported that Flight 1152 was headed to Knoxville and that no injuries occurred on either plane.
The FAA's statement left little ambiguity about where the breakdown occurred. The agency said the pilot of Flight 507 "received instructions from air traffic control that put the flight in the path of another airplane that was departing from a parallel runway." Both flight crews, the FAA added, "responded to onboard alerts."
That language places the error squarely on the controller side, not on the flight deck. The pilots followed instructions. The instructions were wrong.
The agency has not yet said whether the controller involved has been reassigned, what specific heading or altitude instructions were given, or whether staffing levels at Nashville's tower played any role. Those are questions the investigation will need to answer.
Incidents like this one raise familiar concerns about the state of America's air traffic control workforce. Controller shortages and fatigue have been recurring themes in aviation safety discussions for years. A recent staffing report at LaGuardia raised hard questions about whether controller workload is contributing to dangerous outcomes at major airports.
The Washington Times noted that audio and flight data indicate both crews received collision-avoidance alarms, with one plane climbing and the other descending, the textbook response when the Traffic Collision Avoidance System, or TCAS, issues a resolution advisory. That system exists precisely because human controllers sometimes make mistakes. On Saturday, it did its job.
The FAA has not disclosed whether the 500-foot separation figure meets its formal threshold for a "near midair collision," though the New York Post reported that the proximity could qualify under that definition. If it does, the incident would be classified at the most serious end of the FAA's close-call scale.
Southwest Airlines issued a brief statement after the incident. Spokesperson Lynn Lunsford said:
"Southwest appreciates the professionalism of its Pilots and Flight Crews in responding to the event. Nothing is more important to Southwest than the Safety of our Customers and Employees."
The airline confirmed the go-around and the safe landing but offered no additional detail about what its crews experienced in the cockpit or what communications they had with the tower. That reticence is standard during an active FAA investigation, but it also means the public is left to piece together what happened from tracking data and federal statements.
The incident is the latest in a string of unsettling near misses and procedural breakdowns at American airports. In one recent case, an American Airlines pilot had to brake hard to avoid a truck on a Charlotte taxiway, highlighting ground-safety failures that persist despite years of warnings.
Communication errors have also surfaced as a recurring problem. Earlier this year, Republic Airways pilots contacted JFK tower by mistake while landing at LaGuardia, a mix-up that underscored how thin the margin for error can be in congested airspace.
The FAA has opened its investigation, but key facts are still missing. The agency has not identified the specific runways involved, the aircraft types operating as Flights 507 and 1152, or the exact air traffic control instructions that sent the planes toward each other. Passenger and crew counts remain undisclosed.
Perhaps most importantly, the FAA has not said whether the controller's error was an isolated lapse or part of a broader pattern at Nashville International. That distinction matters. An isolated mistake is one thing. A systemic problem, driven by staffing shortages, fatigue, outdated procedures, or inadequate training, is something far more dangerous.
The horizontal distance between the two planes at their closest point has also not been released. Vertical separation of 500 feet tells only part of the story. If the jets were also close laterally, the margin was even thinner than the headline number suggests.
For now, the traveling public is left with a familiar reassurance: the system worked because the backup system caught the failure. Onboard collision-avoidance technology saved the day after the humans in the tower put two planes on a path toward each other.
That is not a system working. That is a system failing and being rescued by its last safety net.
Every passenger who boards a commercial flight trusts that air traffic control will keep planes apart. When that trust is broken, and the only thing standing between routine travel and disaster is an automated alarm, the FAA owes the public more than an investigation notice. It owes answers, and it owes them fast.
