Long landing rollout — MXY760

KAVP · 04

2026-05-18 01:52 UTC· KMCO → KAVP· BANK OF UTAH TRUSTEE· BCS3

▶ Replay 📊 Analyse

MXY760 (Bank of Utah) was operating from KMCO to KAVP on 2026-05-18. SkyMeter detected a long landing rollout at Wilkes Barre Scranton International Airport (KAVP) on runway 04 at 01:52 UTC. Trace data at the event: 931 ft AGL, 0 kt GS. METAR at the time reported 5 kt wind, 3,219 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)
  • SECURITY6/9784 2026-05-16 12:00Z – 2026-06-12 22:00Z SFC–400 ft

    Moyock, NC, Saturday, May 16, 2026 through Friday, June 12, 2026 Local

    View FAA NOTAM →
  • VIP6/0904 2026-05-17 14:30Z – 2026-05-17 23:59Z SFC–9,999 ft

    Sterling, VA, Sunday, May 17, 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 04
  • 931 ft AGL at event
  • 0 kt ground speed
  • 0 fpm vertical
  • 5 kt wind
  • 0 kt crosswind component
  • 3,219 m visibility
  • KAVP 202154Z 00000KT 2SM BKN024 OVC035 19/18 A2993 RMK AO2 SFC VIS 10 RAE41 SLP131 P0002 T01890183 $

Flight context

  • MXY760
  • Bank of Utah
  • BCS3
  • KMCO → KAVP
  • 2026-05-18 01:52 UTC
  • KAVP runway 04

All events on this flight

Long landing rollout 01:52:17 UTC · KAVP runway 04 · 931 ft AGL · 0 kt GS
Long landing rollout 01:52:17 UTC · KAVP runway 04 · 931 ft AGL · 0 kt GS

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

SkyMeter · trace data observed via ADS-B· KAVP