On the afternoon of April 18, 2026, two Southwest Airlines Boeing 737s came within roughly 500 feet of each other in the terminal airspace around Nashville International Airport (BNA). There was no collision, no injuries, and no damage. Both aircraft landed normally a few minutes later. The reason that line reads the way it does — and not the other way around — is that the Traffic Collision Avoidance System on each jet did exactly what it was designed to do: it issued coordinated Resolution Advisories, the crews followed them within seconds, and the geometry of two converging aluminum tubes resolved itself without anyone touching the radio.
For working pilots, the Nashville event is less a story about a near-miss than a quiet reminder of how the last layer of the safety net actually behaves when the layers above it stretch thin.
What Reportedly Happened
Initial reporting from local Nashville outlets and aviation trade press places both aircraft on standard arrival profiles into BNA in the late afternoon. According to those accounts, the two 737s were vectored onto converging paths in the terminal area, and the lateral and vertical separation closed below standard minimums before either crew received a corrective instruction from controllers. TCAS II on both aircraft progressed from a Traffic Advisory to coordinated Resolution Advisories — one crew received a climb command, the other a descent command — and both complied promptly. Vertical separation was restored in seconds.
The FAA has confirmed it is investigating the loss of separation. The NTSB is aware of the event but, as of publication, has not announced a formal investigation. Specific altitudes, headings, and the recorded closest point of approach will be confirmed only through the formal preliminary report.
Why TCAS II Worked the Way It Did
TCAS II is mandated on US-registered transport-category aircraft with more than 30 passenger seats under 14 CFR §121.356, and is interoperable with ICAO ACAS II. The system interrogates nearby Mode S and Mode C transponders, builds a three-dimensional picture of conflicting traffic, and — when a collision becomes probable inside roughly 15 to 35 seconds — issues a Resolution Advisory in the vertical plane only.
Two design choices matter here:
- Coordination. When both aircraft are TCAS II–equipped, the units negotiate via the Mode S data link so the advisories are always opposite in sense. One climbs, the other descends. Neither crew has to know what the other is doing.
- Authority. Per FAA Advisory Circular 120-55 and the Aeronautical Information Manual §4-4-15, flight crews are expected to follow an RA promptly even if it conflicts with an ATC instruction, and to notify ATC as soon as practical. This is not a suggestion; it is the operational norm baked into every Part 121 training footprint.
The Nashville sequence appears to be a textbook execution of that norm: the system saw it, the crews flew it, the controllers were informed, and traffic continued.
The Broader Context: ATC Workload
The reason an event like this lands in the national news cycle, rather than in a quiet ASRS report, is the ongoing strain on the en route and terminal controller workforce. The FAA has acknowledged in multiple public updates that controller staffing remains below targeted levels at several large facilities, and the agency continues to expand hiring and academy throughput. Industry groups, including AOPA and NATCA, have consistently advocated for sustained investment in both staffing and modernization.
It is important to be careful here. A single loss-of-separation event is not, by itself, evidence of a systemic failure, and the agencies involved are actively working the problem. What the Nashville event does illustrate is the value of defense-in-depth: when controller workload is elevated for any reason — weather, traffic volume, sector complexity — the airborne layer becomes the layer that matters most.
Practical Takeaways for US Pilots
For Part 121 and Part 135 crews, none of this is new, but it is worth re-anchoring on the fundamentals before the next leg:
- Fly the RA, then talk. Pitch to the green band, disconnect the autopilot if your operator's procedures require it, and advise ATC after the maneuver is stable. Do not reverse an RA based on a controller call.
- Treat TAs as a setup, not a finish. A Traffic Advisory is the system telling you to look outside, brief the likely RA, and be ready to fly it manually within five seconds.
- Honor the vertical command exactly. RAs are designed around minimum vertical rates (typically 1,500 fpm for an initial RA, 2,500 fpm for a strengthened RA). Under-flying the command erodes the safety margin the algorithm assumed when it issued it.
- Debrief honestly. ASRS and your operator's ASAP program exist precisely so events like this generate learning, not blame.
For Part 91 operators in busy Class B and Class C terminal areas, the lesson is simpler: keep your transponder on Mode C or Mode S with altitude reporting active, because every airliner around you is using your return to keep itself — and you — out of trouble.
Where This Goes Next
Expect an FAA preliminary statement on the loss of separation, and watch the NTSB Aviation Accident Database for any formal docket. Southwest will conduct its own internal review under its SMS program. The most useful product for line pilots will likely be the eventual ASRS callback summary or an FAA InFO bulletin reinforcing RA compliance procedures.
Until then, the headline that matters is the boring one: the system worked, the crews flew the airplane, and two full 737s went to the gate.
Sources
- FAA Advisory Circular 120-55C, Air Carrier Operational Approval and Use of TCAS II — https://www.faa.gov/regulations_policies/advisory_circulars
- FAA Aeronautical Information Manual, §4-4-15, Traffic Alert and Collision Avoidance System (TCAS I & II) — https://www.faa.gov/air_traffic/publications/atpubs/aim_html
- NTSB Aviation Accident Database & Synopses — https://www.ntsb.gov/Pages/AviationQueryV2.aspx
Information current as of publish date; pilots responsible for verifying with current FAA/NTSB sources before flight.
AeroCopilot surfaces FAA safety bulletins, NOTAMs, and operator-specific items like RA compliance reminders directly into your pre-flight briefing, so the relevant guidance is in front of you before you push back — not after.
By the AeroCopilot Editorial Team.