Skip to main content
← All Fed Slop Issues

5. What the Army ISR jet N1098L was doing over the Provo and UVU corridor

Attributed claims only

This site makes no claim that N1098L, its crew, LASAI Aviation, Leidos, or the US Army had any role in or knowledge of Charlie Kirk's death. Flying an aircraft and running a lawful surveillance program are lawful acts. A flight trace proves presence, never purpose and never occupancy. Tyler Robinson is charged, not convicted, and presumed innocent.

The issue in plain words​

On September 10, 2025, a US Army intelligence jet, N1098L, flew from Biggs Army Airfield in El Paso and came down into the Utah Valley twice. Two free volunteer flight archives hold the full day, with 2,872 and 4,439 position points, and they agree. The aircraft is a Bombardier Global 6500 operated by LASAI Aviation II LLC under the Army's HADES program, callsign AXLE10 (also rendered AXEL10). The full record is N1098L Spy Plane.

The first pass ran 9:04 to 9:28 AM local time. The second ran 12:38 to 1:00 PM, closest to the UVU campus at 12:48 PM, about 25 minutes after Charlie Kirk was killed at 12:23. Both times the jet flew the same inbound track, slowed to about 120 knots, dropped to roughly 200 feet above Provo Municipal Airport's field elevation, then went to full power and climbed out over the runway. Its closest point to UVU was 4.16 km, about 2.6 miles, on both passes.

The question: was this routine flying, or something that should have been investigated? Citizen investigators conclude Kirk was killed by an explosive at the microphone. The government's story is a rooftop .30-06 fired by Tyler Robinson. An Army collection jet over the valley the same day is either a coincidence or a record the charging package never asked for.

Side by side​

Fed Slop SideA LASAI/Leidos Global 6500 Army trainer. Routine missed approaches at PVU, done hundreds of times at 100+ airports. Not drone-launch capable. Not operational HADES ISR. No link to the shooting.
Citizen InvestigatorsA HADES/AXEL low, slow double pass the same day, including after the shot, is the anomaly. A drone drop/recovery profile is the live hypothesis. Tasking and sensor logs are the records that should be forced out.

The fed slop side, in full​

The official-narrative side says this is a LASAI and Leidos Global 6500 Army trainer flying routine missed approaches at Provo Municipal, the kind of thing these aircraft do hundreds of times at more than 100 airports. It was not drone-launch capable and was not flying operational HADES ISR. It has no link to the shooting. The FAA and FBI, on this telling, found no aircraft link. The El Paso-to-Kalispell route is a standard training line. The Provo dips are currency work.

This site's own reading of the data leans the same way on the geometry. A steady track, down to about 200 feet above the field, then power and a climb over the runway, is the shape of a straight-in approach followed by a go-around. It was flown at the airport, not over the campus. Closest approach of 4.16 km is what the Provo Municipal approach path measures from UVU. Sister ship N2100L landing at Provo on 1 July 2025 passed 4.17 km from the same point. The site also says plainly that the aircraft very likely did not launch drones and was very likely not built out to do so. That is the honest ordinary reading, and it belongs on the table at full strength.

Official-side commentators treat any remaining interest as conspiracy decay: if it looks like an instrument approach, it is an instrument approach, and asking for tasking orders is a way to smear the Army. On that view, Tyler Robinson is the case, the jet is a hobby, and the September 10 flight stack is weather.

What citizen investigators say​

Citizen investigators say the anomaly is the timing and the repeat. A HADES-program aircraft flew the same low, slow double pass on the same day a political leader was killed nearby, and one of those passes came after the shot. They argue a drone drop-and-recovery profile is a live hypothesis worth testing, and they note that a drone-retrieval training explanation is itself one of the benign accounts offered for the passes. The drone question is collected on N1098L and the Drone Question Over UVU and the Drones hub.

John Cullen and other trackers have put the same two Provo dips next to a third clock: AXEL21 over St. George on September 11, near the sheriff's station, around 9 PM — Discord-post time. Three HADES-family appearances in 36 hours is, they argue, the pattern a lone-gunman file cannot absorb. That is the chain that it was not a lone gunman.

This site's position is more careful. The plane very likely did not launch drones. It may have been a training plane, and it may have been there to waste the time of citizen investigators. If the people who planned for it to be there knew the crime would happen, that may be a path to people who had foreknowledge. The site does not claim that is true. It claims the question is important. The N1098L HADES Over UVU page and the Proof Intel Services hub are where that argument is kept in bounds.

What investigators agree on is the next step: the tasking order and sensor logs are the records that would answer it, and they should be forced out rather than assumed. The Airborne Surveillance Records page is the CoverUp file for products that may exist and have not been produced. Who was aboard is the companion personnel question; this site does not republish crew names.

When this fight ran​

  • September 14–20, 2025. Citizen OSINT first posted the tail and the two low passes. Altitude figures in early threads did not agree with each other (600 ft vs 203 ft; 12:24 vs 12:48). The recovered ADS-B later settled the clocks at 9:16 AM and 12:48 PM bottom-outs. Official-side accounts mostly did not engage.
  • Late September – October 2025. Trainer-versus-ISR became the split. One camp said missed approaches at 100+ airports. The other camp said a HADES double pass including after the shot is the anomaly even if the geometry is an approach. FAA/FBI "no aircraft link" language circulated as a close.
  • 2026. Recovery of both volunteer archives (2,872 and 4,439 points agreeing to two decimals) hardened the geometry. A widely watched August debate on whether Robinson acted alone did not mention the jet. Trackers were still posting the Provo dips in September 2026.

Why it matters for Tyler Robinson​

No ADS-B track, tasking order, or sensor product from N1098L has appeared in the case against Tyler Robinson. If an Army collection aircraft was over the valley that day with sensors running, the government may hold airborne records of the scene that could show where the fatal event came from. A lone-gunman case that never mentions such an aircraft, investigators say, is a case that has chosen what not to look at.

Proof Not Tyler and Tyler Robinson Not Assassin put the missing airborne product next to the missing firing tape and the ATF fragment. The low-pass timing page is the place that records how early claims of a 12:24 pass conflicted with the later 12:48 figure. The LASAI fleet shows this was not a one-off airframe. Fix the laws is how a reader forces the tasking out.

A trace proves presence. It does not prove purpose. Investigators still want the tasking, because presence of a HADES jet 25 minutes after the shot is the kind of fact a charging package that closes on a 22-year-old apprentice has to explain or disclose.

What would settle it​

  • The HADES mission tasking order for September 10, 2025, and who planned the Provo approaches.
  • The aircraft's configuration that day: what sensors were fitted and whether any were recording.
  • Any sensor or imagery product covering the Orem and Provo area, and its preservation status.
  • Provo Municipal tower records and radio logs for both passes.
  • A control comparison: how often this tail flew the same missed-approach pair at PVU in 2024–2025, on days with no sourced Kirk event.

Read more on this site​