Unstable approach — JBU185
KRDU · 142026-06-27 02:42 UTC· KJFK → KRDU· JETBLUE AIRWAYS CORP· BCS3
JBU185 (Jetblue Airways) was operating from KJFK to KRDU on 2026-06-27. SkyMeter detected a low approach-stability score at Raleigh Durham International Airport (KRDU) on runway 14 at 02:42 UTC. Trace data at the event: 1545 ft AGL, 127 kt GS. Approach stability score: 41/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 5 kt wind, 4 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)- SECURITY6/3956 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Atlantic City, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3961 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Chester, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3965 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Galloway, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3967 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
PHILADELPHIA, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3973 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
WILMINGTON, DE, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4115 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
BASKING RIDGE, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4117 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Warren, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/6442 2026-06-10 04:01Z – 2026-07-20 03:59Z SFC–1,000 ft
Philadelphia, PA, Wednesday, June 10, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - SECURITY6/9498 2026-06-24 11:00Z – 2026-06-30 23:59Z SFC–2,000 ft
Baltimore, MD, Wednesday, June 24, 2026 through Tuesday, June 30, 2026 Local
View FAA NOTAM → - AIR SHOWS/SPORTS6/8970 2026-06-24 16:00Z – 2026-06-28 20:00Z SFC–15,000 ft
Baltimore, MD, Wednesday, June 24, 2026 through Sunday, June 28, 2026 UTC
View FAA NOTAM → - SECURITY6/0081 2026-06-26 04:01Z – 2026-07-04 03:59Z SFC–400 ft
New York, NY, Friday, June 26, 2026 through Friday, July 3, 2026 Local
View FAA NOTAM → - SECURITY6/0506 2026-06-26 21:30Z – 2026-06-27 02:00Z SFC–400 ft
Philadelphia, PA, Friday, June 26, 2026 through Friday, June 26, 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
- 1545 ft AGL at event
- 127 kt ground speed
- 0 fpm vertical
- Approach stability 41/100
- 5 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KRDU 082151Z 23005KT 10SM FEW060 BKN250 28/13 A2996 RMK AO2 SLP142 T02830133 $
Flight context
- JBU185
- Jetblue Airways
- BCS3
- KJFK → KRDU
- 2026-06-27 02:42 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