Long landing rollout — ASPEN41

KRIV · 32

2026-07-12 21:21 UTC· KIWA KRIV· T38

ASPEN41 was operating from KIWA to KRIV on 2026-07-12. SkyMeter detected a long landing rollout at March ARB Airport (KRIV) on runway 32 at 21:21 UTC. Trace data at the event: 1450 ft AGL, 6 kt GS. METAR at the time reported 5 kt wind, 3 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)
  • SECURITY6/3948 2026-06-01 07:00Z – 2026-07-21 06:59Z

    MESA, AZ, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/3966 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    Mesa, AZ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7079 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft

    Mesa, AZ

    View FAA NOTAM →
  • SECURITY6/7078 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft

    Mesa, AZ

    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 32
  • 1450 ft AGL at event
  • 6 kt ground speed
  • 0 fpm vertical
  • 5 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • KRIV 180255Z AUTO 31007KT 10SM CLR 21/13 A3003 RMK AO2 SLP159 T02140128 52013

Flight context

  • ASPEN41
  • T38
  • KIWA → KRIV
  • 2026-07-12 21:21 UTC
  • KRIV runway 32

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· KRIV