Long landing rollout — N725AT
KOFP · 162026-09-03 13:46 UTC· KSTC → KOFP· RBJ INDUSTRIES INC· C25B
N725AT (RBJ Industries) was operating from KSTC to KOFP on 2026-09-03. SkyMeter detected a long landing rollout at Hanover County Municipal Airport (KOFP) on runway 16 at 13:46 UTC. Trace data at the event: 200 ft AGL, 10 kt GS, 0 fpm vertical. Approach stability score: 81/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, 2 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/6998 2026-08-27 11:00Z – 2026-09-08 03:00Z SFC–400 ft
St. Paul, MN, Thursday, August 27, 2026 through Monday, September 7, 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 16
- 200 ft AGL at event
- 10 kt ground speed
- 0 fpm vertical
- Approach stability 81/100
- 3 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- METAR KOFP 312354Z AUTO 00000KT 10SM CLR 27/23 A3008 RMK AO2 SLP183 T02670228 10333 20267 52004
Flight context
- N725AT
- RBJ Industries
- C25B
- KSTC → KOFP
- 2026-09-03 13:46 UTC
- KOFP runway 16
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