Go-around — SKW4739

SKW4739 (Skywest Airlines) was operating from KRDM to KSFO on 2026-07-20. SkyMeter detected a go-around at San Francisco International Airport (KSFO) on runway 28L at 00:11 UTC. Trace data at the event: 213 ft AGL, 114 kt GS, 0 fpm vertical. METAR at the time reported 6 kt wind, 2 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 →
• 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/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 →
• SECURITY6/7984 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft

  Oakland, CA

  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/6388 2026-07-17 02:26Z – 2026-07-31 04:00Z SFC–10,000 ft

  63NM NE REDDING, CA, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6393 2026-07-17 02:30Z – 2026-07-31 04:00Z SFC–10,000 ft

  63NM NE REDDING, CA, 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/6434 2026-07-17 05:07Z – 2026-08-01 04:00Z SFC–10,000 ft

  63NM NE REDDING, CA, Friday, July 17, 2026 through Saturday, August 1, 2026 UTC

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

  63NM NE REDDING, CA, Friday, July 17, 2026 through Saturday, August 1, 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 →

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