BACN31 was operating from KWRB to KWRB on 2026-08-14. SkyMeter detected a go-around at Patrick Air Force Base (KCOF) on runway 03 at 15:29 UTC. Trace data at the event: 194 ft AGL, 129 kt GS, 0 fpm vertical. METAR at the time reported 3 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/2968 2026-08-10 12:30Z – 2026-08-15 06:00Z SFC–2,500 ft
MAYPORT, FL, Monday, August 10, 2026 through Saturday, August 15, 2026 Local
View FAA NOTAM → - SECURITY6/3199 2026-08-12 05:00Z – 2026-08-15 09:30Z SFC–17,999 ft
Macon, GA, Wednesday, August 12, 2026 through Saturday, August 15, 2026 Local
View FAA NOTAM → - SECURITY6/3974 2026-08-13 05:00Z – 2026-08-15 09:30Z SFC–17,999 ft
Macon, GA, Thursday, August 13, 2026 through Saturday, August 15, 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 03
- 194 ft AGL at event
- 129 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KCOF 152055Z AUTO 14010KT 10SM FEW150 31/26 A3011 RMK AO2 SLP201 60000 T03140262 58013 $
Flight context
- BACN31
- GLEX
- KWRB → KWRB
- 2026-08-14 15:29 UTC
- KCOF runway 03
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