Go-around — ASA1561

ASA1561 (Alaska Airlines) was operating from PANC to KSFO on 2026-07-21. SkyMeter detected a go-around at San Francisco International Airport (KSFO) on runway 28L at 03:30 UTC. Trace data at the event: 474 ft AGL, 155 kt GS, 0 fpm vertical. METAR at the time reported 13 kt wind, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.

• SECURITY6/4011 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  BELLEVUE, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4013 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Seattle, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4033 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  RENTON, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4034 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Renton, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4040 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Portland, OR, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4041 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  PORTLAND, OR, 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/7984 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft

  Oakland, CA

  View FAA NOTAM →
• SECURITY6/8071 2026-07-08 16:07Z – 2026-07-21 06:59Z SFC–400 ft

  PORTLAND, OR

  View FAA NOTAM →
• HAZARDS6/4243 2026-07-09 14:00Z – 2026-07-23 14:00Z SFC–10,000 ft

  2NM N HOOPA, CA, Thursday, July 9, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4266 2026-07-09 14:00Z – 2026-07-23 14:00Z SFC–10,000 ft

  2NM N HOOPA, CA, Thursday, July 9, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• SECURITY6/8073 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft

  Renton, WA

  View FAA NOTAM →
• SECURITY6/8074 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft

  Renton, WA

  View FAA NOTAM →
• SECURITY6/8080 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft

  Seattle, WA

  View FAA NOTAM →
• SECURITY6/8081 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft

  Bellevue, WA

  View FAA NOTAM →
• HAZARDS6/6363 2026-07-17 01:54Z – 2026-07-31 04:00Z SFC–8,000 ft

  20NM NW MEDFORD, OR, 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/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/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 →
• SECURITY6/6147 2026-07-19 16:00Z – 2026-07-24 04:00Z SFC–1,000 ft

  Bellevue, WA, Sunday, July 19, 2026 through Thursday, July 23, 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.

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