Go-around — ROU1768

ROU1768 (Air Canada) was operating from CAM9 to KSFO on 2026-08-11. SkyMeter detected a go-around at San Francisco International Airport (KSFO) on runway 28L at 22:29 UTC. Trace data at the event: 210 ft AGL, 159 kt GS, 0 fpm vertical. METAR at the time reported 8 kt wind, 5 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/6145 2026-07-19 16:00Z – 2027-07-19 23:00Z SFC–1,000 ft

  Bellevue, WA, Sunday, July 19, 2026 through Monday, July 19, 2027 Local

  View FAA NOTAM →
• HAZARDS6/9888 2026-07-29 13:00Z – 2026-08-12 03:00Z SFC–6,000 ft

  20NM NW MEDFORD, OR, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0878 2026-08-02 01:15Z – 2026-08-15 05:00Z SFC–6,000 ft

  2NM NE GRANTS PASS, OR, Sunday, August 2, 2026 through Saturday, August 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0889 2026-08-02 05:00Z – 2026-08-15 05:00Z SFC–6,000 ft

  2NM NE GRANTS PASS, OR, Sunday, August 2, 2026 through Saturday, August 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0890 2026-08-02 13:00Z – 2026-08-15 03:00Z SFC–5,000 ft

  20NM NW MEDFORD, OR, Sunday, August 2, 2026 through Saturday, August 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0938 2026-08-02 15:28Z – 2026-08-16 04:00Z SFC–6,000 ft

  11NM SE UKIAH, CA, Sunday, August 2, 2026 through Sunday, August 16, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1969 2026-08-05 05:00Z – 2026-08-18 05:00Z SFC–6,000 ft

  2NM NE GRANTS PASS, OR, Wednesday, August 5, 2026 through Tuesday, August 18, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2493 2026-08-06 05:00Z – 2026-08-16 05:00Z SFC–9,500 ft

  35NM SE ROSEBURG, OR, Thursday, August 6, 2026 through Sunday, August 16, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2696 2026-08-06 19:30Z – 2026-08-21 03:00Z SFC–9,000 ft

  24NM NE VANCOUVER, WA, Thursday, August 6, 2026 through Friday, August 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2772 2026-08-07 03:45Z – 2026-08-20 05:00Z SFC–8,000 ft

  7NM SW MEDFORD, OR, Friday, August 7, 2026 through Thursday, August 20, 2026 UTC

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

  24NM NE VANCOUVER, WA, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3043 2026-08-08 18:32Z – 2026-08-22 04:00Z SFC–8,000 ft

  12NM N WILLOW CREEK, CA, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3088 2026-08-08 23:14Z – 2026-08-22 04:00Z SFC–9,000 ft

  12NM N WILLOW CREEK, CA, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3104 2026-08-09 05:00Z – 2026-08-23 13:00Z SFC–5,000 ft

  12NM N MEDFORD, OR, Sunday, August 9, 2026 through Sunday, August 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3107 2026-08-09 05:00Z – 2026-08-24 04:00Z SFC–8,000 ft

  7NM SW MEDFORD, OR, Sunday, August 9, 2026 through Monday, August 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3168 2026-08-10 06:45Z – 2026-08-25 04:00Z SFC–10,500 ft

  40NM SE PORTLAND, OR, Monday, August 10, 2026 through Tuesday, August 25, 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