EJA801 (Netjets Sales) was operating from KTUS to KAUS on 2026-05-18. SkyMeter detected a go-around at Austin Bergstrom International Airport (KAUS) on runway 18L at 19:12 UTC. Trace data at the event: 702 ft AGL, 142 kt GS. METAR at the time reported 16 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/4165 2026-02-14 07:00Z – 2026-08-15 06:59Z SFC–400 ft

    Nogales, AZ, Saturday, February 14, 2026 through Friday, August 14, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft

    SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 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 18L
  • 702 ft AGL at event
  • 142 kt ground speed
  • 0 fpm vertical
  • 16 kt wind
  • 2 kt crosswind component
  • 16,093 m visibility
  • KAUS 200853Z 19003KT 10SM FEW300 24/21 A2995 RMK AO2 SLP129 T02390211 58001 $

Flight context

  • EJA801
  • Netjets Sales
  • C700
  • KTUS → KAUS
  • 2026-05-18 19:12 UTC
  • KAUS runway 18L

All events on this flight

Go-around 19:12:16 UTC · KAUS runway 18L · 702 ft AGL · 142 kt GS
Go-around 19:12:16 UTC · KAUS runway 18L · 702 ft AGL · 142 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· KAUS