Diversion — EJA823
KPWA · 17L2026-08-19 21:08 UTC· KBJC → KPWA· NETJETS SALES INC, DOWNING CIRCLE LLC, FERNHILL AVIATION LLC, KC· C700
EJA823 (Netjets Sales) was operating from KBJC to KSHV (Shreveport Regional Airport) on 2026-08-19. SkyMeter detected a diversion to Wiley Post Airport (KPWA) on runway 17L at 21:08 UTC. Peak cruise altitude FL433, turnaround area near Ulysses, US. METAR at the time reported 6 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)- HAZARDS6/1462 2026-08-04 13:00Z – 2026-09-01 04:00Z SFC–15,000 ft
20NM SW PUEBLO, CO, Tuesday, August 4, 2026 through Tuesday, September 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/3075 2026-08-08 19:30Z – 2026-08-22 04:00Z SFC–12,000 ft
28NM NE LAS VEGAS, NM, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/3101 2026-08-09 13:00Z – 2026-08-24 03:00Z SFC–15,000 ft
24NM SW PUEBLO, CO, Sunday, August 9, 2026 through Monday, August 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/4894 2026-08-13 13:00Z – 2026-08-28 04:00Z SFC–15,000 ft
8NM SE TRINIDAD, CO, Thursday, August 13, 2026 through Friday, August 28, 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 17L
- 1299 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- METAR KPWA 161453Z 20010KT 10SM CLR 31/19 A3016 RMK AO2 SLP193 T03110189 51011
Flight context
- EJA823
- Netjets Sales
- C700
- KBJC → KPWA
- 2026-08-19 21:08 UTC
- KPWA runway 17L
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