Diversion — VJA505

KLXV · 16

2026-01-09 18:52 UTC· KMIA → KLXV· BANK OF UTAH TRUSTEE· GL5T

▶ Replay 📊 Analyse

VJA505 (Bank of Utah) was operating from KMIA to KASE (Aspen-Pitkin Co/Sardy Field) on 2026-01-09. SkyMeter detected a diversion to Lake County Airport (KLXV) on runway 16 at 18:52 UTC. Peak cruise altitude FL467, turnaround area near Sibley, US. METAR at the time reported 14 kt wind, 2 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY5/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft

    South Padre Island, TX, Tuesday, May 6, 2025 Local

    View FAA NOTAM →
  • SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft

    OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local

    View FAA NOTAM →
  • SECURITY5/3678 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–2,000 ft

    Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local

    View FAA NOTAM →
  • SECURITY5/3679 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–5,000 ft

    Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 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 16
  • 9919 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • 14 kt wind
  • 2 kt crosswind component
  • SPECI KLXV 131543Z AUTO 22006G15KT 1 3/4SM +RA BR FEW012 OVC020 03/01 A3020 RMK AO2 RAB32 P0003 T00280011

Flight context

  • VJA505
  • Bank of Utah
  • GL5T
  • KMIA → KLXV
  • 2026-01-09 18:52 UTC
  • KLXV runway 16

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