Long landing rollout — JBU488
KORH · 292025-11-18 15:49 UTC· KMCO → KORH· JETBLUE AIRWAYS CORP· A320
JBU488 (Jetblue Airways) was operating from KMCO to KORH on 2025-11-18. SkyMeter detected a long landing rollout at Worcester Regional Airport (KORH) on runway 29 at 15:49 UTC. Trace data at the event: 879 ft AGL, 10 kt GS. Approach stability score: 89/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 14 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 →
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 29
- 879 ft AGL at event
- 10 kt ground speed
- 0 fpm vertical
- Approach stability 89/100
- 14 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KORH 071854Z 19007KT 10SM CLR 16/03 A2991 RMK AO2 SLP133 T01610028 $
Flight context
- JBU488
- Jetblue Airways
- A320
- KMCO → KORH
- 2025-11-18 15:49 UTC
- KORH runway 29
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