Go-around — None

KAVL · 35

2026-07-27 17:21 UTC· KNIP KAVL· P8

None was operating from KNIP to KAVL on 2026-07-27. SkyMeter detected a go-around at Asheville Regional Airport (KAVL) on runway 35 at 17:21 UTC. Trace data at the event: 2539 ft AGL, 163 kt GS. METAR at the time reported 10 kt wind, 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)
  • HAZARDS6/8779 2026-07-26 18:03Z – 2026-08-02 01:30Z SFC–1,300 ft

    16NM NE LAKE CITY, FL, Sunday, July 26, 2026 through Sunday, August 2, 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 35
  • 2539 ft AGL at event
  • 163 kt ground speed
  • 0 fpm vertical
  • 10 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KAVL 140754Z AUTO 00000KT 10SM CLR 21/19 A3013 RMK AO2 SLP175 T02060194

Flight context

  • None
  • P8
  • KNIP → KAVL
  • 2026-07-27 17:21 UTC
  • KAVL runway 35

All events on this flight

Go-around 17:21:25 UTC · KAVL runway 35 · 2,539 ft AGL · 163 kt GS
Go-around 17:31:45 UTC · KAVL runway 35 · 2,293 ft AGL · 149 kt GS
Go-around 17:21:25 UTC · KAVL runway 35 · 2,539 ft AGL · 163 kt GS
Go-around 17:31:45 UTC · KAVL runway 35 · 2,293 ft AGL · 149 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· KAVL