Long landing rollout — TOPCT31

KCBF · 14

2026-08-17 21:21 UTC· KOFF KCBF· R135

TOPCT31 was operating from KOFF to KCBF on 2026-08-17. SkyMeter detected a long landing rollout at Council Bluffs Municipal Airport (KCBF) on runway 14 at 21:21 UTC. Trace data at the event: 964 ft AGL, 14 kt GS. Approach stability score: 40/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 3 kt wind, 2 kt crosswind component, 3,219 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/4893 2026-08-13 13:00Z – 2026-08-28 03:00Z SFC–9,000 ft

    43NM E HOT SPRINGS, SD, Thursday, August 13, 2026 through Friday, August 28, 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 14
  • 964 ft AGL at event
  • 14 kt ground speed
  • 0 fpm vertical
  • Approach stability 40/100
  • 3 kt wind
  • 2 kt crosswind component
  • 3,219 m visibility
  • METAR KCBF 160555Z AUTO 06006KT 2SM +RA BR FEW005 SCT027 BKN037 15/15 A3023 RMK AO2

Flight context

  • TOPCT31
  • R135
  • KOFF → KCBF
  • 2026-08-17 21:21 UTC
  • KCBF runway 14

All events on this flight

Long landing rollout 21:21:29 UTC · KCBF runway 14 · 964 ft AGL · 14 kt GS
Long landing rollout 21:21:29 UTC · KCBF runway 14 · 964 ft AGL · 14 kt GS

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

SkyMeter · trace data observed via ADS-B· KCBF