Skip to main content
← Planes

ISR Program Context

ISR — Intelligence, Surveillance, and Reconnaissance — is the umbrella term for military and contracted aviation missions that collect intelligence in real time over a target area. This page is the program-level hub for the aircraft in this section that are tied to active US Army ISR work — chiefly the LASAI Aviation fleet of Bombardier Global 6500 business jets flown under the Army's HADES program. Two of those tail numbers are catalogued individually: the N1098L spy plane, documented descending over the Orem / Utah Valley University corridor on September 10, 2025, and its fleet sister ship N2100L. Read this page first to understand what ISR capability is and why an Army-tasked ISR jet in the UVU airspace window matters; then read the two aircraft pages for the specific flight data.

What ISR aviation does​

ISR-equipped aircraft typically combine some or all of the following capabilities:

  • Signals intelligence (SIGINT): Intercepting radio, cellular, and other electronic emissions in the target area.
  • Imagery intelligence (IMINT): Real-time electro-optical and infrared sensors with operator-grade resolution.
  • Synthetic aperture radar (SAR): Through-cloud and through-foliage ground imaging.
  • Drone deployment and recovery: Releasing and retrieving small unmanned systems for closer-in collection — a capability the Army has publicly said it wants to test from the Global 6500 HADES airframe (per The War Zone / TWZ reporting cited in the case notes).
  • Communications relay: Acting as an airborne node for ground-team communications.

A platform with these sensors flying near an event does not, by itself, prove anything about that event. What it does establish is that records may exist — and that is the entire point of the questions below.

The HADES program​

HADES — High Accuracy Detection & Exploitation System — is the US Army's planned ISR aircraft program-of-record built on the Bombardier Global 6500 airframe. It is intended to replace and consolidate several legacy ISR platforms (the Army's earlier ARTEMIS, ARES, and ATHENA prototype jets). According to the case notes, the HADES program is run out of Biggs Army Airfield (KBIF) in El Paso, Texas, and is associated with program lead Bradley Hansell.

The aircraft N1098L (ICAO hex A0299E, callsign AXLE10 — also rendered AXEL10 in some ADS-B logs) is publicly documented as part of this Global-6500 ISR ecosystem, operated by LASAI Aviation II LLC. Its fleet sister ship N2100L is named in the investigation as a "similar Global 6500" in the same LASAI reconnaissance fleet, tied in X analysis to the same AXLE-series effort and reported under callsigns AXLE21 / AXEL21. The whole LASAI Global 6500 fleet is described in citizen analysis as flying under a Leidos / LASAI "training" cover — the stated mission framing that the routine-vs-targeted debate below turns on. Both aircraft pages are being maintained in parallel:

The contractor structure that limits public disclosure​

Most US Army ISR missions are flown by defense contractors rather than uniformed military crews. Per the case notes and FAA records, LASAI Aviation II LLC is a defense contractor specializing in ISR missions for the US Army, registered at 10660 Aviation Lane, Manassas, VA 20110, and control of LASAI Aviation reportedly fell under Leidos in 2021. Industry reporting on the broader Army business-jet ISR competition has also named other large defense firms — among them Sierra Nevada Corporation and SAIC — as participants; the specific aircraft tracked in this case are the Leidos / LASAI Global 6500s.

The contracting structure means:

  • Crew identities are typically protected as proprietary or classified.
  • Mission tasking is typically not subject to public records requests.
  • FAA-level flight tracking (ADS-B) is sometimes the only public visibility into the mission.
  • Public NTSB databases will only show entries if there was an incident — and a search for N1098L returns no incidents.

This is why investigators of the September 10 N1098L flight have been unable to publicly confirm the crew or the tasking — the contracting layer is opaque by design. The case notes document that obtaining crew details would require formal FOIA requests to the FAA, direct requests to LASAI Aviation, or airport ramp-log requests at Biggs (KBIF) and Glacier Park (KGPI) — channels that are slow, often redacted, and rarely productive for a private observer. Two different and unverified crew lists for the September 10 flight have circulated on X, which underscores how little is actually confirmed.

Routine training vs. targeted surveillance — the open debate​

