Unstable approach — C2002

KMCC · 16

2026-08-11 20:35 UTC· KRIV KMCC· C30J

C2002 was operating from KRIV to KMCC on 2026-08-11. SkyMeter detected a low approach-stability score at Mc Clellan Airfield (KMCC) on runway 16 at 20:35 UTC. Trace data at the event: 1168 ft AGL, 128 kt GS. Approach stability score: 53/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 9 kt wind, 8 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.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • HAZARDS6/7246 2026-07-21 05:00Z – 2026-08-21 03:00Z SFC–10,500 ft

    20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Friday, August 21, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7372 2026-07-21 13:38Z – 2026-08-22 03:00Z SFC–10,500 ft

    20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Saturday, August 22, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9881 2026-07-29 02:10Z – 2026-08-12 04:00Z SFC–13,500 ft

    25NM S BISHOP, CA, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/1527 2026-08-04 13:48Z – 2026-08-17 04:00Z SFC–6,000 ft

    27NM NE STOCKTON, CA, Tuesday, August 4, 2026 through Monday, August 17, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/1795 2026-08-04 20:57Z – 2026-08-18 04:00Z SFC–6,000 ft

    27NM NE STOCKTON, CA, Tuesday, August 4, 2026 through Tuesday, August 18, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2274 2026-08-05 19:25Z – 2026-08-15 04:00Z SFC–13,500 ft

    25NM S BISHOP, CA, Wednesday, August 5, 2026 through Saturday, August 15, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2433 2026-08-05 21:49Z – 2026-08-15 04:00Z SFC–6,000 ft

    27NM NE STOCKTON, CA, Wednesday, August 5, 2026 through Saturday, August 15, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2489 2026-08-06 02:15Z – 2026-08-19 04:00Z SFC–9,000 ft

    27NM S BAKERSFIELD, CA, Thursday, August 6, 2026 through Wednesday, August 19, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2916 2026-08-08 01:45Z – 2026-08-15 05:00Z SFC–6,000 ft

    25NM S BAKERSFIELD, CA, Saturday, August 8, 2026 through Saturday, August 15, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/3138 2026-08-09 17:20Z – 2026-08-22 15:00Z SFC–15,000 ft

    15NM SE BIG PINE, CA, Sunday, August 9, 2026 through Saturday, August 22, 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
  • 1168 ft AGL at event
  • 128 kt ground speed
  • 0 fpm vertical
  • Approach stability 53/100
  • 9 kt wind
  • 8 kt crosswind component
  • 16,093 m visibility
  • KMCC 121455Z AUTO 16006G11KT 10SM CLR 18/12 A2987 RMK AO2

Flight context

  • C2002
  • C30J
  • KRIV → KMCC
  • 2026-08-11 20:35 UTC
  • KMCC runway 16

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