Unstable approach — FFL938

FFL938 (Efficiency Aloft) was inbound to KSTS on 2026-07-23. SkyMeter detected a low approach-stability score at Charles M. Schulz Sonoma County Airport (KSTS) on runway 14 at 01:15 UTC. Trace data at the event: 1217 ft AGL, 148 kt GS. Approach stability score: 56/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 10 kt wind, 9 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.

• 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 →
• 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 →
• HAZARDS6/4964 2026-07-12 00:13Z – 2026-07-26 03:00Z SFC–10,500 ft

  3NM N LOYALTON, CA, Sunday, July 12, 2026 through Sunday, July 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4978 2026-07-12 13:00Z – 2026-07-26 13:00Z SFC–10,500 ft

  3NM N LOYALTON, CA, Sunday, July 12, 2026 through Sunday, July 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5054 2026-07-12 14:45Z – 2026-07-26 13:00Z SFC–12,500 ft

  3NM N LOYALTON, CA, Sunday, July 12, 2026 through Sunday, July 26, 2026 UTC

  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/6409 2026-07-17 04:39Z – 2026-07-30 07:00Z SFC–11,000 ft

  10NM SW MOUNT SHASTA, CA, Friday, July 17, 2026 through Thursday, July 30, 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/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 →
• HAZARDS6/6733 2026-07-19 12:00Z – 2026-08-02 04:00Z SFC–10,500 ft

  16NM NE SUSANVILLE, CA, Sunday, July 19, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6741 2026-07-19 12:00Z – 2026-08-02 04:00Z SFC–6,500 ft

  7NM NE REDDING, CA, Sunday, July 19, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6774 2026-07-19 18:27Z – 2026-08-02 04:00Z SFC–10,500 ft

  22NM NE SUSANVILLE, CA, Sunday, July 19, 2026 through Sunday, August 2, 2026 UTC

  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 →
• HAZARDS6/7854 2026-07-22 17:23Z – 2026-08-05 04:00Z SFC–7,000 ft

  9NM NW GRASS VALLEY DISPATCH CENTER, CA, Wednesday, July 22, 2026 through Wednesday, August 5, 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.

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