LXJ325 (Huffman Edward) was operating from KIAD to KIAD (Washington Dulles International Airport) on 2026-07-22. SkyMeter detected a diversion to Charleston Executive Airport (KJZI) on runway 09 at 13:33 UTC. Peak cruise altitude FL381, turnaround area near Chapel Hill, US. Approach stability score: 84/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 10 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)
  • HAZARDS6/4931 2026-07-11 15:58Z – 2026-07-23 01:00Z SFC–3,000 ft

    2NM NE SHALLOTTE, NC, Saturday, July 11, 2026 through Thursday, July 23, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/5843 2026-07-14 23:37Z – 2026-07-22 23:45Z SFC–4,200 ft

    18NM SW WAYNESBORO, VA, Tuesday, July 14, 2026 through Wednesday, July 22, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft

    2NM W SHULERVILLE, SC, Monday, July 20, 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 09
  • 10 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • Approach stability 84/100
  • 10 kt wind
  • 7 kt crosswind component
  • 16,093 m visibility
  • METAR KJZI 161115Z AUTO 36005KT 10SM CLR 21/20 A3028 RMK AO2

Flight context

  • LXJ325
  • Huffman Edward
  • E545
  • KIAD → KJZI
  • 2026-07-22 13:33 UTC
  • KJZI runway 09

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