Return to field — TKR168
KMCC · 162026-07-21 20:27 UTC· KMCC → KMCC· AERO-FLITE INC· RJ85
TKR168 (Aero-Flite) had departed KMCC on 2026-07-21. SkyMeter detected a return to field at Mc Clellan Airfield (KMCC) on runway 16 at 20:27 UTC. Peak altitude 6,859 ft, turnaround area near Sheridan, US. Approach stability score: 31/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, 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 → - HAZARDS6/7245 2026-07-21 03:43Z – 2026-08-04 03:30Z SFC–7,000 ft
9NM NW GRASS VALLEY DISPATCH CENTER, CA, Tuesday, July 21, 2026 through Tuesday, August 4, 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 16
- 6859 ft AGL at event
- 293 kt ground speed
- 0 fpm vertical
- Approach stability 31/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KMCC 161655Z AUTO 18013KT 10SM BKN020 19/13 A2992 RMK AO2
Flight context
- TKR168
- Aero-Flite
- RJ85
- KMCC → KMCC
- 2026-07-21 20:27 UTC
- KMCC runway 16
All events on this flight
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