Unstable approach — N789KG
KMKC · 222026-07-29 17:14 UTC· KANE → KMKC· RPS AIR LLC· C56X
N789KG (RPS AIR) was operating from KANE to KMKC on 2026-07-29. SkyMeter detected a low approach-stability score at Charles B. Wheeler Downtown Airport (KMKC) on runway 22 at 17:14 UTC. Trace data at the event: 1877 ft AGL, 142 kt GS. METAR at the time reported 5 kt wind, 3 kt crosswind component, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/9803 2026-07-28 21:15Z – 2026-08-01 23:45Z SFC–200 ft
0.5NM NE MENASHA, WI, Tuesday, July 28, 2026 through Saturday, August 1, 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 22
- 1877 ft AGL at event
- 142 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KMKC 162054Z 18006KT 10SM CLR 32/23 A3014 RMK AO2 SLP197 T03220233 58019
Flight context
- N789KG
- RPS AIR
- C56X
- KANE → KMKC
- 2026-07-29 17:14 UTC
- KMKC runway 22
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