Long landing rollout — JBU2432
KBOS · 272026-08-09 21:17 UTC· KLGA → KBOS· JETBLUE AIRWAYS CORP· BCS3
JBU2432 (Jetblue Airways) was operating from KLGA to KBOS on 2026-08-09. SkyMeter detected a long landing rollout at General Edward Lawrence Logan International Airport (KBOS) on runway 27 at 21:17 UTC. Trace data at the event: 29 ft AGL, 10 kt GS, 0 fpm vertical. Approach stability score: 92/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 10 kt wind, 5 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)- VIP6/3108 2026-08-09 20:00Z – 2026-08-09 22:00Z SFC–17,999 ft
Morristown, NJ, Sunday, August 9, 2026 Local
View FAA NOTAM → - VIP6/3115 2026-08-09 20:00Z – 2026-08-09 22:00Z SFC–17,999 ft
Morristown, NJ, Sunday, August 9, 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 27
- 29 ft AGL at event
- 10 kt ground speed
- 0 fpm vertical
- Approach stability 92/100
- 10 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KBOS 162254Z 20009KT 10SM FEW200 BKN250 23/17 A3025 RMK AO2 SLP243 T02330167
Flight context
- JBU2432
- Jetblue Airways
- BCS3
- KLGA → KBOS
- 2026-08-09 21:17 UTC
- KBOS runway 27
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