Foreign-Nexus Flight Records Withheld (Claims)
:::caution Legal Disclaimer Nothing on this page is a claim of fact that any living person or organization knew of, planned, participated in, or covered up any crime, or acted illegally, immorally, or unethically. This page documents questions and allegations raised in public commentary — not findings of fact. All persons and organizations named are presumed innocent; the allegations referenced are unproven and have not been established in any court. Tyler Robinson is charged, not convicted. :::
This page catalogs a reported cover-up mechanism, not a finding of fact. Citizen investigators allege that the "foreign-nexus" flight leads around Utah Valley University — the campus where Charlie Kirk was killed on September 10, 2025 — rest almost entirely on public ADS-B tracking data with no released passenger or cargo manifests, mission logs, or Provo security-exception paperwork. They further allege that "contractors" who reportedly deplaned at Provo and did not reboard were never publicly identified or made the subject of a task force. The claim is that the records able to confirm or kill these leads are precisely the ones withheld. None of this is proven, and Tyler Robinson is charged, not convicted.
The claim
The foreign-flight leads circulating online are built from what trackers could see — tail numbers, routes, and times — and stop where the official record goes dark. Commentators argue that manifests, cargo logs, visas, and security waivers exist somewhere but have not been disclosed, so the leads can be neither confirmed nor dismissed. This page synthesizes that "records withheld" angle and routes readers to the detailed flight pages elsewhere on the site.
The SU-BTT timeline
Much of the attention centers on SU-BTT, an Egyptian-registered aircraft (described variously as a Falcon 7X or Gulfstream-class jet). According to circulating flight notes:
- July 20, 2025 — its first-ever U.S. trip, reportedly to an Army base in Nebraska.
- September 4, 2025 — flew from France to Provo, Utah.
- September 10, 2025 (~7:08 MT) — left Utah for Wilmington, shortly before the assassination.
- September 11, 2025 — exited the U.S. toward Egypt.
Commentators call it unusual that the jet's other U.S. stops were at Army airfields, while Provo was not. These are attributed timeline claims drawn from tracking data, not confirmed mission facts.
The reported Provo "contractors"
Per posts attributed to Candace Owens and to sources described as being at Duncan Aviation, SU-BTT reportedly had government clearance to skip security at Provo, and four to six "contractors" boarded or deplaned who did not reboard when the jet left. Some reportedly carried badges reading "US Department of Defense Liaison," and one account claims counter-UAS (anti-drone) gear was tested at Provo Airport between September 4 and 10. Who these individuals were, and whether any of it is accurate, has not been publicly established.
The companion aircraft
Notes also reference SU-BND, a second Egyptian-registered jet described as the "blue plane," which reportedly had its transponder on but did not take off at a key moment and stayed in the Provo area for months. A separate VIP flight, SAM-702, is tied to the Fort Huachuca thread around September 9. These companion tracks are used by commentators to argue a pattern rather than a single anomaly; the pattern remains unproven.
The wider "armada" and Dugway claims
Some accounts push the pattern further. One widely shared post claims that beyond SU-BTT and SU-BND, three more Egyptian-registered jets — SU-BTU, SU-BTV, and SU-BGM — appeared in Provo during 2025, which the poster framed as a "five-plane armada" of VIP Falcons and Gulfstreams routing through Utah via Cairo and Paris. A separate claim asserts SU-BTT did not actually launch from Provo at all but from Dugway Proving Ground's restricted Michael Army Airfield, with the transponder off until it cleared the R-6404 no-fly zone, and that trackers mislabeled the origin as Provo because it was the nearest public airport. These are contested, single-source interpretations of tracking data and are not established; they are included to show the shape of the claims, not to endorse them. See the N1098L overview for the parallel surveillance-aircraft thread and Israel connections for the alleged foreign angle.
The withheld records
The heart of the cover-up claim is what is missing. Commentators say the following would settle the leads either way, and none of it is public:
- Manifests for SU-BTT, SU-BND, and SAM-702.
- Contractor identities and visas for those who reportedly deplaned at Provo.
- Provo security-exception paperwork authorizing any clearance to skip screening.
- CBP entry and exit records for the foreign aircraft and their passengers.
This is where the leads stall — not on tracking data, which is abundant, but on the identity and authorization records, which are undisclosed.
What would settle it
The narrow, checkable questions raised by investigators are:
- Manifests for SU-BTT, SU-BND, and SAM-702 across the September 4-11 window.
- Names, visas, and badges of the reported 4-6 Provo "contractors," and whether any were ever interviewed or task-forced.
- The Provo security-exception paperwork — who authorized any clearance to skip screening, if one existed.
- CBP entry and exit records for the foreign aircraft and their passengers.
If those records were released and showed ordinary travel, the leads would collapse. Because they are the one category that stays sealed, the leads instead remain permanently untestable — which is the exact pattern this page documents.
Why it matters
When a lead can only ever be tested by records that are not released, it stays permanently open — impossible to confirm, impossible to dismiss. That is why this is catalogued under Cover Up (Possible): as an unresolved question about record access around a high-profile killing, not as a claim that any flight, passenger, or government played a role.
Counterarguments, skepticism, and innocent explanations
- Manifests are private by default. Passenger and cargo lists for private and foreign aircraft are not public records; their absence is normal, not evidence of concealment.
- Ground time and blackouts are routine. A jet sitting for days, or ADS-B gaps, can reflect ordinary maintenance, crew rest, diplomatic travel, or airspace rules.
- "Did not reboard" has benign explanations. People routinely arrive on one aircraft and leave by another; a crew or passenger not reboarding proves nothing.
- Tracking is not identity. ADS-B shows where an aircraft went, not who or what was aboard or why — the leads infer intent from routes.
- No established role. None of these flights, badges, or contractors has been shown in any court to have any connection to the killing.
- All persons and organizations referenced are presumed innocent. No court has found that anyone named committed a crime in connection with these claims.
Sources
- Master investigation file timeline for SU-BTT (July 20 Nebraska trip; Sept 4 France to Provo; Sept 10 ~7:08 MT departure to Wilmington; Sept 11 exit to Egypt).
- Notes and posts on SU-BND ("transponder on, did not take off"; extended Provo stay) and SAM-702 (~Sept 9 from Fort Huachuca).
- Posts attributed to Candace Owens and to Duncan Aviation sources on the reported Provo security clearance, 4-6 "contractors" who did not reboard, "US Department of Defense Liaison" badges, and counter-UAS testing at Provo (Sept 4-10).
- Circulating "what would settle it" lists calling for SU-BTT / SU-BND / SAM-702 manifests, contractor identities and visas, Provo security-exception paperwork, and CBP entry/exit records — all described as undisclosed.