Return to field — TKR160

KMCC · 34

2026-07-13 17:13 UTC· KMCC → KMCC· AERO-FLITE INC· RJ85

▶ Replay 📊 Analyse

TKR160 (Aero-Flite) had departed KMCC on 2026-07-13. SkyMeter detected a return to field at Mc Clellan Airfield (KMCC) on runway 34 at 17:13 UTC. Peak altitude 7,027 ft, turnaround area near Sheridan, US. Approach stability score: 58/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 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft

    BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

    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 34
  • 7027 ft AGL at event
  • 282 kt ground speed
  • 0 fpm vertical
  • Approach stability 58/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KMCC 162155Z AUTO 20011G20KT 10SM CLR 25/10 A2990 RMK AO2

Flight context

  • TKR160
  • Aero-Flite
  • RJ85
  • KMCC → KMCC
  • 2026-07-13 17:13 UTC
  • KMCC runway 34

All events on this flight

Return to field 17:13:17 UTC · KMCC runway 34 · 7,027 ft AGL · 282 kt GS
Unstable approach 17:54:33 UTC · KMCC runway 34 · 1,181 ft AGL · 132 kt GS
Unstable approach 19:01:19 UTC · KMCC runway 34 · 1,170 ft AGL · 120 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· KMCC