RHINO44 was operating from II10 to KFFO on 2026-06-24. SkyMeter detected a long landing rollout at Wright-Patterson Air Force Base (KFFO) on runway 05R at 01:09 UTC. Trace data at the event: 800 ft AGL, 10 kt GS. Approach stability score: 71/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 3 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/4118 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CARMEL, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4128 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
WESTFIELD, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7205 2026-06-23 21:07Z – 2026-07-21 03:59Z SFC–400 ft
Carmel, IN
View FAA NOTAM → - SECURITY6/7208 2026-06-23 21:07Z – 2026-07-21 03:59Z SFC–400 ft
Westfield, IN
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 05R
- 800 ft AGL at event
- 10 kt ground speed
- 0 fpm vertical
- Approach stability 71/100
- 3 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KFFO 181655Z 04006KT 10SM BKN018 BKN027 BKN033 OVC060 24/19 A3020 RMK AO2A SLP223 T02440190
Flight context
- RHINO44
- C17
- II10 → KFFO
- 2026-06-24 01:09 UTC
- KFFO runway 05R
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