Diversion — EJA158
KLXV · 162026-02-17 22:43 UTC· KMIA → KLXV· NETJETS SALES INC, BANK OF UTAH TRUSTEE, EDINTON HOLDINGS USA IN· GLEX
EJA158 (Netjets Sales) was operating from KMIA to KRIL (Garfield County Regional Airport) on 2026-02-17. SkyMeter detected a diversion to Lake County Airport (KLXV) on runway 16 at 22:43 UTC. Peak cruise altitude FL446, turnaround area near Sibley, US. METAR at the time reported 21 kt wind, 4 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/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
- 21 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- METAR KLXV 070553Z AUTO 06004KT 10SM CLR 07/M02 A3054 RMK AO2 SLP185 T00671017 10133 20067 58005
Flight context
- EJA158
- Netjets Sales
- GLEX
- KMIA → KLXV
- 2026-02-17 22:43 UTC
- KLXV runway 16
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