← Timeline

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

Legal Disclaimer — No Claim Of Wrongdoing

Nothing on this page is a finding by this website that any living person named here committed a crime, acted unethically or illegally, or had any knowledge of the assassination of Charlie Kirk before it happened. No one named here has been charged with, accused by any authority of, or found to have committed any offense connected to September 10, 2025.

What appears here about who was where, who travelled on what, or who attended what comes from comments made by other people on social media and in public commentary, attributed to whoever made them. This site does not adopt those claims. They are recorded so that readers, journalists and investigators can check them against primary records — a flight manifest, a visitor log, a FOIA release — and establish whether there is any truth in them. Until that is done, nothing here should be read as an accusation.

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.

• Program leadership (claimed) — The master investigation file asserts that Bradley Hansell is 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). That leadership claim comes from the notes and has not been confirmed against an official Army record.

• 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

Updated 23 September 2026 — the raw archives settle the versions below

Both free ADS-B archives hold this day (adsb.lol, 2,872 points; globe.airplanes.live, 4,439). They answer open questions 1 and 2 at the bottom of this page:

• 07:48 MDT — climbing out of Biggs Army Airfield, El Paso (heard by globe.airplanes.live only).
• 09:14–09:17 MDT — the first low pass, at Provo Municipal: lowest point 4,700 ft barometric at 09:16:45, about 200 ft above the field, then a climb out over the airport. The 09:16 time is right; the 11:47 time is not — at 11:47 the jet was at 37,000 ft about 711 km away.
• About 10:34 to 11:27 MDT — Kalispell, Montana. Descending on final approach 2.1 km out at 10:34, climbing out from 0.08 km at 11:27 (adsb.lol only). FlightAware's archived log gives landed 16:38Z, off 17:27Z. So the "El Paso to Kalispell" summary and the Utah passes are the same day: the flight to Kalispell went by way of the first Provo pass, and the flight back by way of the second.
• 12:23–12:24 MDT — descending from about 30,000 ft, roughly 204–229 km from UVU. There was no pass at 12:24.
• 12:47–12:49 MDT — the second low pass, the same approach at Provo again: lowest point 4,750 ft barometric at 12:49:03, about 250 ft above the field, then a climb out over the airport.
• About 14:24–15:16 MDT — at about Biggs' field elevation (globe.airplanes.live only; FlightAware: landed 20:33Z), then on to Salinas, California (approaching at 17:41 MDT).

At its closest the jet was a little over 4 km from campus on both passes, on the Provo Municipal approach path. No on-ground position was heard anywhere that day. N1098L was heard on the ground at, or flying low near, Provo on 29 separate days between November 2023 and June 2026 — its whole record. Altitudes are barometric, not corrected for local pressure.

• ~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, roughly three hours before the shot. Some circulating screenshots use ~204 ft language for a morning segment instead — altitude figures vary by which capture is read, which is why the raw archive matters more than any screenshot.

• ~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; the raw archives settle it for 09:16 (see the box above).

• ~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 struck 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 circulation (Sept–Oct 2025) — The two-low-segment picture (figures variously ~600 ft / three hours pre-shot and ~204–335 ft / ~20–25 minutes post-shot, speeds near 113–129 kt) spread widely on X from ADS-B screenshots. Blake Bednarz carried the ~3 hours before / ~25 minutes after framing on the ATHENA/HADES Global 6500 from about September 15. The underlying altitude, speed and clock values come from public flight-tracking data; the readings of what the aircraft was doing are citizen interpretation, 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.

• 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 dispute	Version A	Version B	Version 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)	Both versions come from citizen ADS-B screenshots; the raw archives settle it for 09:16 (box above)
Second low pass time	~12:24 PM MDT, 335 ft, 129 kt	~12:48 PM MDT, 203–204 ft, 113–118 kt	Blake Bednarz's ~3 hr / ~25 min framing aligns with the 12:48 version, which the raw archives confirm
Was the jet over Utah at all	One summary says the only flight that day was KBIF → KGPI (El Paso to Kalispell)	The raw archives show both: the Kalispell trip ran by way of two low passes at Provo Municipal, about 4 km from UVU	Callsign AXEL10/AXLE10 used in military-op interpretations
Purpose of the passes	Routine HADES training, including drone-retrieval practice — the innocent explanation offered publicly	ISR tasking over the event, unexplained and never accounted for — the HADES over UVU argument	Miscalculated turn / pilot error (unverified 2026 claim); information-attack rebuttal (Oct 1, 2025 analysis). No mission order has been released for any of them
Can this airframe launch drones	Trainer config / no external hardpoints — C2/relay only (@raumgeist et al.)	Army program reporting describes air-launched-drone test capability for the type	Capability ≠ proof of a Sept 10 release
Crew on board	Two mutually incompatible crew lists circulate online	Neither list is verified. No named individual should be treated as confirmed to have been aboard	Page 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.

The plane very likely did not launch drones. It very likely may have been a training plane, not built out to be able to launch drones, and it may have been there to waste the time of citizen investigators.

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. What sensors were running on either pass, and where is the product they generated — a HADES jet at that altitude and speed was collecting something?
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 not public yet; the Charlie Kirk Investigation Laws could bring these powerful truths out.

Best understanding of when this happened

Best understanding: flight-tracking discussions focus on SEPT 10 daytime relative to the UVU window (not a multi-month axis).

Date range (working model): SEPT 10 daytime flight-tracking window

The chart below is not a government finding. Bar height is relative likelihood from public claims. Domain is trimmed to non-trivial likelihood.

Interesting In This Area

• Two accounts of the first low pass differ by two and a half hours.
• The second pass is placed at 12:24 by one account and 12:48 by another.
• Searches for this exact tail number reportedly spike thirty-two days early.
• The page refuses to publish either circulating crew roster as fact.

Images

This image is a portrait-oriented screenshot of a mobile search result interface, displaying information about a US Army aircraft.

Other Pages In This Section

Nebraska Army Base Visit — SU-BTT (July 20, 2025, Claims)

The whole claim rests on ADS-B screenshots. The same-day tracker post names a civil airfield at Omaha; the later compilations name an Army base. The page shows exactly where the label changed.

Read this

Pre-Event Political Pressure Timeline (July–September 2025)

Nine weeks of escalation, from the July speaker fallout to the last appearance on Ben Shapiro's show. Read as one arc it is the strongest motive material on the site, and none of it names a killer.

Read this

SU-BTT Plane Movements Timeline 2025

Every claimed 2025 movement of one Egyptian-registered Falcon, in date order. It sat at Provo the week of the assassination and left the morning of it, which cuts both ways — and the page says so.

Read this

Spencer Cox, Utah Officials & Governor Timeline

The state-level chronology: appointments, podium appearances, charging decisions, and the reported "by Monday" crime-scene deadline attribution. Utah's own officials, on their own clock.

Read this

This website's author is @HolonCitizen on X and YouTube/@HolonCitizen. Follow me there.

Interesting

• The three official arrest documents do not agree with each other.
• Compilations report a public call for Tucker Carlson to be "neutralized" weeks earlier.
• The all-caps "THEY ARE GOING TO KILL ME" text lands beside UVU rooftop search spikes.

Related Areas

• N1098L and the drone question over UVU
• LASAI Aviation II — the operator of record
• Biggs Army Airfield departure point
• Fort Huachuca — the Sept 9 meeting

• Airborne surveillance records withheld
• Counter-drone coverage at Provo Airport
• ISR program context for the airframe