Long landing rollout — JBU1242
KBDL · 192026-05-19 01:56 UTC· JETBLUE AIRWAYS CORP· A320
JBU1242 (Jetblue Airways) was inbound to KBDL on 2026-05-19. SkyMeter detected a long landing rollout at Bradley International Airport (KBDL) on runway 19 at 01:56 UTC. Trace data at the event: 187 ft AGL, 12 kt GS, 0 fpm vertical. METAR at the time reported 8 kt wind, 1 kt crosswind component, 16,093 m visibility. A long landing rollout is detected when ground deceleration after touchdown is below the per-runway P10 envelope. It is an observational measure of rollout efficiency, not a runway-exit incident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY6/9784 2026-05-16 12:00Z – 2026-06-12 22:00Z SFC–400 ft
Moyock, NC, Saturday, May 16, 2026 through Friday, June 12, 2026 Local
View FAA NOTAM → - SECURITY6/0907 2026-05-18 13:00Z – 2026-05-19 20:00Z SFC–1,000 ft
Morristown, NJ, Monday, May 18, 2026 through Tuesday, May 19, 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 19
- 187 ft AGL at event
- 12 kt ground speed
- 0 fpm vertical
- 8 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KBDL 201251Z 00000KT 10SM FEW028 SCT046 OVC075 15/11 A3010 RMK AO2 SLP192 T01500106
Flight context
- JBU1242
- Jetblue Airways
- A320
- 2026-05-19 01:56 UTC
- KBDL runway 19
All events on this flight
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