Go-around — ASA1476

ASA1476 (Alaska Airlines) was operating from KSMF to KSEA on 2026-08-04. SkyMeter detected a go-around at Seattle Tacoma International Airport (KSEA) on runway 34L at 22:41 UTC. Trace data at the event: 575 ft AGL, 150 kt GS. METAR at the time reported 6 kt wind, 4 kt crosswind component, 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/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 →
• HAZARDS6/8326 2026-07-24 00:00Z – 2026-08-05 05:00Z SFC–10,000 ft

  35NM E ROSEBURG, OR, Friday, July 24, 2026 through Wednesday, August 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8423 2026-07-24 16:00Z – 2026-08-07 04:00Z SFC–9,500 ft

  35NM SE ROSEBURG, OR, Friday, July 24, 2026 through Friday, August 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8438 2026-07-24 18:30Z – 2026-08-08 04:00Z SFC–9,500 ft

  25NM SW THE DALLES, OR, Friday, July 24, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8485 2026-07-24 23:00Z – 2026-08-08 04:00Z SFC–9,000 ft

  49NM W YAKIMA, WA, Friday, July 24, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8490 2026-07-25 01:45Z – 2026-08-08 04:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Saturday, July 25, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8555 2026-07-25 19:00Z – 2026-08-09 05:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8581 2026-07-26 05:00Z – 2026-08-09 05:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Sunday, July 26, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8585 2026-07-26 14:00Z – 2026-08-09 05:00Z SFC–9,500 ft

  25NM SW THE DALLES, OR, Sunday, July 26, 2026 through Sunday, August 9, 2026 UTC

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

  10NM W MADRAS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9852 2026-07-29 00:30Z – 2026-08-12 04:00Z SFC–9,000 ft

  17NM NW REDMOND, OR, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9939 2026-07-29 14:00Z – 2026-08-12 04:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0415 2026-07-30 15:00Z – 2026-08-12 05:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0573 2026-07-31 04:00Z – 2026-08-12 04:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Friday, July 31, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0581 2026-07-31 05:30Z – 2026-08-14 04:00Z SFC–10,500 ft

  25NM SW THE DALLES, OR, Friday, July 31, 2026 through Friday, August 14, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0952 2026-08-02 17:00Z – 2026-08-16 05:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Sunday, August 2, 2026 through Sunday, August 16, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1476 2026-08-04 05:00Z – 2026-08-19 05:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Tuesday, August 4, 2026 through Wednesday, August 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1478 2026-08-04 05:00Z – 2026-08-18 05:00Z SFC–10,500 ft

  25NM SW THE DALLES, OR, Tuesday, August 4, 2026 through Tuesday, August 18, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1681 2026-08-04 16:00Z – 2026-08-19 05:00Z SFC–10,500 ft

  25NM SW THE DALLES, OR, Tuesday, August 4, 2026 through Wednesday, August 19, 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