Two Southwest Airlines Boeing 737s loaded with passengers were seconds from a potential midair collision over Nashville on April 18, 2026, after an air traffic controller mistakenly directed one jet into the path of the other. Cockpit alarms blared aboard both planes. Pilots on Southwest Flight 507 and Southwest Flight 1152 broke away from their assigned courses to avoid each other, and both aircraft landed safely at Nashville International Airport with no injuries reported.
The incident, which unfolded during the evening arrival rush around 5:30 p.m. Central time, has prompted a federal review and renewed questions about whether one of the country’s fastest-growing airports has the controller staffing to match its surging traffic.
How the conflict developed
Both flights were inbound to Nashville International when a controller issued an instruction that placed one aircraft on a converging course with the other. Within moments, cockpit collision-avoidance alerts activated aboard both 737s. The aircraft are equipped with the Traffic Collision Avoidance System, known as TCAS, which is designed to generate climb-or-descend commands when it detects a closing threat. Initial reporting indicates the crews took evasive action consistent with TCAS resolution advisories, though whether the maneuvers were prompted solely by the automated system, by visual sighting of the other jet, or by a corrected tower instruction has not been confirmed.
The Federal Aviation Administration defines a near midair collision as any encounter in which aircraft pass within 500 feet of each other or in which a pilot reports a collision hazard, according to the agency’s Aeronautical Information Manual. The cockpit alarm activations and the evasive maneuvers described in initial reporting strongly suggest the Nashville encounter met at least one of those thresholds, though exact separation distances have not been confirmed by radar data or an official preliminary report.
Both flights continued to safe landings. Passengers reported no injuries, and neither aircraft showed signs of structural damage. But the absence of physical harm does not reduce the regulatory seriousness of the event. Under FAA protocols, any conflict that forces pilots into abrupt evasive action because of a controller error triggers a mandatory review.
What the FAA and Southwest have said
The FAA acknowledged the incident and confirmed it is under review but has not released a detailed timeline of the controller’s transmissions or the radar track data showing how close the two jets came. The agency has not provided any on-the-record quotes about the specifics of the encounter; its public statements have been limited to confirming that the matter was referred for investigation, consistent with standard procedure for potential near midair collisions.
Southwest Airlines has not issued a detailed public statement about the encounter. The airline’s standard protocol in such cases is to cooperate with FAA and National Transportation Safety Board investigators while conducting its own internal safety review. As of late April 2026, neither the pilots of Flight 507 nor those of Flight 1152 have spoken publicly about the event.
The NTSB has not yet published a preliminary report. Pilot accounts, when they become available through NTSB interviews or through NASA’s confidential Aviation Safety Reporting System, often add critical detail about how quickly a conflict developed and how much reaction time crews had.
Nashville’s rapid growth and ATC workload
Nashville International Airport has experienced a dramatic rise in passenger traffic over the past decade. The airport handled more than 23 million passengers in 2024, a figure that has roughly doubled since 2014, according to data published by the Metropolitan Nashville Airport Authority. That growth has brought more flights, tighter spacing on approach, and heavier workloads for the controllers managing arrivals and departures.
The National Air Traffic Controllers Association, the union representing most FAA controllers, has warned for years that staffing has not kept pace with traffic increases at airports across the country. A 2024 NATCA report found that roughly three-quarters of FAA air traffic facilities were operating below the agency’s own staffing targets. Whether Nashville’s tower was short-staffed on the evening of April 18 has not been confirmed, and any direct link between staffing levels and the controller’s erroneous instruction remains unestablished.
Still, the pattern is familiar. Investigations into ATC-related close calls at other busy hubs, including incidents at Austin-Bergstrom, JFK, and Honolulu in recent years, have repeatedly uncovered gaps in staffing, training, and procedural safeguards. Each case turned on a specific mix of local traffic patterns and facility conditions, but the recurring theme of controllers stretched thin has become difficult to dismiss.
What investigators will examine
Several key questions remain open. Investigators will want to determine the precise closest point of approach between the two 737s. They will review the controller’s transmissions, including whether the erroneous instruction resulted from a misheard callsign, a momentary lapse in situational awareness, or confusion over runway assignments. Nashville’s airspace configuration, with its mix of parallel runway operations, intersecting arrival flows, and a blend of airline, cargo, and general aviation traffic, can complicate a controller’s mental model of where each aircraft is headed.
Audio recordings from the tower frequency, if released through LiveATC or obtained by investigators, would allow a second-by-second reconstruction of the clearances and readbacks that preceded the conflict. As of this writing, no such recordings have been independently verified and published.
The FAA’s formal classification of the event also matters. If the agency categorizes it as a confirmed near midair collision rather than a lesser “loss of standard separation,” the incident will carry greater weight in safety databases and could influence future staffing and procedural decisions at Nashville and similar high-growth airports.
Why near-misses demand scrutiny even when no one is hurt
Aviation safety professionals often describe near midair collisions as the most important accidents that never happened. The system worked on April 18 because the cockpit technology performed as designed and because two flight crews reacted quickly under pressure. But the margin between a successful evasion and a catastrophe can be measured in seconds and hundreds of feet.
The controller’s mistaken instruction is not in dispute. The pilots’ successful response is a matter of record. What remains to be determined is whether this was an isolated lapse in an otherwise sound operation or a warning sign of deeper strain at a facility managing rapid growth with finite resources. Until the FAA and NTSB release their findings, the Nashville incident stands as a stark reminder that the safety net protecting commercial aviation depends on every link in the chain, and that when one link fails, the margin for recovery is razor-thin.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
