Chain 3: The Following Planes, and Deducing the Country
:::caution Attributed claims only Flying an aircraft, registering it in a foreign country, parking it at a public airport, and operating a lawful government surveillance programme are all lawful acts. No government, operator, crew, or contractor named or linked here has been charged with or found responsible for anything relating to Charlie Kirk's death. This page is an argument built by named investigators from primary position data, with the weakest link identified as the weakest link rather than hidden. :::
The conclusion this chain reaches — and where it stops
Links 1 through 5 are strong: foreign state-registered aircraft were repeatedly on the ground where Charlie Kirk and Erika Kirk were, a US Army intelligence aircraft flew the UVU corridor on the day, and flight records were later removed.
Link 6 — the step from those aircraft to Israel — is an inference from motive, not from the aircraft. It is the weakest link on this page and it is labelled as such.
Most treatments of this subject online blur those two halves together. This page keeps them apart deliberately, because the first half is defensible from primary data and the second half is not yet.
Link 1 — The overlaps are real, and they were tested against primary position data
This site did not take the claim on trust. It rebuilt the register of 85 claimed overlaps and tested each against recovered ADS-B trace files rather than against screenshots of tracking websites.
| What primary position data found | Rows |
|---|---|
| At the claimed field — corroborated | 25 |
| — of those, transmitting on the ground | 10 |
| Contradicted — the aircraft was tracked and was elsewhere | 3 |
| Same metro, wrong field | 1 |
| Not heard — the archive was asked and held nothing | 37 |
| No free archive reaches the date | 10 |
| No aircraft or no date named in the claim | 9 |
Of the 29 rows primary data can actually decide, 25 put the aircraft at the field the claim names. Full drill-down: all 85 rows and the 25 corroborated rows.
Note what this site did with the rows that did not confirm: it published them as their own pages — the 37 not heard, the 3 refuted. A "not heard" result is a coverage fact, never a finding.
Strength: strong, and independently reproducible.
Link 2 — On the day itself, two Egyptian-registered jets were on the ground five miles away
On 10 September 2025, primary ADS-B places SU-BTT at 1.23 km and SU-BND at 1.29 km from Provo Municipal Airport (KPVU) — about five miles from Orem — both transmitting with the on-ground flag set.
SU-BTT had been parked there since 4 September, six days before. SU-BND had arrived 23 May and sat for 113 days. SU-BND was still at Provo on 13 September, three days after the assassination, and then left for Goose Bay, Paris, and Cairo. See the 10 September Orem date.
One internal correction, stated plainly. An older page on this site describes SU-BTT as having departed roughly five hours before the shooting and treats that as exculpatory — see the Egyptian jet SU-BTT. Both can be true: the recovered trace places the aircraft on the ground at Provo that day and then flying on to Wilmington. The two pages disagree about what time it left, and this site publishes the disagreement rather than picking the reading it prefers. Whether the jet was still on the ramp at 12:23 PM is unresolved, and nothing on this page should be read as saying it was.
Strength: strong. These are measured positions, fix by fix, not readings of a website.
Link 3 — That is not how ordinary business charter behaves
A business jet earns money by moving. An aircraft that sits on the ramp of a small Utah field for 113 days, or for six days across a specific event, is not doing charter economics. Long static dwell at a secondary field near a subject of interest is a presence pattern, and presence is what collection platforms do.
Strength: moderate. Maintenance, crew scheduling, storage costs, owner convenience, and simple parking are all real and boring explanations for a jet sitting still. The aircraft cost analysis asks the related question of who could afford this behaviour at all.
Link 4 — A US Army intelligence aircraft flew the corridor that day
N1098L is a Bombardier Global 6500 operated for the US Army's HADES programme — High Accuracy Detection and Exploitation System — a signals and imagery collection platform. On 10 September 2025 it operated near the Orem corridor under callsign AXEL10 / AXLE10 on a profile investigators describe as unusually low and slow. See US Army HADES, N1098L HADES over UVU, and the low-pass timing.
This one is different in kind from links 1 through 3, because there is no dispute about what the aircraft is. HADES is an acknowledged Army ISR programme. The dispute is entirely about what it was doing.
Strength: strong on identity, unresolved on purpose. Public analyses arguing this was routine — training, transit, or a scheduled sortie — exist and are not unreasonable. But an acknowledged intelligence-collection aircraft over the site on the day is a fact that a lone-gunman finding has to absorb, and the Army has not published the mission.
Link 4b — A survey contractor photographed the campus that morning
N59906, a Piper PA-31 Navajo Chieftain operated by MARC Inc. — a Mississippi contractor that sells specialised aircraft for mapping, LiDAR, and surveillance — made multiple passes over UVU the morning of 10 September 2025. Citizen investigators' published times: 11:01, 11:09, 11:18, 11:35. Campus cameras later pick up the man the state calls the shooter at about 11:50. @ProjectConstitu, 7 November 2025 broke the flight; the same account's 31 August 2026 update records that the FAA certificate issued on 4 April 2026 to Alpha Whiskey 2 LLC, same town, same kind of flying.
This site has already corrected the framing around those passes: they were flown at about 19,000 ft MSL, a standard high-altitude mapping band, not a "low pass," and there were five survey legs, not four. An ADS-B trace proves the plane was there. It proves nothing about why. @HolonCitizen, 31 August 2026 put the remaining question in one sentence: name the client. Charlie Kirk Law 1, Item #44 is written to force the MARC Inc contract out.
Strength: strong on presence, unresolved on customer. A mapping grid over I-15 is lawful ordinary work. A mapping grid over this campus, this morning, with photographs that have been described in public and a client who has not been named, is a fact a lone-gunman finding has to absorb the same way HADES is.
Link 5 — The records were then removed
Flight records relevant to this case have disappeared from tracking archives. This site has done the recovery work and — critically — the control testing required to tell a removal from a retention boundary. See Flight Data Recovery, deleted flight records, Erika flight logs erased, and the discipline page What a 403 means.
Strength: strong, and honestly reported. This investigation publicly retracted a removal claim when a control aircraft failed the same way — the retraction is documented, and it is why the surviving removal claims should be believed.
Link 6 — And now the hard part: which country
Here is where the chain becomes an inference rather than a measurement, and this page is not going to pretend otherwise.
What the aircraft themselves say. SU-BTT and SU-BND carry the SU- prefix, which is Egypt. On the face of the registration, the country is Egypt, not Israel. See Egyptian foreign ops, Egyptian jets at Provo, and the Egyptian crew hotel. N1098L is American, operated for the US Army.
How investigators get to Israel anyway. The argument does not come from the tail numbers. It comes from motive and from a separate evidentiary track:
- A documented funding rupture 48 hours before. Messages reportedly confirmed as genuine by TPUSA spokesman Andrew Kolvet have Charlie Kirk writing that he had "just lost another huge Jewish donor. $2 million a year because we won't cancel Tucker" and that the pressure was "leaving me no choice but to leave the pro-Israel cause." See donor texts, 48 hours. This is the one item in the entire Israel file that an adverse party authenticated.
- The Iran war. Kirk's public opposition to a US war with Iran put him against that war's most powerful advocates — Iran, Iran war: Charlie versus Israel.
- His own reported warnings. They are going to kill me and Charlie said Israel would kill him.
- A halted foreign-nexus review. Former NCTC director Joe Kent says the review examining exactly this was ordered stopped — Joe Kent foreign inquiry shutdown.
- Registration as cover. The general argument — that a service does not fly its own flag on an operational airframe, and that third-country registration is standard tradecraft — is the bridge investigators use from Egyptian tails to a non-Egyptian customer. It is a plausibility argument, not evidence about these aircraft.
And what does not survive scrutiny. The claim of sixteen Israeli-registered phones at UVU rests on one man's unpublished proprietary dataset, with a count that drifts between 12 and 16 across retellings and no released method — and the same dataset reportedly showed Chinese, Russian, and Iranian phones nobody suggests were assassins. See Israeli phones at UVU. The life-insurance item disproves its own timing. Operation Grim Beeper proves a capability exists, which implicates nobody in Utah.
Strength: this link is weak, and calling it strong would discredit links 1 through 5. The honest formulation is: the aircraft evidence establishes foreign state-registered presence and an American ISR overflight; the Israel attribution comes from a separately documented motive, and the two have not been joined by any evidence in the public record.
Where the chain lands
Strip it to what survives:
- Foreign state-registered aircraft were repeatedly on the ground at the fields where the Kirks were, and primary position data confirms it on 25 of the 29 rows it can decide.
- Two of them were parked five miles from the killing on the day of the killing, one for six days and one for 113.
- An acknowledged US Army intelligence-collection aircraft flew that corridor that day.
- A survey contractor photographed the campus that morning. The client has not been named.
- The records were then removed, and the removals were verified against controls.
- A federal review of foreign ties was, by a named former director's account, ordered to stop.
- Nobody has ever placed a person aboard any of these aircraft. ADS-B locates an airframe. Erika Kirk's itinerary — the basis of 61 of the 85 claimed rows — has never been published.
That is a case for compelled disclosure. It is not yet a case for attribution to a country, and this page does not make one.
What would settle it
- Disclose every federal aircraft, drone, and collection asset over Utah County on 10 September 2025, and the HADES mission tasking.
- Produce the ownership and charter chain behind SU-BTT and SU-BND — beneficial owner, operator, and who paid for the ground time.
- Name the MARC Inc / N59906 client for the morning of 10 September 2025, and release the image set — Charlie Kirk Law 1, Item #44.
- Produce Erika Kirk's flight itinerary for the claimed overlap dates, which would confirm or destroy 61 of the 85 rows in an afternoon.
- Restore the NCTC foreign-ties review and publish its work product — see the four disclosure laws.