Go-around — EJM4
KJAC · 192026-07-13 17:26 UTC· KSLC → KJAC· TETON HOLDINGS II LLC· GLF4
EJM4 (Teton Holdings II) was operating from KSLC to KJAC on 2026-07-13. SkyMeter detected a go-around at Jackson Hole Airport (KJAC) on runway 19 at 17:26 UTC. Trace data at the event: 7261 ft AGL, 176 kt GS. METAR at the time reported 4 kt wind, 2 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/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/2268 2026-07-01 13:00Z – 2026-07-14 03:00Z SFC–14,500 ft
27NM SE JACKSON, WY, Wednesday, July 1, 2026 through Tuesday, July 14, 2026 UTC
View FAA NOTAM → - SECURITY6/7862 2026-07-03 16:07Z – 2026-07-21 05:59Z SFC–400 ft
Salt Lake City, UT
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 19
- 7261 ft AGL at event
- 176 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KJAC 161556Z 29005KT 10SM FEW120 12/01 A3028 RMK AO2 SLP223 T01220006
Flight context
- EJM4
- Teton Holdings II
- GLF4
- KSLC → KJAC
- 2026-07-13 17:26 UTC
- KJAC runway 19
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