Diversion — VTE3118

KCSG · 06

2026-08-02 17:24 UTC· KFLL KCSG· CORPORATE FLIGHT MANAGEMENT INC DBA, CONTOUR AVIATION· E135

VTE3118 (Corporate Flight Management Inc DBA) was operating from KFLL to KMCN (Middle Georgia Regional Airport) on 2026-08-02. SkyMeter detected a diversion to Columbus Metropolitan Airport (KCSG) on runway 06 at 17:24 UTC. Peak cruise altitude FL330, turnaround area near Alachua, US. Approach stability score: 77/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 8 kt wind, 7 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

    Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/0628 2026-07-31 13:07Z – 2026-08-03 01:30Z SFC–1,300 ft

    13NM S TAYLOR, FL, Friday, July 31, 2026 through Monday, August 3, 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 06
  • 391 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • Approach stability 77/100
  • 8 kt wind
  • 7 kt crosswind component
  • 16,093 m visibility
  • KCSG 162151Z 11008KT 10SM CLR 32/19 A3023 RMK AO2 SLP232 T03220194

Flight context

  • VTE3118
  • Corporate Flight Management Inc DBA
  • E135
  • KFLL → KCSG
  • 2026-08-02 17:24 UTC
  • KCSG runway 06

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· KCSG