CNV836 was operating from KNTD to KNZY on 2026-07-24. SkyMeter detected a go-around at Vandenberg Air Force Base (KVBG) on runway 30 at 19:51 UTC. Trace data at the event: 462 ft AGL, 152 kt GS, 0 fpm vertical. METAR at the time reported 14 kt wind, 5 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)- HAZARDS6/4895 2026-07-10 23:19Z – 2026-07-24 23:00Z SFC–10,500 ft
3NM W PIÑON HILLS, CA, Friday, July 10, 2026 through Friday, July 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/4907 2026-07-11 15:00Z – 2026-07-24 23:00Z SFC–10,500 ft
3NM W PIÑON HILLS, CA, Saturday, July 11, 2026 through Friday, July 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/5145 2026-07-13 00:57Z – 2026-07-26 07:45Z SFC–8,500 ft
3NM W PIÑON HILLS, CA, Monday, July 13, 2026 through Sunday, July 26, 2026 UTC
View FAA NOTAM → - SECURITY6/7911 2026-07-24 16:30Z – 2026-07-27 02:00Z SFC–400 ft
San Diego, CA, Friday, July 24, 2026 through Sunday, July 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 30
- 462 ft AGL at event
- 152 kt ground speed
- 0 fpm vertical
- 14 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KVBG 161955Z 32010KT 10SM FEW018 FEW028 SCT230 21/14 A3002 RMK SLP168 T02130137 $
Flight context
- CNV836
- B737
- KNTD → KNZY
- 2026-07-24 19:51 UTC
- KVBG runway 30
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