Skip to main content
← Timeline

N1098L (HADES) Plane Activity Timeline — Pre & Post Shot

This is a single-aircraft chronology. N1098L is a Bombardier Global 6500 flown for the US Army's HADES program (High Accuracy Detection and Exploitation System), registered to LASAI Aviation II LLC, and it is reported to have made two unusually low, unusually slow passes within a few miles of UVU on September 10, 2025 — one before the shot and one after it, the day Charlie Kirk was killed. Citizen ADS-B interpreters often refer to the military mission callsign AXEL10 / AXLE10 as well as civil tail N1098L. Everything here is aircraft-tracking data and the arguments built on it; the aircraft profile is on N1098L Spy Plane, the low-pass timing argument is on N1098L low-pass timing and HADES low passes, and every other tail number is on Other Planes Activity and across the Planes section.

Disambiguation: Day-one social panic about N888KG (a Provo Challenger ADS-B gap covered in mainstream pieces, whose owner publicly denied any connection) is a different aircraft from N1098L; do not conflate the two (Other Planes Activity). The Egyptian Falcon parked at Provo the same week is a third, separate thread — see SU-BTT movements.

Before September 10, 2025​

  • 2021 — LASAI Aviation, the operator of record, came under Leidos control according to corporate-history research summarized on LASAI Aviation II LLC; the same operator's aircraft were reported circling Washington DC on and immediately after January 6, 2021.

  • Prior registration — The airframe reportedly carried the tail number N911PV before being re-registered as N1098L, a change researchers flag when reconstructing older track history — see ISR Program Context.

  • 2024–2025 (program context) — Open trade reporting described Army plans to test air-launched drones from a Global Express business jet, the same airframe family as the HADES aircraft; that context is the basis for the hypotheses on N1098L Air-Launched Drones and Switchblade & DARPA Drone Claims. Program geography also ties HADES/ISR training discussions to Fort Huachuca, the Army Intelligence Center, in citizen commentary — program association, not proof of September 10 tasking. The base's own September 8–9 window is on Fort Huachuca — Sept 9 Meeting, the Fort Huachuca military timeline and U.S. intelligence assisted — Fort Huachuca.

  • Program leadership — Bradley Hansell is identified in the master file as responsible for the HADES program, run out of Biggs Army Airfield in El Paso, Texas — the field the September 10 flight is said to have departed, profiled on Biggs Army Airfield (KBIF).

  • August 8, 2025 — Researchers report a spike of searches for "N1098L" from Israeli IP ranges, 32 days before the shooting; the method and its limits are discussed on Israeli Search Patterns (Claims), Israel IP search patterns and Planes Search Patterns. This is a Google Trends inference, not a subpoenaed record.

September 10, 2025 — The Two Passes​

  • ~07:48 MDT — One tracking summary states the aircraft's first and only flight of the day departed Biggs Army Airfield (KBIF), El Paso, and arrived at Glacier Park International (KGPI), Kalispell, Montana at 10:38 MDT — a leg that, taken alone, would not put the jet over Utah Valley at all. Citizen posts also phrase the outbound as ~0747 CT toward FCA/KGPI under callsign AXEL10.

  • ~09:16 MDT / 15:16:01 UTC — A second tracking account places the first low pass here: a descent to roughly 650 ft at low speed near Utah Lake, described by researchers as consistent with a release, roughly three hours before the shot. Some @I_Am_JohnCullen cuts also use ~204 ft language on a morning segment — altitude figures vary by screenshot interpretation.

  • ~11:47 MDT — A third account places the first low pass at 11:47 AM at about 600 ft AGL, still roughly two miles from campus (some posts say ~1127 MT return-loop language). The 09:16 and 11:47 versions cannot both describe the same event, and this page does not choose between them — see the conflicts table.

  • ~11:47 AM–12:23 PM MDT — In every version the jet climbs back toward high altitude (reported cruise near 41,000 ft) between the two passes, which is why the low segments stand out so sharply on an altitude ladder plot.

  • 12:23 PM MDT — Kirk was shot in the UVU courtyard; the ten minutes leading to that second are on 10 Minutes Before the Shot, the ten after on 10 Minutes After the Shot, and the 12:23-versus-12:27 dispute on Shooting Time Disputes.

  • ~12:24 PM MDT — One account places the second low pass here — about 335 ft AGL at 129 knots, roughly one minute after the shot. This is the version quoted inside the "drone retrieval training" explanation.

  • ~12:48 PM MDT / 18:48 UTC — A competing account places the second pass at 12:48 PM, at about 203–204 ft and 116–118 knots (near stall speed for the type; some posts say ~113 kt), lasting on the order of 28 seconds and roughly 20–25 minutes after the shot; this is the version most cited on N1098L HADES Over UVU.

  • Public OSINT source node (Sept–Oct 2025) — @I_Am_JohnCullen published widely viewed threads asserting the two low segments near UVU (figures variously ~600 ft / three hours pre-shot and ~204–335 ft / ~20–25 minutes post-shot, speeds near 113–129 kt), framing them as possible drone drop/recovery. Parallel amplifiers include Blake Bednarz (~Sept 15 framing of ~3 hours before / ~25 minutes after on the ATHENA/HADES Global 6500). These are citizen ADS-B interpretations, not official mission logs.

  • Afternoon — Citizen video from the courtyard and surrounding streets is claimed to show small fast-moving objects overhead; those clips are examined on Military Drones on Video and Butch Hibbs & Crowd Drones. No link between those objects and this aircraft has been established.

  • Same day, nearby airspace — Provo Municipal Airport counter-drone questions and the other tails on the ramp that week are covered on Provo Airport Counter-UAS and the September 10 flight timeline.

