Diversion — SWA776
KBNA · 02L2026-08-02 19:48 UTC· KMKE → KBNA· SOUTHWEST AIRLINES CO· B737
SWA776 (Southwest Airlines) was operating from KMKE to KTPA (Tampa International Airport) on 2026-08-02. SkyMeter detected a diversion to Nashville International Airport (KBNA) on runway 02L at 19:48 UTC. Peak cruise altitude FL407, turnaround area near Seelyville, US. Approach stability score: 89/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 12 kt wind, 11 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- UAS PUBLIC GATHERING6/8930 2026-07-30 16:00Z – 2026-08-03 03:00Z SFC–400 ft
Chicago, IL, Thursday, July 30, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft
Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC
View FAA NOTAM → - SECURITY6/0650 2026-08-01 16:00Z – 2026-08-02 22:00Z SFC–400 ft
Michigan City, IN, Saturday, August 1, 2026 through Sunday, August 2, 2026 Local
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- Runway 02L
- 555 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 89/100
- 12 kt wind
- 11 kt crosswind component
- 16,093 m visibility
- KBNA 171753Z VRB04KT 10SM SCT055 36/19 A3026 RMK AO2 SLP240 6//// T03560189 10361 20244 58016
Flight context
- SWA776
- Southwest Airlines
- B737
- KMKE → KBNA
- 2026-08-02 19:48 UTC
- KBNA runway 02L
Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data