None was operating from KNIP to KAVL on 2026-06-25. SkyMeter detected a go-around at Asheville Regional Airport (KAVL) on runway 35 at 14:01 UTC. Trace data at the event: 4286 ft AGL, 171 kt GS. METAR at the time reported 4 kt wind, 1 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/4004 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHARLOTTE, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4007 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Charlotte, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/9513 2026-06-22 12:30Z – 2026-06-26 06:00Z SFC–2,500 ft
MAYPORT, FL, Monday, June 22, 2026 through Friday, June 26, 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 35
- 4286 ft AGL at event
- 171 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KAVL 172154Z VRB05KT 10SM CLR 29/16 A3029 RMK AO2 SLP229 T02940161
Flight context
- None
- P8
- KNIP → KAVL
- 2026-06-25 14:01 UTC
- KAVL runway 35
All events on this flight
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