Long landing rollout — N2PK
KOSH · 272026-07-21 14:44 UTC· MA51 → KOSH· CAMBRIDGE INDUSTRIES LLC· PC24
N2PK (Cambridge Industries) was operating from MA51 to KOSH on 2026-07-21. SkyMeter detected a long landing rollout at Wittman Regional Airport (KOSH) on runway 27 at 14:44 UTC. Trace data at the event: 803 ft AGL, 0 kt GS. Approach stability score: 79/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 12 kt wind, 8 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)- AIR SHOWS/SPORTS6/5564 2026-07-20 19:15Z – 2026-07-23 23:30Z SFC–16,000 ft
Oshkosh, WI, Monday, July 20, 2026 through Thursday, July 23, 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 27
- 803 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 79/100
- 12 kt wind
- 8 kt crosswind component
- 16,093 m visibility
- KOSH 171853Z 03007KT 10SM OVC014 18/16 A3024 RMK AO2 SLP235 T01830161
Flight context
- N2PK
- Cambridge Industries
- PC24
- MA51 → KOSH
- 2026-07-21 14:44 UTC
- KOSH runway 27
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