Go-around — N400JA
KTIX · 182026-08-28 15:36 UTC· KVBT → KTIX· JETAVIVA LLC· E55P
N400JA (Jetaviva) was operating from KVBT to KTIX on 2026-08-28. SkyMeter detected a go-around at Space Coast Regional Airport (KTIX) on runway 18 at 15:36 UTC. Trace data at the event: 707 ft AGL, 137 kt GS. METAR at the time reported 8 kt wind, 6 kt crosswind component, 6,437 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/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft
Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC
View FAA NOTAM → - SECURITY6/7271 2026-08-24 12:30Z – 2026-08-29 06:00Z SFC–2,500 ft
MAYPORT, FL, Monday, August 24, 2026 through Saturday, August 29, 2026 Local
View FAA NOTAM → - SECURITY6/6989 2026-08-27 21:00Z – 2026-09-02 21:00Z SFC–400 ft
Asheville, NC, Thursday, August 27, 2026 through Wednesday, September 2, 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 18
- 707 ft AGL at event
- 137 kt ground speed
- 0 fpm vertical
- 8 kt wind
- 6 kt crosswind component
- 6,437 m visibility
- KTIX 091747Z VRB06KT 4SM TSRA BKN020 A3015
Flight context
- N400JA
- Jetaviva
- E55P
- KVBT → KTIX
- 2026-08-28 15:36 UTC
- KTIX runway 18
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