Return to field — JBU1158
KFLL · 10R2026-06-25 15:22 UTC· KFLL → KFLL· JETBLUE AIRWAYS CORP· A320
JBU1158 (Jetblue Airways) was operating from KFLL to KFLL (Fort Lauderdale Hollywood International Airport) on 2026-06-25. SkyMeter detected a return to field at Fort Lauderdale Hollywood International Airport (KFLL) on runway 10R at 15:22 UTC. Peak cruise altitude FL393, turnaround area near Municipio de Melena del Sur, CU. METAR at the time reported 0 kt wind, 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/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft
OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local
View FAA NOTAM → - SECURITY6/4130 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MIAMI, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4142 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Miami, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7228 2026-06-13 04:01Z – 2026-07-06 03:59Z SFC–1,000 ft
Miami, FL, Saturday, June 13, 2026 through Sunday, July 5, 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 10R
- 39311 ft AGL at event
- 483 kt ground speed
- 0 fpm vertical
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KFLL 162153Z COR 06013KT 10SM FEW023 SCT030 SCT080 BKN250 30/24 A3005 RMK AO2 SLP175 T03000244
Flight context
- JBU1158
- Jetblue Airways
- A320
- KFLL → KFLL
- 2026-06-25 15:22 UTC
- KFLL runway 10R
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