RCH168 was operating from KWRI to KTPF on 2026-07-24. SkyMeter detected a long landing rollout at Peter O Knight Airport (KTPF) on runway 04 at 04:07 UTC. Trace data at the event: 16 ft AGL, 0 kt GS, 0 fpm vertical. METAR at the time reported 4 kt wind, 2 kt crosswind component, 14,484 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/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft
2NM W SHULERVILLE, SC, Monday, July 20, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - SECURITY6/6747 2026-07-20 12:30Z – 2026-07-24 06:00Z SFC–2,500 ft
MAYPORT, FL, Monday, July 20, 2026 through Friday, July 24, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/6412 2026-07-23 18:00Z – 2026-07-24 03:59Z SFC–400 ft
Raleigh, NC, Thursday, July 23, 2026 through Friday, July 24, 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 04
- 16 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 2 kt crosswind component
- 14,484 m visibility
- METAR KTPF 160315Z AUTO 06008KT 9SM CLR 27/25 A3010 RMK AO2 T02750249 $
Flight context
- RCH168
- C17
- KWRI → KTPF
- 2026-07-24 04:07 UTC
- KTPF runway 04
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