Go-around — FFT3449

FFT3449 (Wells Fargo Trust Co NA) was inbound to KLAS on 2026-06-25. SkyMeter detected a go-around at McCarran International Airport (KLAS) on runway 26L at 03:46 UTC. Trace data at the event: 2899 ft AGL, 136 kt GS. METAR at the time reported 6 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/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/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/3966 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Mesa, AZ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• HAZARDS6/7455 2026-06-11 05:00Z – 2026-06-25 05:00Z SFC–14,000 ft

  80NM N SILVER CITY, NM, Thursday, June 11, 2026 through Thursday, June 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7894 2026-06-12 14:43Z – 2026-06-25 04:00Z SFC–14,000 ft

  80NM N SILVER CITY, NM, Friday, June 12, 2026 through Thursday, June 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8704 2026-06-16 17:05Z – 2026-06-29 05:00Z SFC–11,500 ft

  10NM N TUCSON, AZ, Tuesday, June 16, 2026 through Monday, June 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8804 2026-06-17 05:00Z – 2026-06-30 05:00Z SFC–11,500 ft

  10NM N TUCSON, AZ, Wednesday, June 17, 2026 through Tuesday, June 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8795 2026-06-17 15:00Z – 2026-06-29 04:00Z SFC–11,000 ft

  58NM S ST. GEORGE, UT, Wednesday, June 17, 2026 through Monday, June 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9123 2026-06-18 12:00Z – 2026-06-30 05:00Z SFC–14,000 ft

  80NM N SILVER CITY, NM, Thursday, June 18, 2026 through Tuesday, June 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9125 2026-06-18 14:00Z – 2026-07-02 04:00Z SFC–10,000 ft

  45NM E MESA, AZ, Thursday, June 18, 2026 through Thursday, July 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9293 2026-06-19 13:00Z – 2026-07-02 05:00Z

  10NM N TUCSON, AZ, Friday, June 19, 2026 through Thursday, July 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9309 2026-06-19 13:19Z – 2026-07-02 05:00Z SFC–10,500 ft

  10NM N TUCSON, AZ, Friday, June 19, 2026 through Thursday, July 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9342 2026-06-20 00:21Z – 2026-07-02 04:00Z SFC–13,500 ft

  30NM N SILVER CITY, NM, Saturday, June 20, 2026 through Thursday, July 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9455 2026-06-21 14:00Z – 2026-07-05 04:00Z SFC–9,000 ft

  14NM E PAYSON, AZ, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9496 2026-06-21 14:00Z – 2026-07-05 03:00Z SFC–13,000 ft

  33NM W SHOW LOW, AZ, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC

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

  16NM NE SAN CARLOS, AZ, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC

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

  45NM E MESA, AZ, Tuesday, June 23, 2026 through Monday, July 6, 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