Unstable approach — JBU726
KRDU · 142026-07-04 23:32 UTC· KFLL → KRDU· JETBLUE AIRWAYS CORP· A320
JBU726 (Jetblue Airways) was operating from KFLL to KRDU on 2026-07-04. SkyMeter detected a low approach-stability score at Raleigh Durham International Airport (KRDU) on runway 14 at 23:32 UTC. Trace data at the event: 1541 ft AGL, 139 kt GS. Approach stability score: 42/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 6 kt wind, 1 kt crosswind component, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. 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 → - SECURITY6/4001 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
GREENSBORO, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4129 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
BOCA RATON, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4131 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4132 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Conway, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4133 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
PALM BEACH GARDENS, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4144 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
FORT LAUDERDALE, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4150 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Palm Beach Gardens, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/0777 2026-06-26 04:01Z – 2026-07-21 03:59Z SFC–400 ft
Fort Lauderdale, FL, Friday, June 26, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7906 2026-06-29 15:07Z – 2026-07-21 03:59Z SFC–400 ft
Boca Raton, FL
View FAA NOTAM → - SECURITY6/2638 2026-07-04 19:00Z – 2026-07-05 03:00Z SFC–400 ft
Cary, NC, Saturday, July 4, 2026 through Saturday, July 4, 2026 Local
View FAA NOTAM → - SECURITY6/2666 2026-07-04 21:00Z – 2026-07-05 03:30Z SFC–400 ft
Raleigh, NC, Saturday, July 4, 2026 through Saturday, July 4, 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 14
- 1541 ft AGL at event
- 139 kt ground speed
- 0 fpm vertical
- Approach stability 42/100
- 6 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KRDU 161751Z 16004KT 10SM FEW048 FEW250 28/17 A3037 RMK AO2 SLP278 T02830167 10289 20172 58014
Flight context
- JBU726
- Jetblue Airways
- A320
- KFLL → KRDU
- 2026-07-04 23:32 UTC
- KRDU runway 14
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