Long landing rollout — CFR72
KHMT · 222026-03-27 17:50 UTC· KMCC → KHMT· USDA FOREST SERVICE FEPP, CALIFORNIA DEPT OF FORESTRY AND FIRE P· S2T
CFR72 (Usda Forest Service Fepp) was operating from KMCC to KHMT on 2026-03-27. SkyMeter detected a long landing rollout at Hemet Ryan Airport (KHMT) on runway 22 at 17:50 UTC. Trace data at the event: 1515 ft AGL, 29 kt GS. Approach stability score: 43/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 3 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/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft
Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 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 22
- 1515 ft AGL at event
- 29 kt ground speed
- 0 fpm vertical
- Approach stability 43/100
- 3 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- METAR KHMT 230815Z AUTO 00000KT 10SM CLR 18/14 A2990 RMK AO2 T01830136 $
Flight context
- CFR72
- Usda Forest Service Fepp
- S2T
- KMCC → KHMT
- 2026-03-27 17:50 UTC
- KHMT runway 22
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