Long landing rollout — JBU1338
KBDL · 192026-04-04 04:37 UTC· KMCO → KBDL· JETBLUE AIRWAYS CORP· A320
JBU1338 (Jetblue Airways) was operating from KMCO to KBDL on 2026-04-04. SkyMeter detected a long landing rollout at Bradley International Airport (KBDL) on runway 19 at 04:37 UTC. Trace data at the event: 187 ft AGL, 10 kt GS, 0 fpm vertical. METAR at the time reported 6 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 → - HAZARDS6/4875 2026-03-30 13:00Z – 2026-04-04 06:00Z SFC–2,500 ft
20NM NW MEDFORD, OR, Friday, July 10, 2026 through Saturday, July 25, 2026 UTC
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
- 10 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KBDL 221251Z 02011KT 10SM FEW025 SCT060 BKN140 BKN250 13/08 A3035 RMK AO2 SLP276 T01330083
Flight context
- JBU1338
- Jetblue Airways
- A320
- KMCO → KBDL
- 2026-04-04 04:37 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