Unstable approach — C2701

KMCC · 16

2026-08-08 02:02 UTC· KMCC KMCC· C27J

C2701 was operating from KMCC to KMCC on 2026-08-08. SkyMeter detected a low approach-stability score at Mc Clellan Airfield (KMCC) on runway 16 at 02:02 UTC. Trace data at the event: 1172 ft AGL, 149 kt GS. METAR at the time reported 10 kt wind, 2 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)
  • SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft

    SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local

    View FAA NOTAM →
  • SECURITY6/6491 2026-07-20 07:01Z – 2026-09-16 06:59Z SFC–1,499 ft

    Concord, CA, Monday, July 20, 2026 through Tuesday, September 15, 2026 Local

    View FAA NOTAM →
  • 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/7909 2026-07-22 18:11Z – 2026-08-08 04:00Z SFC–12,500 ft

    20NM N INDEPENDENCE, CA, Wednesday, July 22, 2026 through Saturday, August 8, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8464 2026-07-24 20:09Z – 2026-08-07 20:00Z SFC–13,500 ft

    20NM N INDEPENDENCE, CA, Friday, July 24, 2026 through Friday, August 7, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8945 2026-07-27 14:57Z – 2026-08-09 04:00Z SFC–5,500 ft

    SONORA, CA, Monday, July 27, 2026 through Sunday, August 9, 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/2267 2026-08-05 18:05Z – 2026-08-08 04:00Z SFC–9,000 ft

    27NM S BAKERSFIELD, CA, Wednesday, August 5, 2026 through Saturday, August 8, 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 →
  • SECURITY6/1482 2026-08-07 17:00Z – 2026-08-10 05:00Z SFC–400 ft

    San Francisco, CA, Friday, August 7, 2026 through Sunday, August 9, 2026 Local

    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 →

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
  • 1172 ft AGL at event
  • 149 kt ground speed
  • 0 fpm vertical
  • 10 kt wind
  • 2 kt crosswind component
  • 16,093 m visibility
  • KMCC 150055Z AUTO 23010KT 10SM CLR 27/12 A2994 RMK AO2

Flight context

  • C2701
  • C27J
  • KMCC → KMCC
  • 2026-08-08 02:02 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