Diversion — JBU83
KSAV · 102026-08-29 22:44 UTC· KJFK → KSAV· JETBLUE AIRWAYS CORP· A320
JBU83 (Jetblue Airways) was operating from KJFK to KMCO (Orlando International Airport) on 2026-08-29. SkyMeter detected a diversion to Savannah Hilton Head International Airport (KSAV) on runway 10 at 22:44 UTC. Peak cruise altitude FL383, turnaround area near Jackson, 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 7 kt wind, 4 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/7351 2026-08-27 12:00Z – 2026-10-13 03:00Z SFC–400 ft
Timonium, MD, Thursday, August 27, 2026 through Tuesday, October 13, 2026 UTC
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 10
- 46 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 89/100
- 7 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KSAV 120653Z AUTO 19003KT 10SM CLR 23/23 A2999 RMK AO2 SLP153 T02330233 TSNO
Flight context
- JBU83
- Jetblue Airways
- A320
- KJFK → KSAV
- 2026-08-29 22:44 UTC
- KSAV runway 10
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