Go-around — SKW6332

SKW6332 (Skywest Airlines) was operating from KPHX to KBOI on 2026-07-19. SkyMeter detected a go-around at Boise Air Terminal/Gowen Field (KBOI) on runway 10R at 07:07 UTC. Trace data at the event: 3458 ft AGL, 163 kt GS. METAR at the time reported 3 kt wind, 1 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/4158 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

  MERIDIAN, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Boise, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Sandy, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Salt Lake City, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3948 2026-06-01 07:00Z – 2026-07-21 06:59Z

  MESA, AZ, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

  Mesa, AZ

  View FAA NOTAM →
• SECURITY6/7864 2026-07-03 15:07Z – 2026-07-21 05:59Z SFC–400 ft

  Sandy, UT

  View FAA NOTAM →
• SECURITY6/7862 2026-07-03 16:07Z – 2026-07-21 05:59Z SFC–400 ft

  Salt Lake City, UT

  View FAA NOTAM →
• HAZARDS6/3016 2026-07-06 14:00Z – 2026-07-20 04:00Z SFC–11,000 ft

  7NM SW FLAGSTAFF, AZ, Monday, July 6, 2026 through Monday, July 20, 2026 UTC

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

  7NM SW FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC

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

  7NM SW FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3812 2026-07-08 02:09Z – 2026-07-21 04:00Z SFC–12,000 ft

  6NM S SCIPIO, UT, Wednesday, July 8, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• SECURITY6/7869 2026-07-09 11:07Z – 2026-07-21 05:59Z SFC–400 ft

  Meridian, ID

  View FAA NOTAM →
• SECURITY6/7871 2026-07-09 11:07Z – 2026-07-21 05:59Z SFC–400 ft

  Boise, ID

  View FAA NOTAM →
• HAZARDS6/4555 2026-07-10 14:00Z – 2026-07-23 04:00Z SFC–10,500 ft

  44NM NE WELLS, NV, Friday, July 10, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4975 2026-07-12 13:00Z – 2026-07-26 04:00Z SFC–12,000 ft

  9NM SE DUGWAY, UT, Sunday, July 12, 2026 through Sunday, July 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5155 2026-07-13 13:00Z – 2026-07-26 04:00Z SFC–11,000 ft

  40NM NE WELLS, NV, Monday, July 13, 2026 through Sunday, July 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6221 2026-07-16 17:58Z – 2026-07-30 04:00Z SFC–12,000 ft

  9NM SE DUGWAY, UT, Thursday, July 16, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6358 2026-07-17 13:00Z – 2026-07-31 04:00Z SFC–12,000 ft

  9NM SE DUGWAY, UT, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6359 2026-07-17 14:00Z – 2026-07-31 03:00Z SFC–15,500 ft

  5NM E BEAVER, UT, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6569 2026-07-18 14:00Z – 2026-07-31 03:00Z SFC–15,500 ft

  5NM E BEAVER, UT, Saturday, July 18, 2026 through Friday, July 31, 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