Return to field — N801KL

KFCM · 18

2026-07-18 00:00 UTC· KFCM → KFCM· ARIEL CORP· CL35

▶ Replay 📊 Analyse

N801KL (Ariel) had departed KFCM on 2026-07-18. SkyMeter detected a return to field at Flying Cloud Airport (KFCM) on runway 18 at 00:00 UTC. Peak cruise altitude FL476, turnaround area near Butte, US. Approach stability score: 42/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 0 kt wind, 12,875 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • UAS PUBLIC GATHERING6/5200 2026-07-17 18:00Z – 2026-07-18 06:00Z SFC–400 ft

    Ames, IA, Friday, July 17, 2026 through Saturday, July 18, 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 18
  • 47662 ft AGL at event
  • 493 kt ground speed
  • 0 fpm vertical
  • Approach stability 42/100
  • 0 kt wind
  • 0 kt crosswind component
  • 12,875 m visibility
  • METAR KFCM 312353Z 30004KT 8SM CLR 29/16 A2988 RMK AO2 SLP111 T02890161 10317 20289 51007

Flight context

  • N801KL
  • Ariel
  • CL35
  • KFCM → KFCM
  • 2026-07-18 00:00 UTC
  • KFCM runway 18

All events on this flight

Return to field 00:00:16 UTC · KFCM runway 18 · 47,662 ft AGL · 493 kt GS
Unstable approach 01:13:07 UTC · KFCM runway 28L · 2,003 ft AGL · 165 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· KFCM