EJA414 (Netjets Sales) was operating from KJWN to KOMA on 2026-06-08. SkyMeter detected a go-around at Eppley Airfield (KOMA) on runway 14L at 23:40 UTC. Trace data at the event: 1574 ft AGL, 169 kt GS. METAR at the time reported 5 kt wind, 5 kt crosswind component, 11,265 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/3954 2026-06-01 00:00Z – 2026-07-20 23:59Z

    STILLWATER, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/4134 2026-06-01 00:00Z – 2026-07-20 23:59Z

    TULSA, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

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

    Stillwater, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    CLAYTON, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Tulsa, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Kansas City, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Riverside, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    PRAIRIE VILLAGE, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    St, Louis, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/5819 2026-06-08 13:00Z – 2026-06-10 21:00Z SFC–1,000 ft

    JEFFERSON CITY, MO, Monday, June 8, 2026 through Wednesday, June 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 14L
  • 1574 ft AGL at event
  • 169 kt ground speed
  • 0 fpm vertical
  • 5 kt wind
  • 5 kt crosswind component
  • 11,265 m visibility
  • KOMA 181352Z 15011KT 7SM OVC008 23/22 A3008 RMK AO2 SLP180 T02330217

Flight context

  • EJA414
  • Netjets Sales
  • E55P
  • KJWN → KOMA
  • 2026-06-08 23:40 UTC
  • KOMA runway 14L

All events on this flight

Go-around 23:40:39 UTC · KOMA runway 14L · 1,574 ft AGL · 169 kt GS
Go-around 23:40:39 UTC · KOMA runway 14L · 1,574 ft AGL · 169 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· KOMA