Unstable approach — CFR641

KMCC · 16

2026-07-19 04:02 UTC· KMCC → KMCC· STATE OF CALIFORNIA, DEPT OF FORESTRY & FIRE PROTECTION· BE20

▶ Replay 📊 Analyse

CFR641 (State of California) was operating from KMCC to KMCC on 2026-07-19. SkyMeter detected a low approach-stability score at Mc Clellan Airfield (KMCC) on runway 16 at 04:02 UTC. Trace data at the event: 1163 ft AGL, 119 kt GS. Approach stability score: 52/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 7 kt wind, 1 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/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/6388 2026-07-17 02:26Z – 2026-07-31 04:00Z SFC–10,000 ft

    63NM NE REDDING, CA, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6393 2026-07-17 02:30Z – 2026-07-31 04:00Z SFC–10,000 ft

    63NM NE REDDING, CA, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6411 2026-07-17 04:44Z – 2026-07-19 04:00Z SFC–10,000 ft

    63NM NE REDDING, CA, Friday, July 17, 2026 through Sunday, July 19, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6434 2026-07-17 05:07Z – 2026-08-01 04:00Z SFC–10,000 ft

    63NM NE REDDING, CA, Friday, July 17, 2026 through Saturday, August 1, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6433 2026-07-17 05:08Z – 2026-08-01 04:00Z SFC–10,000 ft

    63NM NE REDDING, CA, Friday, July 17, 2026 through Saturday, August 1, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6704 2026-07-18 22:29Z – 2026-07-21 04:00Z SFC–10,500 ft

    16NM NE SUSANVILLE, CA, Saturday, July 18, 2026 through Tuesday, July 21, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6738 2026-07-19 03:43Z – 2026-07-23 04:00Z SFC–6,500 ft

    7NM NE REDDING, CA, Sunday, July 19, 2026 through Thursday, July 23, 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
  • 1163 ft AGL at event
  • 119 kt ground speed
  • 0 fpm vertical
  • Approach stability 52/100
  • 7 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KMCC 162155Z AUTO 20011G20KT 10SM CLR 25/10 A2990 RMK AO2

Flight context

  • CFR641
  • State of California
  • BE20
  • KMCC → KMCC
  • 2026-07-19 04: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