Go-around — UAL719
KRNO · 35L2026-06-26 04:42 UTC· KDEN → KRNO· UNITED AIRLINES INC· B738
UAL719 (United Airlines) was operating from KDEN to KRNO on 2026-06-26. SkyMeter detected a go-around at Reno Tahoe International Airport (KRNO) on runway 35L at 04:42 UTC. Trace data at the event: 4608 ft AGL, 169 kt GS. METAR at the time reported 4 kt wind, 4 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4164 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft
Sandy, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4167 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft
Salt Lake City, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/8549 2026-06-16 02:58Z – 2026-06-30 04:00Z SFC–12,000 ft
12NM NE GRAND JUNCTION, CO, Tuesday, June 16, 2026 through Tuesday, June 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/9412 2026-06-20 17:53Z – 2026-07-03 04:00Z SFC–11,000 ft
27NM SW PROVO, UT, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/9461 2026-06-21 12:00Z – 2026-07-04 04:00Z SFC–10,500 ft
3.5NM SW SALT LAKE CITY, UT, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/9460 2026-06-21 14:00Z – 2026-07-04 04:00Z SFC–11,000 ft
27NM SW PROVO, UT, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/9504 2026-06-21 14:14Z – 2026-07-05 15:00Z SFC–10,500 ft
10NM NE OGDEN, UT, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/9555 2026-06-22 12:00Z – 2026-07-04 04:00Z SFC–10,500 ft
3.5NM SW SALT LAKE CITY, UT, Monday, June 22, 2026 through Saturday, July 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/9562 2026-06-22 12:00Z – 2026-07-04 04:00Z SFC–10,500 ft
29NM NW TOOELE, UT, Monday, June 22, 2026 through Saturday, July 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/9582 2026-06-22 13:04Z – 2026-07-05 15:00Z SFC–10,500 ft
29NM NW TOOELE, UT, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/9592 2026-06-22 13:29Z – 2026-07-05 15:00Z SFC–10,500 ft
3.5NM SW SALT LAKE CITY, UT, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/9834 2026-06-22 19:21Z – 2026-07-05 15:00Z SFC–10,500 ft
4NM SW SALT LAKE CITY, UT, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/9985 2026-06-23 13:54Z – 2026-07-07 15:00Z SFC–11,000 ft
27NM SW PROVO, UT, Tuesday, June 23, 2026 through Tuesday, July 7, 2026 UTC
View FAA NOTAM → - HAZARDS6/0277 2026-06-24 12:00Z – 2026-07-08 04:00Z SFC–12,000 ft
2NM S RIFLE, CO, Wednesday, June 24, 2026 through Wednesday, July 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/0276 2026-06-24 15:00Z – 2026-07-07 04:00Z SFC–10,500 ft
4NM SW SALT LAKE CITY, UT, Wednesday, June 24, 2026 through Tuesday, July 7, 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.
Pilot review data
- Runway 35L
- 4608 ft AGL at event
- 169 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KRNO 171955Z 06004KT 10SM SCT090 22/M01 A3012 RMK AO2 SLP158 T02221006
Flight context
- UAL719
- United Airlines
- B738
- KDEN → KRNO
- 2026-06-26 04:42 UTC
- KRNO runway 35L
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