Long landing rollout — MXY100
KHVN · 202026-07-21 16:16 UTC· KCHS → KHVN· BANK OF UTAH TRUSTEE· BCS3
MXY100 (Bank of Utah) was operating from KCHS to KHVN on 2026-07-21. SkyMeter detected a long landing rollout at Tweed New Haven Airport (KHVN) on runway 20 at 16:16 UTC. Trace data at the event: 3 ft AGL, 4 kt GS, 0 fpm vertical. METAR at the time reported 8 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)- 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/4931 2026-07-11 15:58Z – 2026-07-23 01:00Z SFC–3,000 ft
2NM NE SHALLOTTE, NC, Saturday, July 11, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/5843 2026-07-14 23:37Z – 2026-07-22 23:45Z SFC–4,200 ft
18NM SW WAYNESBORO, VA, Tuesday, July 14, 2026 through Wednesday, July 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft
2NM W SHULERVILLE, SC, Monday, July 20, 2026 through Monday, August 3, 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 20
- 3 ft AGL at event
- 4 kt ground speed
- 0 fpm vertical
- 8 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KHVN 162153Z 13004KT 10SM CLR 23/18 A3029 RMK AO2 SLP257 T02280178
Flight context
- MXY100
- Bank of Utah
- BCS3
- KCHS → KHVN
- 2026-07-21 16:16 UTC
- KHVN runway 20
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