Unstable approach — N212HF

N212HF (Gopher AIR) was operating from KCMH to KRNH on 2026-07-02. SkyMeter detected a low approach-stability score at Flying Cloud Airport (KFCM) on runway 10R at 16:43 UTC. Trace data at the event: 1991 ft AGL, 139 kt GS. Approach stability score: 50/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, 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.

• SECURITY6/4128 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  WESTFIELD, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/7208 2026-06-23 21:07Z – 2026-07-21 03:59Z SFC–400 ft

  Westfield, IN

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/0131 2026-06-30 11:00Z – 2026-07-07 02:00Z SFC–400 ft

  Columbus, OH, Tuesday, June 30, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• SECURITY6/1457 2026-07-01 11:00Z – 2026-07-06 02:00Z SFC–400 ft

  SILVIS, IL, Wednesday, July 1, 2026 through Sunday, July 5, 2026 Local

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/1384 2026-07-01 13:30Z – 2026-07-05 22:00Z SFC–16,000 ft

  battle Creek, MI, Wednesday, July 1, 2026 through Sunday, July 5, 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.

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