Southwest 507 at Nashville: how a go-around put two Southwest jets into a TCAS alert
A Southwest 737 MAX went around off runway 2L just as another Southwest 737 lifted off the parallel runway 2R. The tower turned the go-around right, across the departure's climb, and both crews ended up following their collision-avoidance systems. Work it from the tower's side, decode the radio as it happens, and make the calls yourself.
What happened
On Saturday, April 18, 2026, at about 5:37 p.m. local time, Southwest 507, a Boeing 737 MAX 8 arriving from Myrtle Beach, went around from runway 2L at Nashville in gusty winds while Southwest 1152, a Boeing 737 bound for Knoxville, was taking off from the parallel runway 2R. Nashville Tower turned 507 right to heading 110, across 1152's climb. Both crews reported responding to TCAS resolution advisories, and by our reading of the ADS-B data 507 passed about 530 feet beneath 1152, almost directly under it. The FAA said the tower's instructions put 507 in the departing jet's path and that it is investigating. Both flights landed normally.
| Date and time | Sat 18 Apr 2026, 22:37Z (5:37 p.m. CDT) |
|---|---|
| Airport | Nashville International (BNA), north flow, wind 330° at 19 kt gusting 24 (tower) |
| Aircraft 1 | Southwest 507 (SWA507), Boeing 737 MAX 8, Myrtle Beach to Nashville, ILS runway 2L, went around |
| Aircraft 2 | Southwest 1152 (SWA1152), Boeing 737-700, Nashville to Knoxville, departing runway 2R |
| Closest point | About 0.03 nm (170 ft) apart horizontally and 530 ft vertically at 22:37:32Z, around 1,750 to 2,300 ft (our ADS-B analysis). No official figure published. |
| Controller | Nashville Tower (BNA ATCT) |
| Outcome | Both crews reported TCAS RAs; no injuries reported; FAA investigating |
How Nashville runs its parallel runways
It's a gusty Saturday evening and Nashville is in north flow: everyone lands and takes off toward the north-northeast. BNA has three parallel runways, 2L, 2C and 2R. Right now the tower is landing on 2L, the west runway, and launching off 2R, the east one, a little under a mile apart.
Southwest 507 is on the ILS to 2L, about two and a half miles out. Southwest 1152 has been told to line up and wait on 2R. The wind is 330 at 19 knots, gusting 24, so it's coming from well left of the runway.
A tower can roll a departure off one parallel while a jet is on final to the other, as long as the departure's path splits at least 30 degrees from the arrival's missed approach path. If the arrival goes around, the two head different ways.
"Southwest 1152, RNAV to SHWIT, runway 2R, cleared for takeoff."
You're cleared to go. Fly your published departure toward SHWIT.
At this moment 507 is just short of runway 2L, on the last few seconds of its approach. The dashed lines show each jet's path: 507 straight down 2L, and the departure route 1152 will fly, which bends right a couple of miles out.
What is a go-around?
A go-around is a landing that's called off: full power, nose up, climb away and try again. It is a normal, trained maneuver. Southwest later said 507's crew made a precautionary go-around in the gusty wind.
The ADS-B data shows 507 at its lowest at 22:36:22Z, over the first part of runway 2L, then climbing away. By 22:36:32Z, 1152 is rolling down 2R beside it.
The published recording doesn't include 507's go-around call. The first thing we hear is the tower's reply.
"Southwest 507, maintain 2,000."
Level off at 2,000 feet.
"2,000, Southwest 507."
Two Southwest 737s are now climbing side by side, 507 over 2L at about 1,000 feet and 1152 just off 2R. That's expected. The question is where each one turns next.
- SWA507
- Callsign
- 010
- Altitude in hundreds of feet: 1,000 ft
- 15
- Ground speed in tens of knots: about 150 kt
- B38M
- Aircraft type: Boeing 737 MAX 8
Where it went wrong: "turn right heading 110"
"Southwest 507, turn right heading 1-1-0."
Turn right until you're pointed east-southeast.
"Right turn heading 1-1-0, Southwest 507."
Look at where heading 110 points from runway 2L: right, toward 2R's side of the field.
Southwest 507 is starting its right turn. Which jet is now in its way? Tap it on the scope or pick below.
The lines sticking out of each target show where it'll be in one minute. Watch where they meet.
In the FAA's procedure data, a missed approach from the ILS to 2L climbs straight ahead to 1,200 feet, then turns left to heading 240, away from 2R. That's the 30-degree split the parallel departures rely on.
507 turns right from 22:36:54Z, through north-east at 22:37:10Z, and is pointed east by 22:37:31Z, holding 1,900 to 1,950 feet until 22:37:26Z. Over the same half minute 1152 climbs from 700 to 2,200 feet and starts its own planned right turn. Their paths now cross.
"Southwest 507, climb and maintain 3,000."
Keep climbing, up to 3,000.
"Southwest 1152, maintain 2,000."
Stop your climb at 2,000.
"2,000, we're already past it, Southwest 1152."
Too late, we're already above 2,000.
The idea was to stack them: 507 on top at 3,000, 1152 underneath at 2,000. But 1152 had climbed through 2,000 at about 22:37:16Z. Now the plan points the two jets toward the same altitude, one climbing up into the other.
1152 is above 2,000 and climbing. 507 is at about 1,900, turning across its path. They're about half a mile apart and closing. What do you say?
"He's already in the turn. Southwest 507, descend and maintain 2,000."
Change of plan: don't climb, go back down to 2,000.
"Down to 2,000, Southwest 507."
What is a TCAS resolution advisory?
TCAS is the system on airliners that talks to nearby transponders. When two equipped jets close in, it coordinates between them and gives each crew a vertical order: climb for one, descend for the other. That order is a resolution advisory, or RA.
Pilots follow an RA immediately, even if it breaks an ATC clearance, and tell the controller as soon as they can. From then on the controller must not give instructions that fight it.
How close did the planes get?
By our analysis of the Flightradar24 ADS-B data, 507 passed almost directly under 1152 at 22:37:32Z: about 0.03 nm (170 feet) apart sideways and about 530 feet apart vertically, 507 near 1,750 feet and descending, 1152 near 2,300 feet and climbing.
The Aviation Herald, working from ADS-B too, reported about 400 feet and under 0.08 nm at 22:37:31Z, and news reports cited about 500 feet. The FAA has not published a number.
Once two IFR jets are airborne in the terminal area, controllers keep them at least 3 miles apart sideways or 1,000 feet vertically, unless another form of separation applies. Here they were under half a mile apart for about 15 seconds.
ADS-B reports pressure altitude on a standard setting, in 25-foot steps, so it can differ a little from the cockpit altimeter. The gap between the two jets isn't affected.
"Do you want an altitude, Southwest 1152? Out of the RA."
Our collision alert is over. What altitude do you want us at?
"Southwest 1152, climb, you can climb via the SID."
Carry on with your normal departure climb.
The data agrees with the reports: after the crossing 507 dropped to about 1,550 feet, below the 2,000 it was given, while 1152 kept climbing. One went down, the other up, the way TCAS splits a pair.
"Southwest 507, climb and maintain 4,000."
"4,000, Southwest 507. And we responded to the RA."
Climbing to 4,000. And for the record, we followed a collision alert too.
Who was at fault?
The FAA said 507 "received instructions from air traffic control that put the flight in the path of another airplane" departing a parallel runway, and that both crews responded to onboard alerts. It is investigating. That statement is the official record so far, not a final finding. We had not found an NTSB record of the event when we checked on 17 November 2026.
"Southwest 507, 124.7, correction, 118.4."
Talk to Nashville Approach on 118.4 for another try.
507 was turned south to heading 200 and handed to approach. It landed on its second approach at 22:48Z. 1152 went to departure and landed in Knoxville at 23:06Z. From go-around to closest point took about 70 seconds.
What this one teaches
Three habits a tower controller running parallel runways builds, and why each one mattered here.
Know where the go-around goes
Before clearing a departure off the parallel, picture the arrival going around. Its path and the departure's should split, not meet.
Check the turn before you give it
Heading 110 from 2L points across 2R's climb-out. A glance at both targets before keying up shows who is in the way.
Work with the climb, not against it
A departure climbs fast. Once it's above, send the other jet underneath, and once a crew reports an RA, don't fight it.
Try your hand at air traffic control.
Sit at a real radar position in Southern California, with real runways, real procedures and live traffic, and AI controllers in every other seat. It runs in your browser, free.
- Keep jets 3 miles or 1,000 feet apart
- Climb departures and turn them onto their routes
- Hand them off cleanly to the next controller
Southwest 507 near miss: common questions
How close did Southwest 507 and Southwest 1152 get?
Our analysis of Flightradar24 ADS-B data puts the closest point at 22:37:32Z (5:37 p.m. local), about 2 nm northeast of the airport: about 0.03 nm (170 feet) apart horizontally and about 530 feet vertically, with 507 passing under 1152. The Aviation Herald, also from ADS-B, reported about 400 feet vertically and less than 0.08 nm horizontally at 22:37:31Z. The FAA has not published a figure.
Why did Southwest 507 go around?
Southwest said the crew executed a precautionary go-around in gusty winds. Nashville Tower had just reported the wind as 330 degrees at 19 knots, gusting 24.
Who was at fault?
The FAA said Southwest 507 received instructions from air traffic control that put it in the path of an airplane departing from a parallel runway, and that it is investigating. No final finding of cause had been published when we checked on November 17, 2026.
What is a TCAS resolution advisory?
TCAS is the collision-avoidance system on airliners. When two equipped jets get too close, it tells one crew to climb and the other to descend. Pilots follow the resolution advisory right away, even against an ATC instruction, then tell the controller. Both Southwest crews reported responding to one.
Why did the tower tell 507 to climb and then descend?
The tower first climbed Southwest 507 to 3,000 feet and tried to hold Southwest 1152 at 2,000, but 1152 was already above 2,000. With the departure above and climbing, the controller reversed the plan and told 507 to descend to 2,000 so it would pass underneath.
Was anyone hurt?
No injuries were reported. Southwest 507 was vectored for another approach and landed at Nashville at 22:48Z, and Southwest 1152 continued to Knoxville, per Flightradar24.
Is this the 2024 Nashville runway incident?
No. This was an airborne encounter after a go-around on April 18, 2026. It is a separate event from the 2024 Nashville runway incident involving Alaska Airlines flight 369 and a Southwest jet.
Every word on frequency
Nashville Tower, 22:32:05Z to 22:38:56Z (published recording, with gaps)
| 22:32:05Z | Southwest 507 | Tower, Southwest 507, ILS 2L. |
|---|---|---|
| 22:32:28Z | Nashville Tower | Southwest 507, Nashville Tower, runway 2L, cleared to land, wind 330 at 14. |
| 22:32:40Z | Southwest 507 | Cleared to land 2L, Southwest 507. |
| 22:32:45Z | Nashville Tower | Southwest 2803, right at B3, B, T2 to the ramp. |
| 22:32:56Z | Southwest 2803 | B3, B, T2 to the ramp, Southwest 2803. |
| 22:34:39Z | Nashville Tower | Southwest 715, RNAV to FRNCS, runway 2R, cleared for takeoff. |
| 22:34:43Z | Southwest 715 | RNAV FRNCS, cleared for takeoff 2R, Southwest 715. |
| 22:34:46Z | Nashville Tower | Southwest 606, contact Departure. |
| 22:34:48Z | Southwest 606 | Departure, good day. |
| 22:34:51Z | Nashville Tower | Southwest 1152, Nashville Tower, runway 2R, line up and wait. |
| 22:34:54Z | Southwest 1152 | 2R, line up and wait [rest cut off]. |
| 22:34:55Z | Nashville Tower | Southwest 2718, right at B3, north on B, T2 to the ramp. |
| 22:35:00Z | Southwest 2718 | Right B3, B, T2 to the ramp, Southwest 2718. |
| 22:35:06Z | Nashville Tower | Winds are now 330 at 19, gusts 24. |
| 22:35:58Z | Southwest 558 | Tower, Southwest 558, ILS 2L. |
| 22:36:02Z | Nashville Tower | Southwest 558, Nashville Tower, runway 2L, cleared to land, wind 330 at 19, gusts 24. |
| 22:36:07Z | Southwest 558 | 2L, cleared to land, Southwest 558. |
| 22:36:14Z | Nashville Tower | Southwest 1152, RNAV to SHWIT, runway 2R, cleared for takeoff. |
| 22:36:19Z | Southwest 1152 | [readback not readable] |
| 22:36:32Z | Nashville Tower | Southwest 715, contact Departure. |
| 22:36:35Z | Southwest 715 | Departure, Southwest 715. |
| 22:36:45Z | Nashville Tower | Southwest 507, maintain 2,000. |
| 22:36:49Z | Southwest 507 | 2,000, Southwest 507. |
| 22:36:55Z | Nashville Tower | Southwest 507, turn right heading 110. |
| 22:36:58Z | Southwest 507 | Right turn heading 110, Southwest 507. |
| 22:37:12Z | Nashville Tower | Southwest 507, climb and maintain 3,000. |
| 22:37:14Z | Southwest 507 | 3,000, Southwest 507. |
| 22:37:17Z | Nashville Tower | Southwest 1152, maintain 2,000. |
| 22:37:20Z | Southwest 1152 | 2,000, we're already past it, Southwest 1152. |
| 22:37:24Z | Nashville Tower | He's already in the turn. Southwest 507, descend and maintain 2,000. |
| 22:37:28Z | Southwest 507 | Down to 2,000, Southwest 507. |
| 22:37:31Z | Envoy 3436 | Tower, Envoy 3436, ILS 2L. |
| 22:37:44Z | Envoy 3436 | Nashville Tower, Envoy 3436. |
| 22:37:52Z | Southwest 1152 | Do you want an altitude, Southwest 1152? Out of the RA. |
| 22:37:55Z | Nashville Tower | Southwest 1152, climb, you can climb via the SID. |
| 22:37:57Z | Southwest 1152 | Climb via the SID, Southwest 1152. |
| 22:38:00Z | Nashville Tower | Southwest 507, climb and maintain 4,000. |
| 22:38:02Z | Southwest 507 | 4,000, Southwest 507. And we responded to the RA. |
| 22:38:05Z | Nashville Tower | Thanks. |
| 22:38:09Z | Envoy 3436 | Nashville Tower, Envoy 3436, ILS 2L. |
| 22:38:14Z | Nashville Tower | Southwest 507, turn right heading 1[...], turn right heading 200. |
| 22:38:18Z | Southwest 507 | 200, Southwest 507. |
| 22:38:23Z | Nashville Tower | Envoy 43[...], correction, Envoy 3436, runway 2L, cleared to land. |
| 22:38:27Z | Envoy 3436 | [readback], Envoy 3436. |
| 22:38:32Z | Southwest 1152 | And Southwest 1152, we were originally climbing via the [SID name] Seven. Do you want that or the one on the chart? |
| 22:38:38Z | Nashville Tower | Execjet 359, Nashville Tower, runway 2L, cleared to land. |
| 22:38:45Z | Southwest 1152 | Want us to Departure, Southwest 1152? |
| 22:38:47Z | Nashville Tower | Southwest 1152, Departure. |
| 22:38:51Z | Nashville Tower | Southwest 507, 124.7, correction, 118.4. |
| 22:38:56Z | Southwest 507 | 18.4, Southwest 507. |
Radio audio was recorded by LiveATC.net and published by VASAviation, who trimmed silences, so some time is missing between calls. Times are the radar clock shown in that video. Aircraft positions are ADS-B data from Flightradar24, and the scope above is our own drawing of that data. Transmissions may differ slightly from the audio; anything we couldn't make out is in brackets.
Sources
Incident audio and flight data
- VASAviation: Southwest Planes Near Mid-Air Collision | TCAS Saved Lives Again!!, published April 20, 2026. The Nashville Tower recording (audio from LiveATC.net) used for our transcript and call times. This is a third-party publication of the radio audio, not an FAA report.
- Flightradar24. The replay and closest-approach calculation use ADS-B positions for SWA507 (N8904L) and SWA1152 (N441WN) on April 18, 2026, retrieved from the Flightradar24 API, plus the landing times quoted above. This provider link is not a permanent archive of those tracks; the distances and timing are our analysis, not an official separation finding.
- Associated Press via WTOP: Two Southwest Airlines planes came dangerously close in Nashville, April 20, 2026. The FAA's statement that air traffic control instructions put Southwest 507 in the path of the departing jet, and Southwest's statement.
- The Aviation Herald: Southwest B38M and B738 at Nashville on Apr 18th 2026. Aircraft registrations, the go-around reason given by the airline, and an independent ADS-B estimate of the closest point. The Aviation Herald lists 1152 as a 737-800; Flightradar24 lists N441WN as a 737-700, which we use.
Primary FAA procedure references
- FAA Order JO 7110.65, paragraph 5-8-5: Departures and Arrivals on Parallel or Nonintersecting Diverging Runways. The rule that a departure course must diverge by at least 30 degrees from the missed approach course of an arrival to the parallel runway.
- FAA Order JO 7110.65, paragraph 2-1-28: TCAS Resolution Advisories. What controllers do once a crew reports responding to an RA.
- Aeronautical Information Manual, paragraph 4-4-16: TCAS I and II. How pilots respond to resolution advisories and report them to ATC.
- FAA Order JO 7110.65, paragraph 5-5-4: Minima. The 3-mile radar separation minimum in the terminal area.
- FAA Coded Instrument Flight Procedures (CIFP). The runway threshold positions used on our scope and the ILS 2L missed approach (straight ahead to 1,200 ft, then left to heading 240), checked in the cycles effective February and September 2026.
These FAA links explain procedures; they are not incident investigation records. The FAA said it is investigating this event, as reported by the Associated Press; we have not found a published FAA report or an NTSB investigation record for it as of November 17, 2026. This breakdown is an educational reconstruction from the published audio and ADS-B data, not an official finding of cause or fault. The linked FAA pages are maintained online and may change.