N103AK was inbound to KSBA on 2026-06-26. SkyMeter detected a low approach-stability score at Santa Barbara Municipal Airport (KSBA) on runway 25 at 02:07 UTC. Trace data at the event: 1134 ft AGL, 160 kt GS. Approach stability score: 40/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 11 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/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/4052 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4054 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4060 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Oakland, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4061 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
BERKLEY, CA, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local
View FAA NOTAM → - SECURITY6/4192 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Santa Barbara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4204 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Santa Clara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/9305 2026-06-19 03:51Z – 2026-07-02 02:30Z SFC–8,000 ft
30NM W BAKERSFIELD, CA, Friday, June 19, 2026 through Thursday, July 2, 2026 UTC
View FAA NOTAM → - HAZARDS6/0278 2026-06-24 04:32Z – 2026-06-30 05:00Z SFC–8,000 ft
16NM S ALTURAS, CA, Wednesday, June 24, 2026 through Tuesday, June 30, 2026 UTC
View FAA NOTAM → - SPACE OPERATIONS6/0756 2026-06-25 16:25Z – 2026-06-26 05:00Z SFC–10,000 ft
56 ZSE AIRSPACE BROTHERS, OR, Thursday, June 25, 2026 through Friday, June 26, 2026 UTC
View FAA NOTAM → - SECURITY6/9689 2026-06-25 23:00Z – 2026-06-26 08:00Z SFC–3,000 ft
San Francisco, CA, Thursday, June 25, 2026 through Friday, June 26, 2026 Local
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 25
- 1134 ft AGL at event
- 160 kt ground speed
- 0 fpm vertical
- Approach stability 40/100
- 11 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KSBA 090530Z AUTO 00000KT 10SM CLR 18/16 A2981 RMK T01800160 MADISHF
Flight context
- N103AK
- GLF5
- 2026-06-26 02:07 UTC
- KSBA runway 25
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