Go-around — MXY614
KOGD · 032026-07-16 18:06 UTC· KSNA → KOGD· WILMINGTON TRUST CO TRUSTEE· BCS3
MXY614 (Wilmington Trust) was operating from KSNA to KOGD on 2026-07-16. SkyMeter detected a go-around at Ogden Hinckley Airport (KOGD) on runway 03 at 18:06 UTC. Trace data at the event: 5237 ft AGL, 189 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/4182 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Irvine, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4198 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
IRVINE, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/2845 2026-07-04 00:10Z – 2026-07-17 04:00Z SFC–12,500 ft
6NM S SCIPIO, UT, Saturday, July 4, 2026 through Friday, July 17, 2026 UTC
View FAA NOTAM → - HAZARDS6/3016 2026-07-06 14:00Z – 2026-07-20 04:00Z SFC–11,000 ft
7NM SW FLAGSTAFF, AZ, Monday, July 6, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3339 2026-07-07 14:00Z – 2026-07-21 04:00Z SFC–11,000 ft
7NM SW FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/3388 2026-07-07 14:00Z – 2026-07-21 04:00Z SFC–10,000 ft
17NM NE WINNEMUCCA, NV, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/3393 2026-07-07 14:00Z – 2026-07-21 04:00Z SFC–11,000 ft
7NM SW FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/3812 2026-07-08 02:09Z – 2026-07-21 04:00Z SFC–12,000 ft
6NM S SCIPIO, UT, Wednesday, July 8, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/4554 2026-07-10 02:28Z – 2026-07-17 04:00Z SFC–15,500 ft
8NM E BEAVER, UT, Friday, July 10, 2026 through Friday, July 17, 2026 UTC
View FAA NOTAM → - HAZARDS6/4895 2026-07-10 23:19Z – 2026-07-24 23:00Z SFC–10,500 ft
3NM W PIÑON HILLS, CA, Friday, July 10, 2026 through Friday, July 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/4907 2026-07-11 15:00Z – 2026-07-24 23:00Z SFC–10,500 ft
3NM W PIÑON HILLS, CA, Saturday, July 11, 2026 through Friday, July 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/4975 2026-07-12 13:00Z – 2026-07-26 04:00Z SFC–12,000 ft
9NM SE DUGWAY, UT, Sunday, July 12, 2026 through Sunday, July 26, 2026 UTC
View FAA NOTAM → - SECURITY6/7833 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft
Irvine, CA
View FAA NOTAM → - HAZARDS6/5145 2026-07-13 00:57Z – 2026-07-26 07:45Z SFC–8,500 ft
3NM W PIÑON HILLS, CA, Monday, July 13, 2026 through Sunday, July 26, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/3523 2026-07-14 15:00Z – 2026-07-20 06:00Z SFC–400 ft
Pomona, CA, Tuesday, July 14, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/6221 2026-07-16 17:58Z – 2026-07-30 04:00Z SFC–12,000 ft
9NM SE DUGWAY, UT, Thursday, July 16, 2026 through Thursday, July 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.
Pilot review data
- Runway 03
- 5237 ft AGL at event
- 189 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KOGD 162153Z 35005KT 10SM -RA FEW035 FEW065 SCT120 27/11 A3004 RMK AO2 RAB51 SLP114 P0000 T02670111
Flight context
- MXY614
- Wilmington Trust
- BCS3
- KSNA → KOGD
- 2026-07-16 18:06 UTC
- KOGD runway 03
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