Unstable approach — SKW3375

SKW3375 (Skywest Airlines) was operating from KSFO to KBOI on 2026-07-16. SkyMeter detected a low approach-stability score at Boise Air Terminal/Gowen Field (KBOI) on runway 27 at 03:47 UTC. Trace data at the event: 3918 ft AGL, 138 kt GS. Approach stability score: 44/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 4 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/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/7984 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft

  Oakland, CA

  View FAA NOTAM →
• HAZARDS6/3388 2026-07-07 14:00Z – 2026-07-21 04:00Z SFC–10,000 ft

  17NM NE WINNEMUCCA, NV, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC

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

  40NM NW BASQUE, OR, Wednesday, July 8, 2026 through Wednesday, July 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3798 2026-07-08 01:35Z – 2026-07-22 05:00Z SFC–10,000 ft

  40NM NW BASQUE, OR, Wednesday, July 8, 2026 through Wednesday, July 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3807 2026-07-08 15:00Z – 2026-07-22 15:00Z SFC–9,000 ft

  10NM SE FALL RIVER MILLS, CA, Wednesday, July 8, 2026 through Wednesday, July 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4014 2026-07-08 16:17Z – 2026-07-22 15:00Z SFC–9,000 ft

  10NM SE FALL RIVER MILLS, CA, Wednesday, July 8, 2026 through Wednesday, July 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4558 2026-07-10 04:00Z – 2026-07-21 15:00Z SFC–9,000 ft

  10NM SE FALL RIVER MILLS, CA, Friday, July 10, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4559 2026-07-10 04:00Z – 2026-07-21 15:00Z SFC–9,000 ft

  10NM SE FALL RIVER MILLS, CA, Friday, July 10, 2026 through Tuesday, July 21, 2026 UTC

  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/6064 2026-07-15 22:44Z – 2026-07-16 14:00Z SFC–10,000 ft

  41NM SE BURNS, OR, Wednesday, July 15, 2026 through Thursday, July 16, 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