Go-around — DAL2955

DAL2955 (Delta AIR Lines) was operating from KSEA to KLAS on 2026-06-25. SkyMeter detected a go-around at McCarran International Airport (KLAS) on runway 08R at 01:38 UTC. Trace data at the event: 2304 ft AGL, 154 kt GS. METAR at the time reported 14 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/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/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/4033 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  RENTON, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 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 →
• HAZARDS6/8221 2026-06-14 20:07Z – 2026-06-28 03:00Z SFC–6,000 ft

  22NM SE RICHLAND, WA, Sunday, June 14, 2026 through Sunday, June 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8252 2026-06-15 04:35Z – 2026-06-26 04:00Z SFC–5,500 ft

  12NM NE PASCO, WA, Monday, June 15, 2026 through Friday, June 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8253 2026-06-15 15:00Z – 2026-06-30 05:00Z SFC–6,000 ft

  3NM W BENTON CITY, WA, Monday, June 15, 2026 through Tuesday, June 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9121 2026-06-18 13:00Z – 2026-07-01 05:00Z SFC–7,000 ft

  10NM SE PENDLETON, OR, Thursday, June 18, 2026 through Wednesday, July 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8821 2026-06-18 14:00Z – 2026-07-02 05:00Z SFC–7,500 ft

  34NM SE COEUR D'ALENE, ID, Thursday, June 18, 2026 through Thursday, July 2, 2026 UTC

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

  37NM SW GRANGEVILLE, ID, Monday, June 22, 2026 through Monday, July 6, 2026 UTC

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

  37NM SW GRANGEVILLE, ID, Monday, June 22, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0278 2026-06-24 04:32Z – 2026-06-30 05:00Z SFC–8,000 ft

  16NM S ALTURAS, CA, Wednesday, June 24, 2026 through Tuesday, June 30, 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