One go-around. One departure. One right turn.

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.

Incident facts
Date and timeSat 18 Apr 2026, 22:37Z (5:37 p.m. CDT)
AirportNashville International (BNA), north flow, wind 330° at 19 kt gusting 24 (tower)
Aircraft 1Southwest 507 (SWA507), Boeing 737 MAX 8, Myrtle Beach to Nashville, ILS runway 2L, went around
Aircraft 2Southwest 1152 (SWA1152), Boeing 737-700, Nashville to Knoxville, departing runway 2R
Closest pointAbout 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.
ControllerNashville Tower (BNA ATCT)
OutcomeBoth crews reported TCAS RAs; no injuries reported; FAA investigating
Southwest 507Boeing 737 MAX 8 · arriving runway 2L
Southwest 1152Boeing 737-700 · departing runway 2R
Nashville TowerThe local controller working both runways
Scroll to run the clock
NASHVILLE TWR · BNA22:35:15Z
CONTROLLER INSTINCTS0 / 2
22:35:15Z The setup

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.

Why it works

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.

22:36:14Z Cleared for takeoff
Tower · to Southwest 1152

"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.

22:36:32Z Going around

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.

What the tape doesn't have

The published recording doesn't include 507's go-around call. The first thing we hear is the tower's reply.

22:36:45Z First call
Tower · to Southwest 507

"Southwest 507, maintain 2,000."

Level off at 2,000 feet.

Southwest 507

"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.

Read the scope
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
22:36:55Z The turn

Where it went wrong: "turn right heading 110"

Tower · to Southwest 507

"Southwest 507, turn right heading 1-1-0."

Turn right until you're pointed east-southeast.

Southwest 507

"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.

Freeze frame

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.

22:37:06Z The plan on paper
The published missed approach

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.

What the data shows

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.

22:37:12Z The missed beat
Tower · to Southwest 507

"Southwest 507, climb and maintain 3,000."

Keep climbing, up to 3,000.

Tower · to Southwest 1152

"Southwest 1152, maintain 2,000."

Stop your climb at 2,000.

Southwest 1152

"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.

Your call

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?

22:37:24Z The reversal
Tower · to Southwest 507

"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.

Southwest 507

"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.

The rule

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.

22:37:32Z Closest point

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.

The rule

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.

About these altitudes

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.

22:37:52Z Out of the RA
Southwest 1152

"Do you want an altitude, Southwest 1152? Out of the RA."

Our collision alert is over. What altitude do you want us at?

Tower · to Southwest 1152

"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.

22:38:00Z On frequency
Tower · to Southwest 507

"Southwest 507, climb and maintain 4,000."

Southwest 507

"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.

22:38:51Z Off to approach
Tower · to Southwest 507

"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.

Takeaways

What this one teaches

Three habits a tower controller running parallel runways builds, and why each one mattered here.

Plan

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.

Look

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.

Vertical

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.

SectorLive

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
Play free in your browser
Questions

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.

Full transcript

Every word on frequency

Nashville Tower, 22:32:05Z to 22:38:56Z (published recording, with gaps)
22:32:05ZSouthwest 507Tower, Southwest 507, ILS 2L.
22:32:28ZNashville TowerSouthwest 507, Nashville Tower, runway 2L, cleared to land, wind 330 at 14.
22:32:40ZSouthwest 507Cleared to land 2L, Southwest 507.
22:32:45ZNashville TowerSouthwest 2803, right at B3, B, T2 to the ramp.
22:32:56ZSouthwest 2803B3, B, T2 to the ramp, Southwest 2803.
22:34:39ZNashville TowerSouthwest 715, RNAV to FRNCS, runway 2R, cleared for takeoff.
22:34:43ZSouthwest 715RNAV FRNCS, cleared for takeoff 2R, Southwest 715.
22:34:46ZNashville TowerSouthwest 606, contact Departure.
22:34:48ZSouthwest 606Departure, good day.
22:34:51ZNashville TowerSouthwest 1152, Nashville Tower, runway 2R, line up and wait.
22:34:54ZSouthwest 11522R, line up and wait [rest cut off].
22:34:55ZNashville TowerSouthwest 2718, right at B3, north on B, T2 to the ramp.
22:35:00ZSouthwest 2718Right B3, B, T2 to the ramp, Southwest 2718.
22:35:06ZNashville TowerWinds are now 330 at 19, gusts 24.
22:35:58ZSouthwest 558Tower, Southwest 558, ILS 2L.
22:36:02ZNashville TowerSouthwest 558, Nashville Tower, runway 2L, cleared to land, wind 330 at 19, gusts 24.
22:36:07ZSouthwest 5582L, cleared to land, Southwest 558.
22:36:14ZNashville TowerSouthwest 1152, RNAV to SHWIT, runway 2R, cleared for takeoff.
22:36:19ZSouthwest 1152[readback not readable]
22:36:32ZNashville TowerSouthwest 715, contact Departure.
22:36:35ZSouthwest 715Departure, Southwest 715.
22:36:45ZNashville TowerSouthwest 507, maintain 2,000.
22:36:49ZSouthwest 5072,000, Southwest 507.
22:36:55ZNashville TowerSouthwest 507, turn right heading 110.
22:36:58ZSouthwest 507Right turn heading 110, Southwest 507.
22:37:12ZNashville TowerSouthwest 507, climb and maintain 3,000.
22:37:14ZSouthwest 5073,000, Southwest 507.
22:37:17ZNashville TowerSouthwest 1152, maintain 2,000.
22:37:20ZSouthwest 11522,000, we're already past it, Southwest 1152.
22:37:24ZNashville TowerHe's already in the turn. Southwest 507, descend and maintain 2,000.
22:37:28ZSouthwest 507Down to 2,000, Southwest 507.
22:37:31ZEnvoy 3436Tower, Envoy 3436, ILS 2L.
22:37:44ZEnvoy 3436Nashville Tower, Envoy 3436.
22:37:52ZSouthwest 1152Do you want an altitude, Southwest 1152? Out of the RA.
22:37:55ZNashville TowerSouthwest 1152, climb, you can climb via the SID.
22:37:57ZSouthwest 1152Climb via the SID, Southwest 1152.
22:38:00ZNashville TowerSouthwest 507, climb and maintain 4,000.
22:38:02ZSouthwest 5074,000, Southwest 507. And we responded to the RA.
22:38:05ZNashville TowerThanks.
22:38:09ZEnvoy 3436Nashville Tower, Envoy 3436, ILS 2L.
22:38:14ZNashville TowerSouthwest 507, turn right heading 1[...], turn right heading 200.
22:38:18ZSouthwest 507200, Southwest 507.
22:38:23ZNashville TowerEnvoy 43[...], correction, Envoy 3436, runway 2L, cleared to land.
22:38:27ZEnvoy 3436[readback], Envoy 3436.
22:38:32ZSouthwest 1152And Southwest 1152, we were originally climbing via the [SID name] Seven. Do you want that or the one on the chart?
22:38:38ZNashville TowerExecjet 359, Nashville Tower, runway 2L, cleared to land.
22:38:45ZSouthwest 1152Want us to Departure, Southwest 1152?
22:38:47ZNashville TowerSouthwest 1152, Departure.
22:38:51ZNashville TowerSouthwest 507, 124.7, correction, 118.4.
22:38:56ZSouthwest 50718.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.

Evidence and references

Sources

Incident audio and flight data

Primary FAA procedure references

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.