Unstable approach — N541SC

N541SC (King AIR N541sc) was operating from NV60 to KMRY on 2026-08-29. SkyMeter detected a low approach-stability score at Monterey Peninsula Airport (KMRY) on runway 10R at 17:51 UTC. Trace data at the event: 1370 ft AGL, 144 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 8 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.

• 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 →
• 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 →
• UAS PUBLIC GATHERING6/7555 2026-08-29 01:00Z – 2026-09-02 06:59Z SFC–400 ft

  Santa Clara, CA, Saturday, August 29, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/7569 2026-08-29 01:00Z – 2026-09-02 06:59Z SFC–400 ft

  Santa Clara, CA, Saturday, August 29, 2026 through Wednesday, September 2, 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