Diversion — JBU379
KRSW · 062026-08-29 13:04 UTC· KDCA → KRSW· JETBLUE AIRWAYS CORP· A320
JBU379 (Jetblue Airways) was operating from KDCA to KFLL (Fort Lauderdale Hollywood International Airport) on 2026-08-29. SkyMeter detected a diversion to Southwest Florida International Airport (KRSW) on runway 06 at 13:04 UTC. Peak cruise altitude FL383, turnaround area near Georgetown, US. Approach stability score: 66/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 6 kt wind, 3 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)- SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft
Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - VIP6/8638 2026-08-28 20:00Z – 2026-08-30 21:00Z SFC–4,999 ft
Middleburg, VA, Friday, August 28, 2026 through Sunday, August 30, 2026 Local
View FAA NOTAM → - VIP6/8771 2026-08-29 13:00Z – 2026-08-30 02:00Z SFC–9,999 ft
Sterling, VA, Saturday, August 29, 2026 through Saturday, August 29, 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 06
- 30 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 66/100
- 6 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KRSW 160453Z AUTO 08003KT 10SM CLR 26/24 A3010 RMK AO2 SLP188 T02560239 403390256
Flight context
- JBU379
- Jetblue Airways
- A320
- KDCA → KRSW
- 2026-08-29 13:04 UTC
- KRSW runway 06
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