Unstable approach — N563M
KFOE · 212026-07-11 12:15 UTC· KEAU → KFOE· MENARD INC· C560
N563M (Menard) was operating from KEAU to KFOE on 2026-07-11. SkyMeter detected a low approach-stability score at Topeka Regional Airport - Forbes Field (KFOE) on runway 21 at 12:15 UTC. Trace data at the event: 2175 ft AGL, 166 kt GS. Approach stability score: 27/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 4 kt wind, 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)- SECURITY6/4146 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4149 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4151 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4154 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4155 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Riverside, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4157 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
PRAIRIE VILLAGE, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4162 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7652 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Riverside, MO
View FAA NOTAM → - SECURITY6/7650 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO
View FAA NOTAM → - SECURITY6/7646 2026-07-03 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Lawrence, KS
View FAA NOTAM → - SECURITY6/7647 2026-07-03 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Lawrence, KS
View FAA NOTAM → - SECURITY6/3215 2026-07-09 05:01Z – 2026-07-12 04:59Z SFC–1,000 ft
Kansas City, MO, Thursday, July 9, 2026 through Saturday, July 11, 2026 Local
View FAA NOTAM → - SECURITY6/7651 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft
Prairie Village, KS
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 21
- 2175 ft AGL at event
- 166 kt ground speed
- 0 fpm vertical
- Approach stability 27/100
- 4 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KFOE 291753Z 16010KT 10SM FEW048 SCT060 SCT075 23/19 A2987 RMK AO2 PK WND 18030/1710 RAB1658E31 SLP107 P0013 60013 T02280194 10256 20167 57005
Flight context
- N563M
- Menard
- C560
- KEAU → KFOE
- 2026-07-11 12:15 UTC
- KFOE runway 21
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