Skip to main content
← All Fed Slop Issues

4. The names of the crew aboard N1098L on September 10, 2025

Attributed claims only

This site does not publish any N1098L crew names and makes no claim that any person was aboard N1098L on September 10, 2025, or did anything. This site makes no claim that any crew member, operator, contractor, or agency committed a crime or had any role in or knowledge of Charlie Kirk's death. Tyler Robinson is charged, not convicted, and presumed innocent.

The issue in plain words​

N1098L is a Bombardier Global 6500 jet operated by LASAI Aviation II LLC, a US Army intelligence, surveillance, and reconnaissance (ISR) contractor. It is publicly documented as part of the Army's HADES program. On September 10, 2025 it flew two low passes into the Utah Valley, the second one about 25 minutes after Charlie Kirk was killed. The full aircraft record is on N1098L Spy Plane. What the jet was doing over the corridor is Issue 5.

People naturally asked: who was flying it, and who was aboard? Lists of names began to circulate online. Some lists were attributed to AI chat tools. Some were attributed to memory, old contractor rosters, or campus-security adjacency. None of those lists is a crew manifest.

This issue is about those lists. Are they real, or are they made up? And what should a careful reader do with them?

This site's answer is simple and it does not move: we do not republish the names. We do not claim any listed person was aboard. We do not claim any listed person did anything. The question still needs records.

Side by side​

Fed Slop SideCrew-name lists circulating online are AI-fabricated or unverified fan fiction. No public crew field exists, so stop naming people.
Citizen InvestigatorsPublished lists should be checked against manifests and FOIA, not memory-holed as "AI." Until records are produced the crew question stays open. This site does not republish the names or claim any listed person was aboard or did anything.

The fed slop side, in full​

The official-narrative side says the crew-name lists are AI-fabricated or unverified fan fiction. There is no public crew field for this aircraft, so anyone naming people is guessing, and naming private people in connection with a killing can do real harm. The advice is simple: stop naming people.

That position has a solid core. Flight trackers such as FlightAware and Flightradar24 do not publish personnel for private special-mission jets. Crew identities for this sortie have not been publicly confirmed by anyone with records. LASAI Aviation II LLC is a defense contractor. The ISR program layer is opaque by design. A chatbot that emits three plausible-sounding names is not a flight log. Competing lists that do not match each other are evidence that the public does not know, not evidence that any one list is right.

Official-side commentators also treat the whole aircraft as a nothing. If the jet is a trainer flying routine missed approaches, they argue, then crew identity is a gossip question with no case value. On that view, FOIA for a manifest is harassment of contractors who were doing their jobs on a standard El Paso-to-Kalispell training route.

What citizen investigators say​

Citizen investigators agree the names are unverified, and this site agrees too. That is why no names appear here. Where they part ways with the official-narrative side is the next step. Investigators say a published list should be checked against manifests and FOIA records, not simply waved away as "AI." An unverified list is an open question, not a closed one.

The records that would answer it exist somewhere: a crew manifest, a tasking order, a sensor log. Because LASAI is a defense contractor, those records sit behind doors the public cannot open. The LASAI fleet page shows this airframe is one of fifteen, not a lone jet. Biggs Army Airfield is where it launched that morning. Airborne surveillance records are the CoverUp page for the products those people would have been operating. Until those files are produced, the crew question stays open. That is not an accusation against anyone. It is the ordinary demand that a question be answered with documents.

Candace Owens and other independent investigators have asked who tasked the sortie. They have not, on this site's reading, produced a verified crew field either. The honest state of the file is: lists exist, none is proven, FOIA has not killed them, and this page will not launder them into print.

The four proposed laws exist in part to force intelligence-contractor records out. Intelligence Disclosure is the law that would reach a HADES tasking order and a contractor manifest. Without that, the public is left arguing about chatbot output.

When this fight ran​

  • September 14–20, 2025. Citizen trackers first posted the tail, the callsign (AXLE10 / AXEL10), and the two low passes. Name lists followed within days, some tagged as AI-generated, some as "research." Official-side accounts mostly ignored the jet. When they answered at all, the line was that there is no crew field, so stop.
  • October 2025 – spring 2026. FOIA talk, contractor-address rumors, and competing lists. None produced a manifest. This site's N1098L page already said then that it does not name unverified individuals.
  • August 2026. A widely watched debate on whether Tyler Robinson acted alone did not mention the aircraft. Investigators treated that silence as the tell: the official case has no use for a crew question it cannot close.

Why it matters for Tyler Robinson​

No ADS-B track, tasking order, or sensor product from N1098L has appeared in the prosecution of Tyler Robinson, even though the flight overlapped the shooting window. If the aircraft carried sensors over the area, the government may hold airborne records of the scene. Whoever flew it could say what was recorded. Investigators say a case that never asks is a case that does not want the answer, and that the crew question belongs to the evidence, not to gossip.

Citizen investigators conclude Kirk was killed by an explosive at the microphone, and that Tyler Robinson is not the assassin. An Army collection jet over the valley the same day is one of the intelligence-service indicators a lone-gunman file never absorbs. The Proof Intel Services hub and the plane timeline are where that argument lives. Naming unverified people does not advance it. Producing the manifest does.

The drone question — whether this airframe could launch or recover one — is a configuration issue, not a name issue. It is on N1098L and the Drone Question. This page stays on personnel, and stays unnamed.

What would settle it​

  • The FAA and operator crew manifest for the September 10, 2025 sorties.
  • The HADES mission tasking order for that day, and who authorized it.
  • Any sensor or collection logs covering Utah County that day, and whether they were preserved.
  • Written confirmation, under oath, of who was aboard, taken by a body with subpoena power.
  • A public statement from LASAI or the Army that the lists circulating online are false, with the real roster filed under seal if classification requires it.

Read more on this site​