RCH533 was operating from KSKF to KHMN on 2026-08-31. SkyMeter detected a long landing rollout at Holloman Air Force Base (KHMN) on runway 22 at 15:39 UTC. Trace data at the event: 4048 ft AGL, 0 kt GS. METAR at the time reported 5 kt wind, 3 kt crosswind component, 11,265 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/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft
SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - HAZARDS6/9244 2026-08-30 20:00Z – 2026-09-06 02:00Z SFC–6,000 ft
12NM NW ROCKSPRINGS, TX, Sunday, August 30, 2026 through Sunday, September 6, 2026 UTC
View FAA NOTAM → - HAZARDS6/9262 2026-08-31 13:00Z – 2026-09-15 02:00Z SFC–6,000 ft
12NM NW ROCKSPRINGS, TX, Monday, August 31, 2026 through Tuesday, September 15, 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 22
- 4048 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 3 kt crosswind component
- 11,265 m visibility
- KHMN 161042Z 13017KT 7SM -RA BKN060 20/17 A3024 RMK AO2A LTG DSNT NE-E RAB0955E01RAB01E12DZB34E38RAB38 TSB0955E26 SLP165 $
Flight context
- RCH533
- C17
- KSKF → KHMN
- 2026-08-31 15:39 UTC
- KHMN runway 22
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