Israel Intel Flights & UVU
This page collects aircraft and flight-tracking claims that citizen investigators use to tie Israeli or intelligence-linked flights to the Utah Valley University (UVU) timeframe around Charlie Kirk's assassination on September 10, 2025. Everything below is a reported allegation drawn from ADS-B/Flightradar24 screenshots, YouTube breakdowns, and X threads. No court has found that any flight was connected to the killing, and prosecutors officially present a domestic lone-suspect case against Tyler Robinson (charged, not convicted).
Scope note: This page does not invent flight data. It summarizes claims already circulating in the investigation file and links to the Planes section for primary flight write-ups. "Israel" appears in the title because citizen investigators frame some of these flights inside an Israel/foreign-intel theory — not because any court has labeled these aircraft Israeli operational assets in the Kirk case.
The SU-BTT "Egyptian plane" timeline (claims)
The most-discussed foreign aircraft in this material is a plane tracked under tail number SU-BTT, an Egyptian registration. According to timeline notes and Candace Owens' reported commentary, its movements bracket the event:
- July 20, 2025: SU-BTT allegedly made its first-ever trip to America, flying to an Army base in Nebraska, coinciding with a reported military meeting involving foreign leaders on U.S. soil.
- September 4, 2025: SU-BTT reportedly flew from France to Provo, Utah.
- September 10, 2025, ~7:08 MT: SU-BTT allegedly left Utah for Wilmington just hours before the assassination at 12:23 MT.
- September 11, 2025: SU-BTT reportedly left the US bound for Egypt.
Investigators also claim the so-called "Egyptian flight" received government clearance to skip security at Provo, carried four to six "contractors" who did not fly away with the plane, and that some allegedly wore "US Department of Defense Liaison" badges. Owens' reported claim is that these contractors were dropped off "in a highly secret way." A companion aircraft, SU-BND (a "blue plane"), reportedly did not take off but had its transponder switched on.
None of this is verified as connected to the crime; these are flight-log interpretations shared by commentators. Deeper Egyptian-aircraft material lives under Planes — Egyptian Armada and related pages.
The SAM-702 flight from Fort Huachuca (claims)
A second thread centers on a military VIP flight tracked as SAM-702:
- Notes describe roughly 12 lieutenant colonels at Fort Huachuca, Arizona around September 8, 2025, with SAM-702 reportedly departing the morning of September 9, the day before the assassination.
- Candace Owens is credited with identifying Bradley D. Hansell as one of four passengers on that flight, described as Trump's Under Secretary of War for Intelligence and Security.
- Commentators note Hansell's reported prior ties to Boston Consulting Group, which they link to Israeli-connected consulting work, presenting this as circumstantial rather than proven.
These are attributed allegations about who was aboard and why; they do not establish any operational link to the shooting. See Fort Huachuca, September 9 and Planes — Fort Huachuca airport for the broader treatment.
N1098L and the HADES surveillance jet (claims)
The domestic aircraft claim most cited alongside the foreign flights is N1098L, a Bombardier Global 6500 that investigators link to the U.S. Army's HADES (High Accuracy Detection and Exploitation System) ISR program, operated via Leidos:
- Trackers report ICAO hex A0299E, callsign AXEL10 / AXLE10, sourced to the ADS-B Exchange and Flightradar24.
- Posts allege the jet cruised near 41,000 feet but descended to a few hundred feet (cited variously as 203, 335, and 600 feet AGL) and slowed near stall speed roughly one mile from UVU, which some interpret as drone drop-off and recovery windows around 9:16 AM and 12:48 PM MT relative to the 12:23 PM shooting.
- The tail number was reportedly N911PV before being changed to N1098L.
Officials and some analysts describe the low passes as drone-retrieval training, and at least one commenter stated the jet "wasn't from Ukraine" and "wasn't from Israel." That rebuttal is part of the record: N1098L is discussed here because it appears in the same flight-tracking discourse, not because it is Israeli.
Primary write-up: Planes — N1098L and ISR Operations.
Islamabad Serena: flights, phones, and diplomacy (claims)
The flight and cellphone threads converge in an April 2026 claim by Tony Seruga and amplified X summaries:
- Four of the alleged 16 Israeli-registered phones from UVU reportedly pinged at the Islamabad Serena Hotel in Pakistan.
- The same hotel was reportedly hosting US–Iran peace talks, with delegations that reporting placed near Vice President JD Vance, Jared Kushner, and Iranian officials.
- The poster labeled the attached tracking graphic as a recreation, "NOT real," so the visual should not be treated as primary evidence.
The full treatment, including the diplomatic context and its limits, is at the sibling page Islamabad Serena Tracking. This is circumstantial pattern-matching until subscriber identities and lawful intercept logs are produced.
How citizen investigators connect flights to an "Israel" frame
Honest mapping of the discourse requires stating how the leap is made — and why it is weak without more:
- Timing clusters: Foreign or military aircraft near Utah in the event window.
- Phone SIGINT claims: Israeli-registered devices at UVU (see Israelis Present at UVU).
- Motive narratives: Donor pressure, Hamptons, Iran-war friction (see Extreme Motivation).
- Capability arguments: Grim Beeper / state tradecraft (commentary only).
Steps 1–4 stacked still do not equal "Israel flew the shooters in." Citizen investigators allege patterns; this site records the allegations and demands manifests.
Other aircraft mentions in the same discourse
Project notes and Planes pages also discuss additional tails and meetings that sometimes appear in foreign-involvement threads (without inventing new track points here):
- Egyptian crew / hotel logistics claims under Egyptian Crew Hotel.
- Israel-Planes for aircraft specifically tagged in that index.
- Following-Charlie / Erika flight claims under Following Charlie & Erika — separate from UVU day-of tracks.
- Ownership disputes (e.g. alleged Ackman-linked entities on other tails) remain contested claims and are not treated as proven ownership findings here.
Cautions on flight-tracking evidence
Flight data is powerful but easy to over-read:
- ADS-B shows aircraft, not intent. Tail numbers, altitudes, and routes are objective; the motive assigned to them is interpretive.
- Coincidence of timing is not causation. Business jets, military ISR flights, and foreign aircraft transit U.S. airspace constantly; overlap with an event window is not proof of coordination.
- Provenance matters. Much of this rests on screenshots and secondhand summaries rather than official manifests or court exhibits.
- Nationality of registration ≠ nationality of mission. An Egyptian tail is not automatically an Israeli mission; a U.S. Army ISR jet is not automatically a foreign hit team.
What would settle it
To move these flight claims from allegation toward evidence, the record would need:
- Passenger and cargo manifests for SU-BTT, SU-BND, and SAM-702.
- The identities and roles of the "contractors" reportedly dropped at Provo.
- Official mission logs for N1098L / AXEL10 on September 10.
- Confirmation of whether any device from the alleged UVU phone set matches devices later tracked abroad.
- Airport security exception paperwork for Provo if the "skip security" claim is real.
The Charlie Kirk Investigation Laws are proposed to compel exactly these aviation and intelligence records, which remain undisclosed.
Open questions
- Who authorized any Provo security exception for SU-BTT, if one existed?
- Where did the alleged contractors go after drop-off, and under what visas?
- What is the official mission statement for N1098L on September 10, 2025?
- Are SAM-702 passenger lists classifiable, and can they be declassified for this case?
- How many foreign-registered aircraft were in Utah airspace that week (baseline)?
Link map into Planes section (do not invent tracks)
| Claim thread | Go read |
|---|---|
| N1098L / HADES / AXEL10 | /Planes/N1098L, /Planes/ISR-Operations |
| Egyptian aircraft cluster | /Planes/Egyptian-Armada, /Planes/Egyptian-Crew-Hotel |
| Fort Huachuca / SAM timing | /Planes/Airport-Fort-Huachuca, /Proof_Intel_Services/Fort_Huachuca_Sept_9 |
| Israel-tagged aircraft index | /Planes/Israel-Planes |
| Counter-UAS at Provo | /Proof_Intel_Services/Provo_Airport_Counter_UAS |
| N1098L over UVU (intel services framing) | /Proof_Intel_Services/N1098L_HADES_Over_UVU |
If a tail number or altitude is not on those pages or in the investigation file, do not invent it here.
July 20 dual event (meeting + SU-BTT)
Citizen timelines treat July 20, 2025 as a hinge: foreign leaders military meeting on U.S. soil and SU-BTT's first America trip to a Nebraska Army base. That dual timing is ambient geopolitics, not a UVU ops plan. It becomes relevant to this page only when investigators claim the same aircraft later stages into Provo. Even then, multi-week aircraft itineraries have many innocent explanations (diplomacy, logistics, maintenance).
Training vs. ops: the official-sounding rebuttals
For N1098L, the drone-retrieval training explanation is the primary non-hostile reading. For foreign aircraft, diplomatic logistics and contractor transport are the non-hostile readings. Hostile readings assign intent from motive theory. Scientific flight analysis can confirm where a plane was; it cannot alone confirm why.
Fort Huachuca cascade claims (Stew Peters thread)
Shared research notes a Stew Peters-style cascade: after Kent asked about planes/military/foreign, a Hegseth plane to Huachuca, JTF division fired, and later AES explosion discourse. That cascade is a US-intel-assisted cover narrative, not pure Israel-flights. It is linked here because flight pages and foreign-lead pages share characters and dates. Primary home: US Intelligence Assisted, fort-huachuca.
Reader caution on composite graphics
Many viral "flight + phone + timeline" images are composites. The Islamabad graphic was labeled recreation. Treat composite posters as argument slides, not ADS-B exports. Demand original FR24/ADS-B Exchange queries with timestamps.
ADS-B literacy for readers
When evaluating flight claims:
- Confirm tail, date, UTC vs local time conversion (MT vs UTC mistakes are common).
- Prefer raw ADS-B Exchange exports over screenshots with arrows.
- Remember Mode-S/ADS-B can be spoofed or gapped; absence of track is not absence of aircraft.
- Passenger identity almost never appears on public ADS-B — manifests are the missing piece.
SU-BTT contractor claim as the highest-value sub-lead
If contractors were dropped in Provo and did not reboard, who housed them, who paid them, and where cameras show them are higher-value questions than the plane's Egypt return alone. That sub-lead needs hotel, FBO, and CBP work — exactly the sort of foreign-nexus tasking Kent's quotes imply was incomplete.
Research capture summary (this batch)
Research file: SU-BTT timeline, SAM-702/Hansell claims, N1098L HADES low passes, Islamabad phone convergence, explicit instruction not to invent flight data. Cross-check always against /Planes/ pages before elevating a new tail number.
Wilmington and Egypt legs (claims)
The alleged Sept 10 morning leave to Wilmington and Sept 11 exit toward Egypt are used by theorists to suggest a clean exfiltration window. Innocent reading: preplanned itinerary independent of the noon shooting. Settling requires FBO logs and passenger lists, not vibes about direction of flight.
Intervention-style caveat for flight pages
No aircraft on this page is declared an Israeli hit platform. Egyptian registrations, U.S. Army ISR, and VIP SAM flights are discussed because citizen investigators embed them in foreign-involvement narratives. Official explanations (training, diplomacy, logistics) are first-class counter-hypotheses. The site finds neither "flights prove Israel killed Charlie" nor "flights are fully explained and irrelevant" — both require manifests.
Coordination hypothesis vs. coincidence hypothesis
Coordination hypothesis (citizen investigators): multiple air assets timed to UVU window for ISR, insertion, or exfiltration related to the killing.
Coincidence hypothesis (skeptics): busy national airspace + military training + foreign itineraries produce spurious clusters when researchers start from a motive conclusion.
Scientific approach: pre-register the time window, measure baseline traffic, then test whether Sept 10 is an outlier. Few public analyses do that rigorously. Until they do, both hypotheses remain live.
N1098L / HADES low-pass discourse (citizen OSINT)
The highest-volume "intel flight" claim on X is not always an Israeli-registered jet — it is the U.S. Army HADES ISR platform N1098L (callsign AXLE10) that citizen investigators place near UVU on September 10, 2025. Posts by @I_Am_JohnCullen (September 2025) describe ~204 ft AGL / ~118 knots passes adjacent to campus roughly 24 minutes after the reported shot time, note the airframe's drone launch/recovery design, and pair it with @JG_CSTT (Jason Goodman) UAV sightings. @ProjectConstitu (January 2026, high engagement) expands the claim set:
- Two low-altitude passes (~pre-event morning and ~post-event recovery window).
- Origin narrative tying Biggs AAF / Fort Huachuca UAS ecosystem.
- Alleged crew names (publicly circulated: Michael Harlan; Elena Vasquez; J. "Jax" E. Donovan) and purported NSCC name overlaps after a list was "scrubbed" online — all unverified in court, and naming living people as flight crew is not proof of criminal acts.
- Israeli-IP Google Trends spikes for uncommon names in alleged planning windows (aggregate analytics claim; highly speculative).
This site does not conclude that N1098L, its crew, the CIA, or any foreign service killed Charlie Kirk. Flight tracks, if confirmed via raw ADS-B, establish platform presence and timing questions only. Full analysis: N1098L, Fort Huachuca Sept 9.
Additional aircraft and FOIA claims (2026)
Later X posts introduce secondary platforms into the same "intel over UVU" bucket:
- @OneShotKi11 claims surveillance aircraft N59906 (associated with MARC Inc. in the post) was photographing UVU shortly before the shooting and says photos/flight data exist — independent verification not on this page.
- Candace-centered amplifiers (e.g. @FurkanGozukara, June 2026) claim a Pentagon-orchestrated secret intel flight ~48 hours prior, allegedly organized by a Defense Secretary Pete Hegseth deputy and tied to the Fort Huachuca plane narrative. That is a commentator package, not a DoD press release; names of deputies and tasking authorities require manifests and orders.
- FOIA-minded accounts demand UVU drone logs and advanced-drone footage release (see also Drones).
Fringe claims such as an Israeli "Bird of Prey" joint-operation drone (e.g. @WeAreNotGTM) are logged as unverified speculation and are not elevated to evidence.
How Israel-suspect theorists use U.S. ISR flights
Readers should notice the analytical move: U.S. Army ISR near UVU is often folded into an Israel-as-main-suspect story via (a) Five Eyes / joint-intel assumptions, (b) Fort Huachuca + Erika family military-tie theories, or (c) Google Trends Israeli-IP overlays. Each step is a hypothesis stack. Honest pages keep the steps separable: ADS-B fact vs passenger identity vs tasking authority vs foreign-state authorship. See Planes overview.