Long landing rollout — VXP322
KHVN · 022025-11-21 03:08 UTC· KFLL → KHVN· UMB BANK NA TRUSTEE· B738
VXP322 (UMB Bank NA) was operating from KFLL to KHVN on 2025-11-21. SkyMeter detected a long landing rollout at Tweed New Haven Airport (KHVN) on runway 02 at 03:08 UTC. Trace data at the event: 22 ft AGL, 2 kt GS, 0 fpm vertical. Approach stability score: 87/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 4 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/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft
Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - 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 02
- 22 ft AGL at event
- 2 kt ground speed
- 0 fpm vertical
- Approach stability 87/100
- 4 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KHVN 071753Z 20007KT 10SM CLR 17/04 A2998 RMK AO2 SLP151 T01720044 10172 20050 58026
Flight context
- VXP322
- UMB Bank NA
- B738
- KFLL → KHVN
- 2025-11-21 03:08 UTC
- KHVN runway 02
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