Long landing rollout — N56CH

KRIV · 32

2026-08-04 15:31 UTC· KABQ → KRIV· CMH HOMES INC· E550

▶ Replay 📊 Analyse

N56CH (CMH Homes) was operating from KABQ to KRIV on 2026-08-04. SkyMeter detected a long landing rollout at March ARB Airport (KRIV) on runway 32 at 15:31 UTC. Trace data at the event: 1450 ft AGL, 16 kt GS. Approach stability score: 69/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 1 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)
  • HAZARDS6/0715 2026-08-01 02:12Z – 2026-08-08 04:00Z SFC–7,000 ft

    YUCAIPA, CA, Saturday, August 1, 2026 through Saturday, August 8, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/1013 2026-08-02 21:25Z – 2026-08-05 04:00Z SFC–6,000 ft

    YUCAIPA, CA, Sunday, August 2, 2026 through Wednesday, August 5, 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 32
  • 1450 ft AGL at event
  • 16 kt ground speed
  • 0 fpm vertical
  • Approach stability 69/100
  • 1 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KRIV 161855Z AUTO 12007KT 10SM CLR 25/12 A2999 RMK AO2 SLP144 T02520124

Flight context

  • N56CH
  • CMH Homes
  • E550
  • KABQ → KRIV
  • 2026-08-04 15:31 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