Long landing rollout — JKR88
KSUW · 042026-08-28 00:35 UTC· KSUW → KCLE· FLCN14 LLC· FA50
JKR88 (Flcn14) was operating from KSUW to KCLE on 2026-08-28. SkyMeter detected a long landing rollout at Richard I Bong Airport (KSUW) on runway 04 at 00:35 UTC. Trace data at the event: 656 ft AGL, 0 kt GS. Approach stability score: 68/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 5 kt wind, 4 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)- HAZARDS6/8538 2026-08-27 13:04Z – 2026-08-31 23:59Z SFC–2,000 ft
IRON COUNTY, WI, Thursday, August 27, 2026 through Monday, August 31, 2026 UTC
View FAA NOTAM → - SECURITY6/6997 2026-08-27 15:00Z – 2026-08-31 03:00Z SFC–400 ft
Plymouth, MI, Thursday, August 27, 2026 through Sunday, August 30, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/7433 2026-08-27 21:00Z – 2026-08-29 04:30Z SFC–400 ft
Chicago, IL, Thursday, August 27, 2026 through Saturday, August 29, 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
- 656 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 68/100
- 5 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- METAR KSUW 152115Z AUTO 28009KT 10SM OVC050 20/09 A3007 RMK AO2 T01990091
Flight context
- JKR88
- Flcn14
- FA50
- KSUW → KCLE
- 2026-08-28 00:35 UTC
- KSUW 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