Go-around — TITAN10

KDYS · 16

2026-07-12 15:56 UTC· 93TX → KDYS· C30J

▶ Replay 📊 Analyse

TITAN10 was operating from 93TX to KDYS on 2026-07-12. SkyMeter detected a go-around at Dyess Air Force Base (KDYS) on runway 16 at 15:56 UTC. Trace data at the event: 2151 ft AGL, 134 kt GS. METAR at the time reported 6 kt wind, 3 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/4002 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

    FORT WORTH, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/6842 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft

    Fort Worth, TX

    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 16
  • 2151 ft AGL at event
  • 134 kt ground speed
  • 0 fpm vertical
  • 6 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • KDYS 170555Z AUTO 16008KT 10SM CLR 28/16 A3018 RMK AO2 SLP189 T02810157 10357 20278 403800243 50007

Flight context

  • TITAN10
  • C30J
  • 93TX → KDYS
  • 2026-07-12 15:56 UTC
  • KDYS runway 16

All events on this flight

Go-around 15:56:59 UTC · KDYS runway 16 · 2,151 ft AGL · 134 kt GS
Go-around 16:32:20 UTC · KDYS runway 16 · 1,989 ft AGL · 141 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· KDYS