After September 10, 2025​

  • September 11–17, 2025 — No public accounting of the aircraft's tasking for the shooting week has been released; the withholding pattern is tracked on Airborne Surveillance Records and Foreign Flight Records.

  • ~September 15, 2025 — Early social amplification (Bednarz and others) of the two-pass / AXEL10 / Global 6500 narrative solidifies the numbers later repeated across X.

  • September 18, 2025 — A researcher states in the master file that a contact at the National Counterterrorism Center was, as of that date, unaware of N1098L's flight path before or after the shooting. That is an assertion about an unnamed source, not a documented briefing; NCTC's role is on NCTC, its then-director on Joe Kent, and the later halt to its foreign-involvement inquiry on Joe Kent — Foreign Inquiry Shutdown and Kent NCTC probe halted.

  • Late September 2025 — Public attention to the tail number grew as flight-tracking screenshots circulated; the parallel drawn to unexplained drone activity at Butler, Pennsylvania is on Butler PA Drone Parallel and Drones and Butler.

  • October 1, 2025 — Rebuttal track — A defense-oriented analysis argued the Utah airspace presence was routine HADES training and that linking the jet to the assassination was an information attack without credible evidence — an innocent reading this page keeps alongside the operational hypotheses.

  • October 6, 2025 — Tracking data records the aircraft departing an Army airfield at 14:18 local and arriving at Corpus Christi International (CRP) at 15:35 local, a 1 hour 17 minute leg, with no further flights scheduled that day; it remained on the ground at CRP.

  • 2026 — Capability dispute — Commentators (e.g. @raumgeist) argue the airframe is a trainer configuration lacking external mods to launch/recover drones, while still possibly serving as C2/relay toward Fort Huachuca — conflicting with the "killer drone mothership" rhetoric weighed on Israeli Armed Quadcopter Theory.

  • 2026 — Alternate innocent reading — At least one aviation-oriented commenter has claimed the low pass was a miscalculated turn that left the pilot unwilling to fly again — unverified, and no pilot is named here.

  • Ongoing — The sister ship N2100L, also a LASAI-operated Global 6500, is tracked on N2100L LASAI Sister Ship as a control case for what routine HADES tasking looks like.

Records Requests Attempted​

  • FAA registry — Lists LASAI Aviation II LLC at 10660 Aviation Lane, Manassas, Virginia. The operator is described as an ISR contractor to the US Army, which is the stated reason crew details are not public.
  • NTSB database — A search for N1098L on the date returns no incident, so no post-flight report is reachable by that route.
  • FBO and handling records — Requests for handling-crew details tied to any September 10 arrival or departure have not produced a public result.
  • Ownership claims — Some commentators have asserted an address overlap between the LASAI corporate filing and offices associated with Bill Ackman. That is an online-researcher claim, it is disputed, and no ownership of this aircraft by any private individual has been established.

Conflicts and Disputed Points​

Point in disputeVersion AVersion BVersion C / notes
First low pass time~09:16 MDT (15:16:01 UTC), ~650 ft (some cuts ~204 ft)~11:47 MDT, ~600 ft AGL (~1127 MT in some posts)Cullen ecosystem primary public interpreter of both
Second low pass time~12:24 PM MDT, 335 ft, 129 kt~12:48 PM MDT, 203–204 ft, 113–118 ktBednarz ~3 hr / ~25 min framing aligns with 12:48 version
Was the jet over Utah at allOne summary says the only flight that day was KBIF → KGPI (El Paso to Kalispell)Multiple tracking captures place two low segments near Utah Lake, about two miles from UVUCallsign AXEL10/AXLE10 used in military-op interpretations
Purpose of the passesDrone drop and recovery training — the innocent explanation offered publiclyAn operational release and recovery timed to the event — the HADES over UVU argumentMiscalculated turn / pilot error (unverified 2026 claim); routine training / information-attack rebuttal (Oct 1, 2025 analysis)
Can this airframe launch dronesTrainer config / no external hardpoints — C2/relay only (@raumgeist et al.)Army program reporting describes air-launched-drone test capability for the typeCapability ≠ proof of a Sept 10 release
Crew on boardTwo mutually incompatible crew lists circulate onlineNeither list is verified. No named individual should be treated as confirmed to have been aboardPage refuses to publish either roster as fact

Note on names: this page deliberately does not reproduce the circulating crew rosters as fact. They contradict each other, no primary document supports either, and the people named are living private individuals.

Open Questions​

  1. Which ADS-B archive segments are authoritative, and can the 09:16 and 11:47 accounts be reconciled from raw data rather than screenshots?
  2. If the only logged flight on September 10 was El Paso to Kalispell, what is the origin of the tracked low segments near Utah Lake?
  3. Who tasked the two low passes, and does a mission order exist naming a training objective and the date it was scheduled?
  4. Was anything released or recovered on either pass, and if so what, and where is the recovery log?
  5. Who was on board, and why is even a redacted crew manifest unavailable if the flight was routine training?
  6. Why does an Israeli-IP search spike for this exact tail number appear a month before the event, and is that signal real or an artifact of how Trends aggregates rare terms?

Laws (Charlie Kirk)​

The unreleased mission tasking orders, crew manifests, sensor logs, and any drone release or recovery records for N1098L on September 10, 2025, together with the raw ADS-B and radar archive for Utah Valley airspace that day and the contract terms between the Army, Leidos, and LASAI Aviation II, are things the Charlie Kirk Investigation Laws may result in powerful truths coming out that aren't out yet.