Go-around — N800AR

N800AR (Perpetual Aviation) was operating from KHOU to KSFO on 2026-05-29. SkyMeter detected a go-around at San Francisco International Airport (KSFO) on runway 28R at 23:16 UTC. Trace data at the event: 483 ft AGL, 133 kt GS, 0 fpm vertical. METAR at the time reported 7 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.

• SECURITY5/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft

  Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 2026 Local

  View FAA NOTAM →
• SECURITY6/0091 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft

  Coyote Wells, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local

  View FAA NOTAM →
• SECURITY6/0092 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft

  CALEXICO, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local

  View FAA NOTAM →
• SECURITY6/4165 2026-02-14 07:00Z – 2026-08-15 06:59Z SFC–400 ft

  Nogales, AZ, Saturday, February 14, 2026 through Friday, August 14, 2026 Local

  View FAA NOTAM →
• SECURITY6/4160 2026-02-14 08:00Z – 2026-08-15 06:59Z SFC–400 ft

  Chula Vista, CA, Saturday, February 14, 2026 through Friday, August 14, 2026 Local

  View FAA NOTAM →
• SECURITY6/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft

  SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• HAZARDS6/0887 2026-05-16 18:37Z – 2026-05-30 04:00Z SFC–10,500 ft

  19NM SW TUCUMCARI, NM, Saturday, May 16, 2026 through Saturday, May 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1015 2026-05-18 00:28Z – 2026-06-01 04:00Z SFC–15,500 ft

  22NM NE RUIDOSO, NM, Monday, May 18, 2026 through Monday, June 1, 2026 UTC

  View FAA NOTAM →
• SECURITY6/0758 2026-05-18 07:01Z – 2026-05-31 06:59Z SFC–1,499 ft

  Concord, CA, Monday, May 18, 2026 through Saturday, May 30, 2026 Local

  View FAA NOTAM →
• HAZARDS6/1359 2026-05-18 20:54Z – 2026-05-31 16:00Z SFC–6,000 ft

  3NM S SIMI VALLEY, CA, Monday, May 18, 2026 through Sunday, May 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1358 2026-05-19 00:52Z – 2026-06-02 02:00Z SFC–10,000 ft

  5NM S CAMPO, CO, Tuesday, May 19, 2026 through Tuesday, June 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1376 2026-05-19 02:58Z – 2026-05-31 15:00Z SFC–6,000 ft

  3NM S SIMI VALLEY, CA, Tuesday, May 19, 2026 through Sunday, May 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1626 2026-05-19 22:38Z – 2026-06-02 04:00Z SFC–15,500 ft

  22NM NE RUIDOSO, NM, Tuesday, May 19, 2026 through Tuesday, June 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2366 2026-05-22 06:00Z – 2026-06-05 04:00Z SFC–10,000 ft

  12NM S PRESCOTT, AZ, Friday, May 22, 2026 through Friday, June 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2354 2026-05-22 12:00Z – 2026-06-04 04:00Z SFC–15,500 ft

  22NM NE RUIDOSO, NM, Friday, May 22, 2026 through Thursday, June 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2573 2026-05-25 15:00Z – 2026-06-06 03:00Z SFC–8,000 ft

  32NM SW SANTA BARBARA, CA, Monday, May 25, 2026 through Saturday, June 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2830 2026-05-25 15:45Z – 2026-06-11 16:00Z SFC–5,000 ft

  GARDEN GROVE, CA, Monday, May 25, 2026 through Thursday, June 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2866 2026-05-25 22:04Z – 2026-06-08 03:00Z SFC–13,000 ft

  24NM NE DOUGLAS, AZ, Monday, May 25, 2026 through Monday, June 8, 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.

All events on this flight

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