Go-around — UAL1604

KRNO · 17R

2026-08-09 00:39 UTC· KDEN KRNO· UMB BANK NA TRUSTEE· A319

UAL1604 (UMB Bank NA) was operating from KDEN to KRNO on 2026-08-09. SkyMeter detected a go-around at Reno Tahoe International Airport (KRNO) on runway 17R at 00:39 UTC. Trace data at the event: 5837 ft AGL, 177 kt GS. METAR at the time reported 11 kt wind, 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.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • HAZARDS6/9393 2026-07-28 14:00Z – 2026-08-11 05:00Z SFC–13,000 ft

    60NM NE FALLON, NV, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9884 2026-07-29 12:00Z – 2026-08-12 04:00Z SFC–12,500 ft

    19NM NW GRAND JUNCTION, CO, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9879 2026-07-29 14:00Z – 2026-08-11 04:00Z SFC–13,000 ft

    60NM NE FALLON, NV, Wednesday, July 29, 2026 through Tuesday, August 11, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0406 2026-07-30 14:00Z – 2026-08-12 05:00Z SFC–13,000 ft

    60NM NE FALLON, NV, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0407 2026-07-30 14:00Z – 2026-08-12 05:00Z SFC–13,000 ft

    60NM NE FALLON, NV, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0722 2026-08-01 13:00Z – 2026-08-14 04:00Z SFC–14,000 ft

    9NM S ELY, NV, Saturday, August 1, 2026 through Friday, August 14, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0881 2026-08-02 13:00Z – 2026-08-16 03:00Z SFC–14,000 ft

    26NM SW PRICE, UT, Sunday, August 2, 2026 through Sunday, August 16, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/1038 2026-08-03 13:00Z – 2026-08-16 04:00Z SFC–14,000 ft

    9NM S ELY, NV, Monday, August 3, 2026 through Sunday, August 16, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/1961 2026-08-05 13:00Z – 2026-08-19 04:00Z SFC–14,000 ft

    9NM S ELY, NV, Wednesday, August 5, 2026 through Wednesday, August 19, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2768 2026-08-07 14:00Z – 2026-08-22 04:00Z SFC–12,500 ft

    8NM SW RIFLE, CO, Friday, August 7, 2026 through Saturday, August 22, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2913 2026-08-08 14:00Z – 2026-08-22 04:00Z SFC–12,500 ft

    10NM SW RIFLE, CO, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2914 2026-08-08 14:00Z – 2026-08-22 04:00Z SFC–6,500 ft

    8NM W RIFLE, CO, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/1985 2026-08-08 22:30Z – 2026-08-10 06:00Z SFC–400 ft

    Denver, CO, Saturday, August 8, 2026 through Monday, August 10, 2026 Local

    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.

Pilot review data

  • Runway 17R
  • 5837 ft AGL at event
  • 177 kt ground speed
  • 0 fpm vertical
  • 11 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KRNO 161855Z 18012G21KT 10SM FEW030 FEW075 24/M08 A3001 RMK AO2 SLP112 FU FEW030 FU PLUME W T02441078

Flight context

  • UAL1604
  • UMB Bank NA
  • A319
  • KDEN → KRNO
  • 2026-08-09 00:39 UTC
  • KRNO runway 17R

All events on this flight

Go-around 00:39:07 UTC · KRNO runway 17R · 5,837 ft AGL · 177 kt GS
Go-around 00:39:07 UTC · KRNO runway 17R · 5,837 ft AGL · 177 kt GS

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

SkyMeter · trace data observed via ADS-B· KRNO