Online discussion of the LASAI / HADES flights divides into two camps, and this page presents both even-handedly because neither is settled:

  • Routine operations / training. On this reading, the September 10 flight profile was ordinary. One account framed N1098L's Orem low passes as drone drop-and-recovery training — describing two maneuvers (reported around 600 ft AGL and 335 ft AGL) as "textbook drone drop/recovery simulations." Skeptics in this camp, such as X user @TJPHager, have argued the aircraft was not built out to launch drones at all, which would weaken the surveillance reading entirely. This connects to a broader online dispute over whether the LASAI jets carry the full ME-11B sensor configuration: critics reportedly point out that the publicly visible equipment is interior-only, with no visible exterior modifications (radomes, antennas, or sensor blisters) of the kind a fully kitted-out ISR collection aircraft would normally show — an argument that, if correct, would cut against the most aggressive surveillance readings. Under this view, grouping N2100L with N1098L is guilt-by-fleet-association, not evidence.
  • Targeted surveillance. Other citizen investigators on X — including John Cullen (@I_am_JohnCullen) and others focused on the aircraft's surveillance capabilities, low-level operations, and possible real-time monitoring — argue that an Army ISR jet descending to low altitude near a campus hours before, and looping back after, a high-profile assassination is worth a full explanation regardless of the stated training purpose. The case notes also record that a contact at the National Counterterrorism Center (NCTC) said officials there were not aware of N1098L's flight path before or after the killing, and described the HADES plane's maneuvers as "too damning" when combined with the drone findings — an attributed, second-hand account, not a confirmed official finding. Some citizen theories in this camp have also raised Fort Huachuca — the US Army's intelligence base in southern Arizona — as a possible command or communications-relay node for the flights; this is presented as an online hypothesis, not an established fact.

Whether the September 10 profile reflects routine training or a targeted use of ISR assets has been debated extensively online and remains an open question, not a settled conclusion.

Why the September 10 ISR question matters​

If a US Army ISR-tasked aircraft was operating in or near the UVU airspace at the time of the assassination, then the federal government has — at minimum — the possibility of sensor records of the area from an airborne platform. Whether those records exist, who has accessed them, and whether they have been preserved are questions that fall to congressional oversight, because the contractor structure puts them beyond ordinary public-records reach.

The same logic applies to any transponder-off segment of a foreign-government aircraft (see SU-BTT Israel/Egyptian Jet) or a private aircraft operating in the same airspace window.

Open questions​

  1. Was N1098L tasked for ISR collection over UVU on September 10, or was the flight purely the repositioning / training run described in some accounts?
  2. If sensor or imagery records exist for that flight, who has accessed them, and have they been preserved under any litigation hold?
  3. Is N2100L actually ISR-equipped and was it airborne anywhere relevant on September 10–11, or is the "not equipped, not involved" view correct?
  4. How many Global 6500s does LASAI Aviation operate for the Army, and do they share crews, basing, or AXLE-series callsigns?
  5. Which congressional committee has jurisdiction to compel disclosure of HADES tasking and contractor records?

Sources​

  • The Defense Post, "US HADES spy plane" (Sept 10, 2025 coverage), and The War Zone / TWZ reporting on the Army's plan to test air-launched drones from a Global 6500-based HADES jet.
  • Charlie Kirk investigation notes: N1098L identification (ICAO A0299E, callsign AXLE10), HADES program run out of Biggs Army Airfield, LASAI Aviation II LLC / Leidos contractor structure, and FOIA / operator contact channels.
  • FAA registration and ADS-B data (Flightradar24 and ADS-B Exchange) for the LASAI Global 6500 fleet, including N1098L and N2100L.
  • X / OSINT investigators on the ISR angle — including John Cullen (surveillance-capability focus) and @TJPHager (skeptic, "not built to launch drones") — presented as competing, attributed views.
  • Second-hand account attributed to a National Counterterrorism Center contact regarding awareness of N1098L's flight path.

Laws (Charlie Kirk)​

  • The HADES ISR sensor and imagery records for any flight over the UVU corridor on September 10, the classified contractor crew and Army tasking behind those flights, and the full LASAI Aviation fleet roster are exactly the kind of records the Charlie Kirk Investigation Laws are designed to force into the open — truths that the contractor structure currently keeps hidden.

Citizen Investigator Claims on X​

(Aircraft OSINT and attributed claims — not findings that any pilot, passenger, or official ordered or carried out the assassination.)

  • X users including @Josh89220 cite FAA/transponder logs of an Army HADES-class ISR jet (N1098L / AXLE10 in investigation notes) making low (~200 ft class) passes near UVU/Orem before and after the shooting — correlation claims, not proven operational role in the killing.
  • Commentators ask whether ISR/counter-UAS capability at Provo/UVU that week was routine training or something investigators should subpoena — open question for N1098L and Counter-UAS.
  • This page’s focus (ISR Program Context) should be read with the Planes overview and Sept 10 flight timeline for cross-checks.

Track These Aircraft​

This page describes an ISR program rather than one tail number. To research the aircraft tied to it, track the two LASAI Aviation Global 6500s on both major flight-tracking sites. FlightRadar24 honors the FAA's LADD block list (some flights can be hidden); ADS-B Exchange is volunteer-fed and unfiltered (it often shows blocked aircraft and tracks the filtered sites leave out).