SU-BTT Israel/Egyptian Jet
An Egyptian-registered Dassault Falcon 7X (tail number SU-BTT) — referred to on Candace Owens's podcast as "the yellow plane" — is reported to have been on the ground in or near Provo, Utah from September 4 through the morning of September 10, 2025, departing the United States in the hours around Charlie Kirk's assassination. It is the lead aircraft in what X researchers call the "Israel/Egyptian Plane Armada" — a cluster of Israel/Egyptian government Falcons and Gulfstreams (SU-BND, SU-BTU, SU-BTV, SU-BGM) that trackers say overlapped with TPUSA events for years. Every claim below comes from independent open-source researchers working from public ADS-B records; little of it has been independently verified, and the innocent explanations are laid out near the end of this page. See also Sept 10 Flight Timeline (transponder window vs. hospital timing) and Egyptian Crew Hotel (La Quinta Orem lodging tip).
Aircraft identification
- Tail number: SU-BTT
- Type: Dassault Falcon 7X (long-range business jet) — reported by trackers as built in 2014
- Registry / operator: Egyptian-registered — described as Israel/Egyptian Air Force / Israel/Egyptian Government use
- Nickname in coverage: "The yellow plane" (Candace Owens's color-coded shorthand; SU-BND was "the blue plane")
- Home base in Utah window: Provo Municipal Airport (PVU), ~7 miles from Utah Valley University
Flight history relevant to the case
Independent trackers, amplified by Candace Owens, describe two US visits in 2025. Dated bullets below reflect their published timelines:
- July 20, 2025: Reported as the jet's first-ever trip to the United States — to an Army base in Nebraska (Omaha / Lincoln corridor).
- First US visit (August): Paris → Omaha/Lincoln (Aug 17) → Wilmington, DE (Aug 23) → Paris (Aug 24).
- September 4, 2025: Second US visit — routing from Paris-Le Bourget (LBG) via Minot, ND into the Provo/Orem, UT area, then stayed. Trackers stress this full inbound arrival and alleged drop-off came six days before the assassination.
- September 10, 2025: Departed Utah for Wilmington, DE — the day of the UVU shooting. Trackers describe this outbound leg as visibly "lighter" than the inbound flight. One widely shared post summarized it bluntly: "Egyptian military planes in Provo at Provo Municipal Airport on 9/10/25. Tail# SU-BTT flew in on 9/4/25 and departed the morning of 9/10/25."
- September 11, 2025: Departed the United States for Egypt (Cairo) via Wilmington.
Owens's team claims 18 people flew in but far fewer flew out, and that the same aircraft had earlier appeared near the 2025 Rotary "Peace 2025" conference in Istanbul (Feb 20–22, 2025) before leaving the country ahead of the assassination.
Conflicting accounts of the Sept 10 departure
Public sources do not agree on how SU-BTT left Utah on September 10. Three versions circulate, and they cannot all be true:
- 7:08 AM departure: Some flight logs show SU-BTT leaving Utah for Wilmington at roughly 7:08 AM MT, hours before the shooting.
- Power-up, go dark, reactivate: Owens's "nuclear flight logs" presentation describes the jet powering up at Provo Municipal around 9:05 AM, going dark, then reactivating 17 minutes after the shot and idling on the tarmac until 1:29 PM.
- Dugway origin: A separate OSINT thread claims it never took off from Provo at all (see below).
These accounts are reported here as competing allegations, not settled fact.
Long-term tracking pattern (2022–2025)
Beyond the September 2025 window, Owens and independent trackers allege a multi-year pattern of SU-BTT overlapping with the Kirk family's movements:
- According to their tallies, the Israel/Egyptian jets logged roughly 73 overlaps with Erika Kirk and about 23 with Charlie Kirk across the United States (Omaha, Wichita, Provo, plus domestic and international legs).
- Owens has framed the odds of that many location overlaps happening by chance as vanishingly small — citing a "0.000000001%" coincidence figure — and her team has said it cross-referenced the flight legs against rental-car records for the Kirks' ground movements. The probability figure is a rhetorical estimate, not a calculated statistic, and is reported here as her framing rather than as a verified number.
- Some reported overlaps are said to include international flights and legs connected to Israel.
- One widely shared post framed the pattern in absolute terms: "72 times those exact planes followed Erika Kirk, not a plane like it, those 2 planes. That is statistically near impossible without intent." This is the trackers' rhetorical framing, not a verified statistic — the published counts themselves vary (68, 70+, 72, and 73 all appear across different posts).
- A separate analysis claims the Israel/Egyptian jets' US stops cluster in five states — Missouri, Delaware, Utah, Nebraska, and Kansas — which posters read as following the Kirks and TPUSA events. Critics note that several of those states (notably Kansas) host major aviation-maintenance hubs, which would also explain repeat visits.
- A separate dual-plane tally circulated on X claims that the blue (SU-BND) and yellow (SU-BTT) jets together overlapped with Erika Kirk's locations 68 times between 2022 and September 2025 — including overseas trips — and that 29 of those overlaps also coincided with Charlie Kirk's location. This 68/29 figure is a different count from the 73/23 tally above and is reported here as an independent researcher's claim, not a reconciled number.
- Two of the most-shared verbatim framings of these tallies, reported here as the trackers' own words rather than as verified statistics:
- "Two specific Egyptian-registered planes (tail numbers SU-BTT and SU-BND…) showed repeated overlaps with Erika Kirk's locations and travel patterns. These overlaps occurred 73 times between 2022 and September 2025."
- "The Egyptian military plane was tracking Erika Kirk NOT Charlie Kirk! Between 2022 and September of 2025, both the blue plane and yellow plane showed 68 overlaps with Erika Kirk's location, including trips she took outside of the country. Out of those 68 instances, 29 of them included Charlie."
- Owens's timelines also single out Turning Point Faith events specifically, describing the Israel/Egyptian jets as allegedly shadowing domestic political targets in a systematic pattern. This is her characterization of the ADS-B data, not an official finding.
- Posters amplifying these tallies have repeatedly framed the silence around the Israel/Egyptian jets as a question — "why is the FBI silent?" — pointing to the aircraft being on the ground at Provo on the day of the assassination. This is rhetorical framing by the trackers, not an official finding.
- Trackers point to public ADS-B data they say shows the aircraft appearing near the family's locations with unusual frequency.
These claims rest on public ADS-B records circulated by independent researchers and have not been independently confirmed. They are reported here as allegations made by the named trackers, not as established fact.
Reported flights to Israel
Independent compilers — credited on X to @nihilox and amplified by @ProjectConstitu (Project Constitution) — claim SU-BTT made dozens of trips toward Israel across the year. They allege the public logs read Cairo-to-Cairo (CAI → CAI) or show no destination because, they say, the jet flew with its transponder off and actually landed in Israel. The dates they list (presented here as the trackers' compiled claims, not confirmed flights) include:
- Jan: 05, 12, 26 — Feb: 11, 16, 18, 23 — Mar: 18 — Apr: 05, 08 — May: 27
- Jun: 14, 18, 21, 22 — Jul: 05, 08 (two flights), 13 — Aug: 05
- Sep: 20 (two), 21, 30 (two) — Oct: 13, 21, 22, 26 — Nov: 18, 30 — Dec: 02, 07
@nihilox summarized the pattern in absolute terms, posting what the account called "irrefutable evidence SU-BTT regularly flies into Israel." The alleged ADS-B signature, as described by these trackers, is consistent: the jet departs Cairo, flies south, then goes dark — dropping off public tracking — and reappears only after the leg into Israel would have been completed. One thread also cites an eye-witness said to place the Egyptian chief of intelligence landing in Israel shortly after one such blackout. @nihilox's stated conclusion is that Egypt is lying about its relationship with Israel, and that this points to a possible Israel connection to the Israel/Egyptian jets that were on the ground the day of the assassination. These are the trackers' claims and an unverified witness account, not confirmed flights.
A related interpretation circulating on X is the "Paris meetings" theory — that SU-BTT's repeated stops at Paris-Le Bourget functioned as neutral ground for high-level government meetings (described by some posters in "dead drop" terms). This is speculation offered by independent researchers, not an established finding.
One of these legs is corroborated by mainstream reporting rather than only by ADS-B screenshots: per Israeli Channel 12 News, SU-BTT flew Cairo to Israel on October 21, 2025, reportedly carrying Hassan Rashad, the head of Egyptian intelligence. Rashad is a foreign public official, and an Egyptian intelligence chief flying to Israel is consistent with the two countries' long-standing diplomatic and security contacts. This single corroborated trip does not establish that the earlier listed legs occurred as described, nor that any of them connect to the Charlie Kirk case.
The Duncan Aviation / contractor claims
Multiple unconfirmed witness accounts shared on X (which the authors themselves flag as uncorroborated) allege the Provo stop was not routine maintenance:
- Sources said to be at Duncan Aviation (the MRO operator at Provo) reportedly described 4–6 subcontractors boarding with Egyptian passports but carrying badges reading "U.S. Department of Defense Liaison."
- The contractors are alleged to have not flown out again, and to have tested "counter-UAS" (anti-drone) gear at Provo Airport between Sept 4–10.
- Provo Tower (PVU) logs are claimed to show a "no-scan priority clearance" federal override on Sept 4, with no passenger manifests recorded.
- The same threads name two alleged passengers ("Maj. Ahmed Khalil" and "Eng. Omar Nassar") as people who, the author says, need to be investigated further — these are unverified names floated online, not confirmed identities, and no wrongdoing has been established.
- A further claim alleges the jet dropped off Egyptian military personnel or subcontractors miles from UVU on the day of the assassination, framed by posters as a possible staging area. One widely shared post described the aircraft as "sitting on the tarmac… dropped off members of the Egyptian military." No evidence supports this; it is reported here strictly as an online allegation.
Treat this entire section as raw, unverified online testimony. None of it has been confirmed by any official source.
Theories about the aircraft's role
Researchers covering SU-BTT have floated several interpretations, framed as open theories rather than conclusions:
- Foreign surveillance — that a foreign-government aircraft may have been monitoring Charlie Kirk, Erika Kirk, or TPUSA events (the "intel-vacuum" theory).
- A possible joint operation — tied to the Wilmington routing discussed below.
- Counter-drone testing or a drone role — John Cullen has speculated the aircraft was associated with drones; other threads tie it to the counter-UAS claims above.
Owens has stressed these were not, in her telling, simple maintenance stops. Skeptics disagree — see the counterpoints section.
Whether any federal body ever ran foreign-aircraft leads like these to ground is itself an open question: former NCTC director Joe Kent has said on the record that his center's parallel review of possible foreign ties to the assassination was ordered to stop once Tyler Robinson was in custody, before such leads were exhausted.
The Dugway departure claim
According to an X thread by @ProjectConstitu (Project Constitution) building on flight-tracker analysis, SU-BTT did not actually take off from Provo Municipal Airport on September 10. That account framed it as: "The Mysterious Egyptian Government Jet SU-BTT Didn't Depart from Provo… It Took Off from DUGWAY PROVING GROUND… transponder OFF… Classic stealth protocol." The specifics they list:
- Trackers showed SU-BTT "materializing" mid-air near Utah with no recorded takeoff from PVU.
- The reported origin was Dugway Proving Ground's Michael Army Airfield — a restricted US military test site west of the Great Salt Lake.
- The aircraft is reported to have flown with its transponder OFF until clearing the R-6404 restricted airspace, then re-acquired tracking, with public trackers defaulting to the nearest public airport (Provo) as the displayed origin.
If accurate, this would place an Israel/Egyptian government jet operating from a restricted US military airfield in the days around a high-profile political assassination. The claim is unverified.
The Wilmington destination
SU-BTT's September 10 destination — Wilmington, DE — has been linked in public reporting to 920 North King Street, One Rodney Square, Suite 404, an address publicly associated over the years with the DEA, the Department of Justice, and the Secret Service; some posters describe it as a joint DHS/FBI/DEA office. According to Candace Owens, an Israel/Egyptian plane landed and stayed overnight on September 10 (assassination day), with an alleged foreign-dignitary pickup transferred to 920 N King St. Researchers connect this to claims that a foreign dignitary may have been shuttled from Provo to Wilmington for a joint US/foreign operation on the day of the assassination. Some X threads have gone further and speculated about the identity of a possible passenger, naming a veteran Egyptian diplomat — but that is unverified online speculation about a living person who has not been charged with anything, and no evidence ties any named individual to the flight.
The Kansas return claim
After the September window, @ProjectConstitu (Project Constitution) posted that SU-BTT had returned to the United States — routing from Paris-Le Bourget (LBG) into Wichita, Kansas (ICT). The post was headlined: "BOMBSHELL: The ASSASSINATION Plane From Sept 10th Is Back — EGYPTIAN Military Aircraft SU-BTT Just TOUCHED Down in Kansas." The thread raised questions about possible "special cargo" and meetings, noting Wichita's status as an aerospace and defense hub.
The plainer reading of the same landing is laid out in the counterpoints below: Wichita is a major Falcon-maintenance center, so a Falcon 7X touching down there is also what a routine service relationship would produce. The claim is reported here as the tracker's framing, not a confirmed connection to the case.
The Sharm El-Sheikh tarmac claim (October 13, 2025)
10:45 — Fox News live coverage of the October 13, 2025 Gaza summit arrival at Sharm El-Sheikh, followed by a Candace Owens podcast segment on the Provo stop, SU-BTU, and an alleged passenger alias. Source: @ProjectConstitu on X, August 16, 2026. If the player does not load, watch the original on X.
On August 16, 2026, the account @ProjectConstitu (Project Constitution) posted a claim that the same aircraft appears in mainstream broadcast footage from the October 13, 2025 Gaza peace summit at Sharm El-Sheikh, Egypt — parked on the tarmac near Air Force One. The post is reproduced below nearly in full, as the poster's own words:
‼️BOMBSHELL: The SAME Egyptian Presidential Plane Candace Owens Flagged in Provo the DAY Charlie Kirk was Assassinated Was Sitting On The Tarmac NEXT TO AIR FORCE ONE in Sharm El-Sheikh On Oct 13th.
On October 13, 2025, during the Gaza peace summit, Fox News live coverage shows Egyptian President Abdel Fattah el-Sisi's motorcade pulling up as Air Force One lands. Right there on the tarmac? SU-BTT. This is the exact tail number Candace exposed.
Let's recap the receipts she already dropped:
• SU-BTT (the "yellow" Egyptian Falcon) landed in Provo on September 4, 2025 — six days before Charlie was killed • It carried a group of Egyptian military contractors
• Those contractors deplaned in Provo • The plane then left for Wilmington, Delaware on the morning of September 10 with only four people on board — the contractors were gone • Those same contractors got rental cars from Duncan Aviation at the Provo FBO
Candace was mocked for "time zone mistakes." She was told it was "just maintenance."
Now we have live Fox News footage from the Egyptian presidential summit showing SU-BTT parked next to Air Force One while el-Sisi greets Trump.
This is not a random charter. This is Egyptian presidential fleet.
So why was a plane from the Egyptian President's fleet sitting in Provo, Utah the week Charlie Kirk was assassinated… dropping military contractors who then vanished into rental cars from Duncan Aviation? The official narrative still wants you to believe this is all a coincidence and Charlie Kirk was assassinated by lone wolf shooter Tyler Robinson It's not.
The post reported 108,133 views, 2,506 likes, 647 reposts, 337 bookmarks, 110 replies and 41 quotes at the time of capture.
The "presidential fleet" inference is the poster's own reading of the footage. An Egyptian VIP aircraft being present at an Egyptian-hosted summit attended by the Egyptian president is, on its face, exactly what one would expect regardless of anything that happened in Utah — and the footage does not establish who was aboard the aircraft in Provo, or why. It is reported here as the tracker's claim.
Full transcript of the video
The following is the complete machine transcript of the 10 minute 45 second video attached to the post, reproduced without cuts. The first portion is Fox News anchor commentary over the Sharm El-Sheikh arrival; the remainder is a Candace Owens podcast segment. Everything in it is the speakers' own words and represents their claims, not established fact. Machine transcription introduces spelling errors in proper nouns — "El Cisi" is el-Sisi, "Dunkin Aviation" is Duncan Aviation, "Probo" is Provo, "LCC" is el-Sisi, "Dave Trolley's assassination" is a garble of "the day of Charlie's assassination," and "Riyad" is Riyadh.
This is the Egyptian president Abdel Fatah El Cisi. I went over to Egypt. I interviewed him early after he took over in June of 2014. He has always wanted to be at the center of some of... the Middle East discussions of how things go forward. So this is a big moment for Egypt as well to be able to host this Gaza Accord and all of these world leaders as they look for the future. And to Martha's point, I think that's a great point about Russia and China. him early after he took over, uh, in, uh, June of 2014. He is always wanted to be at the center of some of the Middle East discussions of how things go forward. So this is a big moment for Egypt as well. to be able to host.
So I reported that on the day of Charlie Kirk's assassination, an Egyptian Air Force plane took off from Provo, Utah Airport. I reported that even more curiously, that Egyptian military plane had previously only ever been to the United States twice in that past year, and both times, it was in the lead up in the weeks leading up to Charlie's assassination. Okay? Here is that plane, the tail number you can see here is S-U-B-T-T. And this is a screenshot again from flight radar. Now, of course, when I pointed out that this foreign military plane arrived on September 4th, so 6 days before into Provo, Utah, and departed 6 days later on September 10th, they ignored the huge substance of this, which is why is this Egyptian military plane here in the middle of Utah? Instead, they said, oh, she made a time zone mistake, like as if I'm on flight radar every day, accustomed to reading the data here. Yeah, I thought that I was looking at mountain time, like local time on flight radar. As Mark just explained, no, they do it according to Universal Time. Okay, big deal. like actually big deal.
Anyways, I was going through the DCIA tips box, you know, our decentralized intelligence agency, tips box, and I found a very interesting email. I'm going to be very careful here to make sure I don't give this person away, but it was someone from a foreign country. They wrote us claiming to have intimate knowledge regarding the flight. And you can take what I'm about to tell you to the bank, okay? In fact, you can even take this as a direct challenge to Cash Patel to dispute what I am going to say. And I feel that I have been presented with absolute solid proof from this individual who is in proximity to one of the individuals that was aboard this flight. Okay?
I can now report to you that it is a fact that on 94, there were, um, this was not some dropping by in Utah, as they were trying to claim because the plane needed to be serviced. That's what they ran with. They ran with. This could have been a routine servicing. I guess there's just no place from Egypt. All the way to Utah that an Egyptian military plane can like get a tire changed. This is totally routine. Nothing you see here. Well, I'm telling you that for a fact, that plane was carrying military subcontractors. And for a fact, they were dropped off in Provo, okay? And that they did not make it back to Cairo. They showed you. I showed you the plane left. Um, they left on September 10th. It then laid over in Wilmington, Delaware, and departed back for Cairo on the 11th. I am telling you that when that plane left. Okay? Those people were mysteriously missing from that plane. Okay? What's going on here? Why are Egyptian military subcontractors, what are Egyptian military subcontractors doing in the middle of Provo, Utah on the day that Charlie Kirk was assassinated? You should be concerned.
And I'm going to give more cause for concerns, okay? Because as you guys will recall, to Egyptian planes. We got it. For the sake of ease, we've labeled one blue, that's S-U-B-N-D, which was the one that was transponding on the ground. At Dunkin Aviation on the day of Charlie's assassination, but it did not go anywhere. And then, of course, our now infamous yellow plane that carried on to Delaware, Wilmington, Delaware that morning. and has seemingly panicked the world, right? I'm reminding you that that flight from Provo to Delaware on the yellow plane had only 4 people on board. Okay? So that plane pretty much emptied out and then had only 4 people, one of which was a foreign dignitary.
Now, one of those individuals, I can confirm, was using the name, and when I say using the name, we are dealing with governments. We are dealing with power and these people just print passports, okay? These are obviously dead ends. But the name that one of those individuals was using is Walid Makmud. Okay? Waleid Makmud. So we now know that of the 4 people that flew to Delaware, someone flew using the name Walid Makmud. Okay? here is where it is going to get interesting. And I don't know if we can show that name. Chris, if we have that, but we can spell that out for them. I don't know if we have a graphic for that.
But here's where it gets interesting. Okay? Wali, Machmood, had been in Provo before. Okay? Specifically, Wali Makmood came to Provo on May 27th of this year, while Lid Makmood came in, and, uh, we can also confirm that if you look up the plane that he was on, there is no transponder data which reflects that trip. He was not on the yellow plane. This is what's very interesting. He was aboard another Egyptian military plane. And the tail number for that plane is S-U-B-T-U. We're going to make that the purple plane, okay? Purple plane was not there on Dave Trolley's assassination, but we now have a person that was on that purple plane, uh, at the end of May, and then, uh, he is going to be on that plane again on the day of Charlie's assassination, both times in Probo.
And we can drop that now into our timeline, okay? May 27th, SUBTU flies into Provo, with Wali Makmuda board. Maybe it's a pilot. I don't know. Then we've got it departs on June 2nd and it is not transponding. Okay? So you cannot find a record of this on flight radar.
Now, why is this compelling? Why is this especially compelling? Because the purple plane, SUBTU, as has been recently discovered by the work of other people, uh, was once upon a time flown with the president of Egypt aboard. And by once upon a time, I mean back in 2023. This tweet came from project Constitution, I'm going to read it in its entirety, okay? Confirmed. Candace Owens just got vindicated again. The Egyptian government website confirms that Egyptian president LCC flew on SUBTU. Remember when Candace Owens dropped that bombshell exposing that Egyptian presidential plane as the mystery bird tied to those shadowy flights and just, you know, he's confusing BTT. He's talking about BTU. We were always talking about BTT. Well, official receipt of receipts just landed straight from the Egyptian presidency website that on April 3rd, 2023, President LCC touched down in Riyad, aboard that same exact aircraft, tail number SUBTU, for a high-level sit down with a Saudi crown prince, Muhammad Bitsalman, okay? So B-T-U. And again, he's mixing it up with BTT, but we can now connect these 2 planes.
Now, before you jump to conclusions, you can go, well, does this solve this? Does this mean that this was the Egyptian president on board? No, we can actually officially rule out that it was President LCC that was aboard the jet on September 10th because he was photographed at a meeting with the Prime Minister of Tunisia, Sarah Zafrani, and it was in Egypt. We can also rule him out as having been the individual that was in Provo back in May because he was, again, photographed multiple times throughout that week in Egypt, okay?
What we can, however, deduce is that Walid Makmud, um, is therefore not the president of Egypt, but he is almost certainly well acquainted with the president of Egypt, because planes that fly presidents around, um, military planes are not going to, you're not going to just, you know, let just some random, wealthy Egyptian aboard your jet, right? This person is going to be well acquainted with the president of Egypt, okay?
So who is Walid Mahmoud? Who is the person using the name Walid Makmoud? That is the question that we are left with. Now, again, maybe Wali is the pilot. That could make sense. But what was he or she doing in Provo at the end of May and into early June? These are questions and honestly, concerns that shouldn't be expressed by me. It should be expressed by every single person at turning point USA, who is interested in getting to the bottom of who assassinated Charlie Kirk. It should be expressed by our government, it should be expressed by the Pentagon and their giggly press secretary and press members. We should be asking this question. Instead, we're just being gaslit.
What is new in this segment
Four claims in the transcript above had not previously appeared on this page. All four are the speaker's assertions, sourced to an anonymous tipster, and none has been independently verified:
- A named tip source. Owens says the passenger information came from an unnamed foreign correspondent to her "DCIA tips box" who claimed proximity to someone aboard the flight, and she frames the resulting claim as a direct challenge to FBI Director Kash Patel to dispute it. An anonymous tip relayed second-hand is not evidence, and Owens does not publish anything that would let a reader check it.
- An alleged passenger name. She states that one of the four people aboard the September 10 Provo→Wilmington leg was travelling under the name "Walid Mahmoud." She herself stresses she is describing a name in use, not a verified identity, saying governments "just print passports" and calling such names "obviously dead ends." No public record confirms that any person by that name was aboard, no such person has been identified, charged, or accused of anything by any authority, and nothing here should be read as alleging that any individual — real or otherwise — did anything wrong. She also floats the entirely innocent possibility that the person was simply the pilot.
- A third aircraft: SU-BTU, the "purple plane." Owens says the same name appears on a May 27, 2025 arrival in Provo aboard SU-BTU, departing June 2 with no transponder record of the trip. This is a new date and a new tail number in the Provo pattern, and it is unverified.
- An official Egyptian record tying SU-BTU to the presidency. She reads out a Project Constitution post claiming the Egyptian presidency's own website documents President Abdel Fattah el-Sisi flying aboard SU-BTU to Riyadh on April 3, 2023 to meet Saudi Crown Prince Mohammed bin Salman. Both she and the post she reads acknowledge the tail numbers SU-BTT and SU-BTU are being conflated in some coverage — they are two different aircraft. A head of state using a government VIP jet is unremarkable in itself; the claim's only relevance here is that it would place SU-BTU in the presidential fleet.
Owens is explicit on one exculpatory point, and it belongs in the record: she rules out President el-Sisi personally as the September 10 passenger and as the May Provo visitor, citing photographs placing him at a meeting with the Prime Minister of Tunisia in Egypt on the first date and in Egypt throughout the relevant week on the second.
Candace Owens on transponder-off flights to Israel (December 18, 2025)
1:19 — Candace Owens saying the Egyptian jets fly in and out of Israel with transponders off. Source: @ProjectConstitu on X, December 18, 2025 — the post quoted by the August 2026 post above. If the player does not load, watch the original on X.
The August 2026 post quotes an earlier December 18, 2025 post from the same account, which carries its own video. That earlier post reported 442,318 views, 2,560 likes, 922 reposts, 273 bookmarks, 92 replies and 23 quotes. Its text, reproduced nearly in full:
🚨BOMBSHELL: Egyptian Planes Tied DIRECTLY TO ISRAEL – Hidden Flights & Transponder Blackouts Revealed PROVE Candace Was Right! 🇪🇬✈️
My team was able to directly corroborate Candace Owens' claims about the SUSPICIOUS Egyptian-registered planes linked to events surrounding TPUSA Faith Events and specifically following Erika & Charlie Kirk. Candace recently stated with confidence that these planes frequently operate routes to and from Israel, routinely disabling transponders to obscure their movements—a pattern that explains the extraordinary defensive reactions whenever the topic arises.
Compelling evidence now confirms this assertion.
The aircraft registered SU-BTT completed a flight from Cairo to Israel on October 21, 2025, as verified by FlightRadar24 tracking data. This movement was independently reported by Israeli media outlet Channel 12 News, which noted: "An aircraft used by the head of Egyptian intelligence, Hassan Rashad, arrived today in Israel from Cairo." This documented instance aligns precisely with the operational profile Candace described: Egyptian registry serving sensitive routes involving Israeli interests. The absence of a comparable Egyptian advocacy presence in the United States underscores that the intense backlash originates from concerns tied to Israel.
This development provides crucial context to the broader investigation and demands further independent scrutiny.
A comprehensive timeline and additional documentation from @RealCandaceO dropping soon. Stay locked.
This connection cannot be dismissed. The facts are emerging, and the public deserves full transparency.
Make sure you are following my main man @nihilox Who's brilliant work led to this bombshell discovery. His work has been integral o this investigation.
Drop a ✈️ if you see the Israel connection clear as day. RT & Share this evidence widely—the truth is gaining momentum.
The October 21, 2025 Cairo→Israel leg described here is the same one covered in the Reported flights to Israel section above — the one leg with mainstream corroboration. The poster's framing that this "PROVES" the wider transponder-blackout pattern does not follow: one documented flight does not establish the roughly thirty other legs on the compiled list, and an Egyptian intelligence chief travelling to Israel is consistent with the two countries' long-standing security relationship.
Full transcript of the video
Complete machine transcript of the 1 minute 19 second clip, reproduced without cuts. These are Candace Owens's own words on her program and represent her claims, not established fact:
I feel very confident that I know why these planes have caused such panic, and it is because there is overwhelming evidence that these planes regularly fly in and out of Israel. And I'm going to present that evidence tomorrow, evidence tomorrow. I say that strongly. This is the, like, I feel very confident saying these Egyptian planes are flying in and out and notice I'm saying planes because once I was able to connect people that were on those planes onto other Egyptian planes, I was able to realize that these planes are flying in and out of Israel and turning their transponder off each time that they do it. That is now makes perfect sense of why there was this mass panic, right? It's not exactly like we have a strong Egyptian lobby. In the United States. Now we're like, whoa, well, those darn Egyptians, again, are trying to get TikTok censored. I mean, every person in the game, Barry, acting. Well, these are the usual suspects that act if something is a threat to Israel, okay? Which is they should have just been forthcoming, pretended that it was changing apart. Instead, they're trying to gaslight us and they're actually frankly just pissing me off. So I became locked in on these Egyptian planes because that's how I am. okay? You keep pushing me and keep pushing me. I will become an expert on these planes. I'll learn how to build an Egyptian plane. And the reality is, like I said, tomorrow I will show you how these planes tie back to Israel.
Note that the method she describes — connecting people across aircraft — is the same method that produces the SU-BTU claim in the August 2026 segment above. If the passenger identification underpinning it is wrong, both claims fall together.
The Terry Tut flight-data analysis (August 2026)
6:25 — Flight-data walkthrough of SU-BTT, SU-BND, and a US ISR contractor jet around September 10, 2025. Video by @Tut21125150 (Terry Tut) on X, August 16, 2026, shared by @MysticMuse1o1. If the player does not load, watch the original on X.
A separate independent analysis circulated on August 16, 2026 by @Tut21125150 (Terry Tut), under the caption "About those Egyptian 🇪🇬 planes ✈️" — 21,962 views, 1,475 likes, 336 reposts, 554 bookmarks. It was surfaced into the Project Constitution thread by @MysticMuse1o1, who wrote:
@ProjectConstitu @RealCandaceO @baroncoleman I don't have a direct link, TerryTut shared the video @GlamHamRadio is also the one who found the google search of the reserved parking spot at UVU that was searched by the license plate # for the pres.
This analysis matters because it is the first on this page to correct the Owens timeline rather than simply amplify it, and because it introduces an aircraft that is not Egyptian at all. As with everything else here, it is an independent researcher's reading of public ADS-B data, not an official finding — and the author says so himself, repeatedly and unprompted.
Full transcript of the video
Complete machine transcript of the 6 minute 25 second video, reproduced without cuts. Machine transcription garbles tail numbers and proper nouns throughout — "SU Bravo November Delta / Sue B&D / Subiendi / Sue BND / SUBND" are all SU-BND; "SU Bravo Tango Tango / Sue BTT / Sioux BTT" are all SU-BTT; "Axel 10" is the callsign AXL10; "Lasai" is L3Harris or a Leidos subsidiary as the speaker intends it; "Lidos" is Leidos; "my not" is Minot; "the RM UVU corridor" is a garble; "indicates emission" is likely "indicates a mission." These are the speaker's own words and represent his claims, not established fact:
Candace, the planes, maybe sit down because there's more. Candace highlighted 2 Egyptian planes. Many people have tagged me, so I looked into them too, and when I did, my jaw dropped. 1st a quick clear up of the timestamps from the gentlemen sharing flight details on Candace's show, on September 10th, Utah was -6 of UTC, not -7 because of daylight savings, so everything I'm about to say is in the correct Utah Mountain local time.
So Egyptian planes, to give you an idea of how rare it is, in the entire United States today, there is one that pops up, but September 10th, not one but 2 Egyptian state-owned jets. SU Bravo November Delta. I'm going to go with Sue B&D, and SU Bravo Tango Tango, which I'll call Sue BTT. These are not tourism jets. They are military, government, transport aircraft. These aircraft normally land at major diplomatic or military hubs, not small regional airports. Their presence at Provo Airport would require special U.S. clearance and is highly unusual.
Not only were both of these jets at Provo on September 10, but separately, both of them arrived via Minot Air Force Base. This is America's only nuclear-based that holds 2 out of the 3 US nuclear triad. If it's press the button time, this base is key. One of these planes was only on the ground for less than an hour, type for refueling, but might work when something or someone needs to be picked up, dropped off, or something or somewhere needs to be authorized, and the very next stop for both of these planes after going wheels up from my not nuclear Air Force Base. was Provo.
And by the way, SUBND landed at Provo May 23rd, 2025 and stayed till September 14th. A foreign state aircraft, hanging out at a regional airport for nearly 4 months. Subiendi also did this on September 5th, 5 days before the assassination. So BND flew a straight corridor north of Provo, and then came straight back. It did not land anywhere. Analysts would call this a mapping run, an electronic surveillance sweep, sensor calibration, or an intelligent flight conducted under special clearance.
Then, on September 14th, it finally left Utah for Goose Bay, Newfoundland, which is a strategic NATO linked location, and even its departure from Provo, raised a little eyebrows. Sue B&D was supposed to leave on September 14th just after midnight, but sat on the ground for nearly 19 more hours before eventually taking off. Diplomatic aircraft movements normally are tightly controlled, so a big delay could mean something held the plane there, or something needed to happen before it was cleared to depart.
Believe it or not, this will get stranger, with Axel 10. On September 10th, the day Charlie was shot. A USISR contractor jet shows up in the mix. Axel 10, a bombardier global 6500 operated by Lasai, which is owned by Lidos, a major military intelligence contractor, tied to the army's Hades deep sensing program, which means detect, map, track signals, communications, electronics, and activity, far beyond the line of sight, from dozens to even 100s of miles away.
On September 10th, Axel 10 made 2 extremely low passes. I calculated as low as 210 feet above ground level, directly aligned within roughly 3 miles of UVU. Once at 9.15 AM, about 3 hours before Charlie was shot, and again at 1248 p.m. local time, about 25 minutes after. A jet like this normally flies at 30, 40, 50,000 feet. And remember, when we see barometric altitude, that is height above sea level, when we take away the elevation of Provo, and the lake the plane is flying over, that's how we arrive at 2 to 300 feet above ground level, which is crazy low, and analysts would probably say indicates emission.
I pulled the KML files for both of the Axel 10 flights. And I wanted to show you how flawlessly aligned that dippers with the RM UVU corridor, both flights, pass the exact airspace and do the same deep dip. Extremely precise behavior and airspace. Either side of Charlie Kirk's assassination.
And still, it gets stranger. At 1308 UTC Universal Time Coordinated, which is 708 AM in Utah on September 10th, Sioux BTT, begins departure from Provo, 708 AM at the same minute, according to its track, Axel 10 pops up on flight radar, wheels on the ground in El Paso for its departure, which will ultimately make that 1st deep dip. Within miles of UVU. These are unrelated aircraft, right, an Egyptian military government plane linked to Minot Air Force Base, and a US jet tied to deep sensing ISR programs. Both planes, 100s of miles apart. Besides the coincidental departure time. They also have in common the location of Provo on the day of the assassination of Charlie Kirk. Statistically unusual, which does not mean coordinated. I want to make that point, and we're not even done with the high strangeness.
Sue BND, the other Egyptian jet that had been sitting dormant in Provo since May 23rd. On the morning of September 10th, sent a handful of ground pings, as seen on Candace, but Subi ND did not take off. It is already unusual for a foreign state aircraft to be at Provo for months. So after being electronically silent, pinging on September 10th, The day of Charlie's shooting is again unusual.
None of this proves a cause, a perpetrator, coordination, but this is real flight data verifiable, and irregular. At a minimum, we're looking at overlapping intelligence grade activity in the air corridor of an assassination. Let me know what you think, and Candace, I really hope this helps you. I am so sorry you lost your friend. I'll see you in the comments. Take care.
What is new in this analysis
Six claims here do not appear elsewhere on this page. All are the author's readings of public ADS-B data and none is independently confirmed:
- A timestamp correction, not an amplification. He opens by correcting the flight-detail presenter on Owens's show: Utah was UTC−6 on September 10, not UTC−7, because of daylight saving. This is the same time-zone objection skeptics raised against Owens — and here it is being conceded and fixed by someone sympathetic to the investigation, then his own timeline is rebuilt on the corrected offset. That makes his 7:08 AM departure figure consistent with the first of the three competing Sept 10 departure accounts listed earlier on this page.
- Both Egyptian jets routed through Minot Air Force Base. He says SU-BTT and SU-BND separately arrived via Minot AFB, North Dakota — a nuclear-mission base — with Provo as the next stop after each, and one of them on the ground under an hour. This is a new leg not previously described here, and it is a claim about a US military airfield rather than a civil one.
- A revised SU-BND stay: May 23 – September 14, 2025. Nearly four months, with departure to Goose Bay, Newfoundland. This page elsewhere describes the SU-BND stay only as "nearly four months" without dates; these are specific, checkable ones.
- A September 5 "mapping run." He says SU-BND flew a straight corridor north of Provo and returned without landing anywhere, which he characterizes as consistent with a mapping run, an electronic surveillance sweep, sensor calibration, or a flight under special clearance. He offers these as analyst-style interpretations, not as a determination.
- A 19-hour departure delay. SU-BND was set to leave just after midnight on September 14 but reportedly sat for nearly 19 more hours.
- AXL10 — a US ISR contractor jet, not an Egyptian one. This is the largest new element. He describes a Bombardier Global 6500 flying as AXL10, operated by a contractor he ties to Leidos and to the US Army's HADES deep-sensing program, making two passes as low as ~210 feet above ground level within roughly 3 miles of UVU — one at 9:15 AM, about three hours before the shooting, and one at 12:48 PM, about 25 minutes after. He says he pulled the KML files for both flights and that the two tracks repeat the same dip over the same airspace. He also notes AXL10 showed wheels-on-ground at El Paso for departure at the same minute SU-BTT began its Provo departure, 7:08 AM local.
The HADES program is real and publicly acknowledged — the US Army's High Accuracy Detection and Exploitation System, a Bombardier Global 6500-based deep-sensing ISR aircraft program, with Leidos as prime integrator. That the aircraft type and program exist does not establish that this particular flight did what is claimed, that the altitude calculation is correct, or that it has any connection to the assassination.
The author's own caveats are as important as his findings, and he states them unprompted: "Statistically unusual, which does not mean coordinated. I want to make that point" and "None of this proves a cause, a perpetrator, coordination, but this is real flight data verifiable, and irregular." His stated conclusion is deliberately limited — "at a minimum, we're looking at overlapping intelligence grade activity in the air corridor of an assassination" — and this page carries it at exactly that strength. See also ISR Operations and SU-BND.
A caution specific to the altitude claim: ADS-B reports barometric altitude above mean sea level, and the author is explicitly subtracting local terrain and lake elevation to reach 210 feet AGL. That arithmetic is the right approach, but it is highly sensitive to which terrain figure is used and to barometric error, and a 200-foot pass by a large business jet is an extraordinary claim. Independent verification against the raw ADS-B Exchange track would settle it either way.
Counterpoints and innocent explanations
In fairness, several facts cut against the sinister reading:
- Provo has a legitimate jet-service hub. Duncan Aviation runs a full-service maintenance, repair, and overhaul (MRO) facility at Provo Municipal Airport — airframe, engine, avionics, paint, and interior work. A foreign VIP Falcon stopping there for service is not inherently suspicious.
- The Wichita stops fit aircraft maintenance, not surveillance. Researchers note SU-BTT made "no fewer than 8 stops" in Wichita, Kansas — but Wichita is the "Air Capital of the World," home to major aviation-maintenance operations including Yingling Aviation, an FAA Part 145 facility that services Dassault Falcon jets (with Dassault-Wichita State University ties dating to 2015). Repeated Wichita visits by a Falcon 7X are exactly what a routine maintenance relationship would produce.
- Liz Wheeler's "loose criteria" rebuttal. Commentator Liz Wheeler argues the overlap spreadsheets count a match whenever an Israel/Egyptian plane is within roughly ±3 days and the same broad region (50–100 miles) — not the same day at the same airport. In her telling, "when you narrow the parameters to Egyptian planes landing on the same day in the same location, the overlap dwindles to… one. On 9/10 in Utah." Other reviewers add that many entries contain UTC-vs-local time errors and wrong-location/wrong-continent mistakes, with one estimate that a large share of the listed overlaps are incorrect.
- A skeptic's audit of the logs. At least one reviewer who pulled a year of FlightRadar history said "5 of the 8" overlaps Owens cited were wrong — claiming the plane had not even left Egypt on some of the dates — and noted that Erika Kirk herself said she stayed home in Arizona on Sept 10 rather than being in "Nebraska/Delaware." That reviewer disputed the "73 overlaps" framing entirely.
- SU-BND stayed for months. The companion "blue plane" reportedly sat in Provo for nearly four months, which fits a long maintenance or storage stay more than a surgical operation.
- John Cullen walked back the "strong association." In later notes, investigator John Cullen — who had earlier speculated about a drone link — is reported to have dismissed a strong association between SU-BTT and the assassination, pointing to long-standing Duncan Aviation maintenance contracts said to date back to 1999 and characterizing some legs as routine ferrying flights. Critics also note a Dassault Falcon is not serviced every two weeks, so the maintenance-versus-conspiracy question turns on how often a VIP jet realistically visits an MRO — a debate, not a settled point.
- The extra evidence never fully materialized. Skeptics say much of the additional corroboration Owens promised — beyond the screenshots — never fully materialized in the form critics could check.
- Transponder gaps and "materializing" tracks can result from terrain shadowing, receiver coverage gaps, and trackers snapping an origin to the nearest public field — mundane data artifacts, not proof of a stealth launch.
Open questions
- Who authorized SU-BTT's operations during the Sept 4–11 US visit, and if the Dugway claim is real, who cleared it onto a restricted military airfield?
- Who were the passengers, and is there any manifest for the Sept 4 arrival and Sept 10 departure?
- Which of the three Sept 10 departure timelines (7:08 AM, the 9:05 AM "go dark," or the Dugway origin) is correct?
- What was the purpose of the Wilmington destination on the day of the assassination?
- Do the "counter-UAS" and "DoD Liaison" witness claims survive any documentary check, or are they unsupported?
- Is there any manifest, customs record, or FBO log for the May 27 – June 2, 2025 SU-BTU visit to Provo that Owens describes, and does it list the name she reports?
- Does the Egyptian presidency's own website in fact document President el-Sisi aboard SU-BTU on April 3, 2023, and if so does that make SU-BTU part of the presidential fleet in any operational sense?
- Does the October 13, 2025 Sharm El-Sheikh broadcast footage actually show SU-BTT, and is a frame-level identification of the tail number possible from the video?
- Did SU-BTT and SU-BND each route through Minot Air Force Base before Provo, and if so who granted a foreign state aircraft access to a nuclear-mission base?
- Does the raw ADS-B Exchange track for AXL10 on September 10, 2025 support two passes at roughly 210 feet AGL within three miles of UVU, once at 9:15 AM and once at 12:48 PM?
- What was SU-BND doing on the reported September 5 out-and-back corridor flight north of Provo with no landing, and why did its September 14 departure reportedly sit 19 hours past its slot?
The full Flightradar24 flight history, leg by leg
Almost every dispute on this page turns on what SU-BTT actually did, and almost every published account works from a summary rather than the log. A complete Flightradar24 flight-history export for this tail, compiled and watermarked by @WeAre_TheElite and circulated alongside the same account's exports for the four sister aircraft, gives the raw legs. It is reproduced here in full for 2025, because the shape of the record is the argument.
The aircraft's registry panel in that export reads:
| Field | Value |
|---|---|
| Aircraft | Dassault Falcon 7X |
| Type code | FA7X |
| Mode S / ICAO hex | 0101D3 |
| Serial number (MSN) | 239 |
| Airline (as listed) | Egypt Government |
| Operator (as listed) | Egypt - Air Force |
| Operator code | EGY |
| Age (Nov 2013 build) | 12 years |
That is the durable identity for this airframe — hex 0101D3, MSN 239 — and it is what any future audit should match on rather than the printed registration.
The three United States visits in 2025
Times below are as displayed in the export. Flight durations are the tracker's own.
| Date | From | To | Duration |
|---|---|---|---|
| 19 Jul 2025 | Cairo (CAI) | Paris–Le Bourget (LBG) | 4:10 |
| 20 Jul 2025 | Paris (LBG) | Omaha (OMA) | 9:10 |
| 20 Jul 2025 | Omaha (OMA) | Lincoln (LNK) | 0:16 |
| — six days on the ground at Lincoln — | |||
| 26 Jul 2025 | Lincoln (LNK) | Wilmington (ILG) | 2:07 |
| 27 Jul 2025 | Wilmington (ILG) | Cairo (CAI) | 10:19 |
| 16 Aug 2025 | Cairo (CAI) | Paris (LBG) | 3:56 |
| 17 Aug 2025 | Paris (LBG) | Omaha (OMA) | 8:48 |
| 17 Aug 2025 | Omaha (OMA) | Lincoln (LNK) | 0:15 |
| — six days on the ground at Lincoln — | |||
| 23 Aug 2025 | Lincoln (LNK) | Wilmington (ILG) | 2:05 |
| 24 Aug 2025 | Wilmington (ILG) | Cairo (CAI) | 10:07 |
| 03 Sep 2025 | Cairo (CAI) | Paris (LBG) | 4:03 |
| 04 Sep 2025 | Paris (LBG) | Minot (MOT) | 8:52 |
| 04 Sep 2025 | Minot (MOT) | Provo (PVU) | 1:39 |
| — six days on the ground at Provo — | |||
| 10 Sep 2025 | Provo (PVU) | Wilmington (ILG) | 3:37 |
| 11 Sep 2025 | Wilmington (ILG) | Cairo (CAI) | 9:43 |
The September 10 Provo→Wilmington leg is logged with STD 10:51 AM, ATD 7:14 AM, STA 11:51 AM — the 7:14 a.m. actual departure being the figure that matches the "7:08 AM" account listed among the three competing departure timelines earlier on this page, and matching the "departed Provo, UT at 7:14am local time" line in the Owens-team timeline. It is roughly five hours before the shooting.
What the shape of that record actually shows
Read as a whole rather than as a highlight reel, the log has a very regular structure, and it is not the structure of a surveillance mission:
- Every US visit is the same trip. Cairo → Paris-Le Bourget → one US city → sit for six days → Wilmington → Cairo. Three times in three months, to the day-count.
- The 15- and 16-minute Omaha→Lincoln hops are positioning flights. Omaha and Lincoln are about 50 miles apart. A wide-body-class business jet does not fly a quarter-hour hop between two Nebraska cities for any operational reason except to reposition to a facility. Both July and August visits do it.
- Wilmington (ILG) is on the way out every single time, and only ever on the way out. Wilmington is a well-known customs and fuel stop for transatlantic business aviation. Its recurrence is what an outbound clearance point looks like, not what a destination looks like.
- The six-day dwell is constant across all three visits regardless of city — Lincoln, Lincoln, Provo. A tasking that was following a person would produce variable dwells tracking that person's schedule. A tasking that is work being done on the aircraft produces a roughly fixed turnaround.
None of that is exculpatory in itself, and the September 4–10 Provo stay is the one visit that lands somewhere other than the two Nebraska fields. But it means the honest question on this page is narrower than the one usually asked: not why was this jet in America, but why was this one visit to Provo instead of Lincoln.
The rest of 2025 — an aircraft that mostly does not leave Egypt
The same export lists the aircraft's non-US activity, and the volume is instructive. Between January and November 2025 SU-BTT logged repeated short sectors that are overwhelmingly Cairo (CAI) → Cairo (CAI) round-robins of 15 to 45 minutes, plus regional runs to Medina (MED), Jeddah (JED), Sharm el-Sheikh (SSH), and El Arish (AAC) — the last flown under the callsign EGY239, matching the airframe's serial number. Examples from the log: Apr 05 and Apr 08 as EGY239 Cairo↔Cairo and El Arish→Cairo; Apr 26 Cairo↔Jeddah; May 02 Cairo↔Medina; Oct 11 Cairo↔Jeddah; Oct 12 Cairo→Sharm el-Sheikh; Oct 16 Cairo↔Medina; Nov 18 Cairo→Cairo.
The Cairo→Cairo entries of 15–45 minutes are the ones compiled elsewhere as the "transponder-off flights to Israel" list. It is worth being exact about what such an entry is and is not: a same-airport round trip of that length is what a maintenance test flight, a training circuit, or an airborne systems check looks like. It is also what a short out-and-back with the transponder disabled over the leg would look like. The log alone cannot distinguish them, and neither can anyone reading it. That is precisely why the one leg with independent corroboration — the October 21, 2025 Cairo→Israel flight reported by Israeli Channel 12 — carries more weight than the other thirty on the compiled list combined.
Duncan Aviation has held an Egyptian Air Force maintenance contract since 1999 — and its main plant is in Lincoln, Nebraska
This is the single most consequential piece of context on this page, and it has been almost entirely absent from the discussion.
A Duncan Aviation press release dated Thursday, 10/29/2015, 14:31, carried by the trade publication DOM — Director of Maintenance, is headlined "Duncan Aviation Signs a Five-Year Contract With the Egyptian Air Force." Its text:
…announces the company has entered into a five-year direct contract agreement with the Egyptian Air Force (EAF) for aircraft maintenance services. Duncan Aviation has been managing the maintenance and repair of the EAF fleet of Falcon 20 aircraft since 1999.
Duncan Aviation's Manager of Government & Special Programs Dave Shipperbottom says the fact that the EAF has chosen to fly over closer maintenance companies and bring their aircraft to Duncan Aviation "reveals a lot about our relationship with them. All the technicians at the squadron level are great to work with. They know us and we know them. It is a good relationship."
The first EAF aircraft arrived at Duncan Aviation's Lincoln, NE, facility on October 20 for a Z-check. The next will arrive in November for a C-check, Major Corrosion Inspection and complete paint.
For more information, visit Duncan Aviation at booth #N4910 during this year's NBAA convention to be held Nov. 17-19 in Las Vegas…
Set that against the flight log above and the fit is exact:
- Lincoln, Nebraska is the destination of every one of the repeated Nebraska visits. Omaha is not the destination; it is the international arrival airport, and the jet immediately hops fifteen minutes west to Lincoln. Duncan Aviation's Lincoln plant is the endpoint.
- The Egyptian Air Force has been flying its aircraft to that specific plant since 1999 — a twenty-six-year relationship, on the record, in a trade press release published a decade before this case.
- Duncan's own manager anticipates and answers the obvious objection in the quote itself: the EAF "has chosen to fly over closer maintenance companies" to get there. The long ferry is the documented norm, not an anomaly.
- The visit types named — Z-check, C-check, Major Corrosion Inspection, complete paint — are multi-day to multi-week events. A six-day dwell is at the short end of that range and entirely ordinary for a lighter scheduled inspection.
This does not explain the Provo stop, which is the only US destination in the 2025 record that is not Lincoln. But it substantially explains Omaha, Lincoln, Wichita, and the recurring Wilmington clearance stop — which between them account for the large majority of the "overlap" entries in the shadowing spreadsheets. Any tally that counts a Lincoln arrival as an overlap with a Kirk or TPUSA event in Nebraska is, on this evidence, counting a maintenance rotation that predates Charlie Kirk's public career by roughly fifteen years.
The counter-argument is available and should be stated: a long-standing maintenance relationship is also exactly the cover an operational flight would use, and Duncan Aviation runs a facility at Provo Municipal Airport as well as at Lincoln, which is the innocent explanation already offered for the September stay. Neither reading can be settled from the flight log. But a reader who did not know about the 1999 contract was being asked to find the Nebraska pattern mysterious, and it is not.
The Provo visit that Candace Owens attributes to SU-BTU appears in the logs as SU-BTV
Owens's August 2026 segment, transcribed in full above, builds a chain: a name allegedly used aboard the September 10 flight was also, she says, in Provo on May 27, 2025, arriving aboard SU-BTU and departing June 2. She calls SU-BTU "the purple plane." That May 27 – June 2 window is load-bearing for her argument, because it is what links a person across two aircraft.
The @WeAre_TheElite Flightradar24 exports place that exact window on a different tail:
| Date | From | To | Aircraft | Duration |
|---|---|---|---|---|
| 26 May 2025 | Cairo (CAI) | Paris (LBG) | SU-BTV | 4:05 |
| 27 May 2025 | Paris (LBG) | Minot (MOT) | SU-BTV | 8:03 |
| 27 May 2025 | Minot (MOT) | Provo (PVU) | SU-BTV | 1:55 |
| 02 Jun 2025 | Provo (PVU) | Wilmington (ILG) | SU-BTV | 2:11 |
| 03 Jun 2025 | Wilmington (ILG) | Cairo (CAI) | SU-BTV | 11:11 |
And the same exports place SU-BTU's Provo visit six weeks earlier:
| Date | From | To | Aircraft | Duration |
|---|---|---|---|---|
| 07 Apr 2025 | Cairo (CAI) | Paris (LBG) | SU-BTU | 4:20 |
| 08 Apr 2025 | Paris (LBG) | Minot (MOT) | SU-BTU | 8:11 |
| 08 Apr 2025 | Minot (MOT) | Provo (PVU) | SU-BTU | 1:43 |
| 14 Apr 2025 | Provo (PVU) | Wilmington (ILG) | SU-BTU | 3:19 |
| 15 Apr 2025 | Wilmington (ILG) | Cairo (CAI) | SU-BTU | 10:10 |
If those exports are accurate, then the aircraft in Provo on May 27 was SU-BTV, not SU-BTU, and the dates Owens gives — arrival May 27, departure June 2 — match SU-BTV's stay to the day. SU-BTU was at Provo April 8–14.
This is a correction that can be checked by anyone, and it should be checked before it is relied on in either direction: two possibilities are open, and this page does not claim to know which holds. Either the tail number in Owens's account is transposed — SU-BTU and SU-BTV differ by one character, and her own segment acknowledges tail numbers being conflated in this coverage — or the compiled export is wrong. What is not open is treating the SU-BTU identification as settled. Everything downstream of it, including the inference that a person moved between the "purple plane" and the September 10 flight, and the further inference from the Egyptian presidency's website that SU-BTU is a presidential-fleet aircraft, rests on which tail was actually at Provo in late May. If the tail is wrong, the person-across-aircraft link dissolves.
Note the wider point this exposes: five Egyptian-registered jets rotated through the same handful of US fields on the same route template in 2025 — SU-BTT, SU-BTU, SU-BTV, SU-BGM and SU-BND. When five near-identical aircraft fly near-identical routes to the same airports, attributing a given arrival to a specific tail from memory or from a summary is unreliable. The hex codes are the only safe handle: SU-BTT is 0101D3, SU-BTU is 0101D0, SU-BTV is 0101D1, and SU-BND is 01003E.
The rental-car claim, in the claimant's own words
Owens has separately alleged that ground transport for the Provo arrivals was arranged through the same FBO. In a segment circulated by @MJTruthUltra in late 2025, she stated:
There's more. I know something else about the Egyptian flights. This time. Another mommy sleuth. I learned that oddly, Duncan Aviation, you know, where that plane was transponding from, the FBO, and Provo sourced rental cars for these quote unquote Egyptians when they landed a couple of days before this operation. I didn't just learn that, I actually had the license plates number for 4 of the vehicles that they rented.
She then read out four vehicles and plates on air, displaying each as a full-screen graphic:
| # | Vehicle | Plate | State |
|---|---|---|---|
| 1 | Silver 2025 Toyota RAV4 | T092ZS | Utah |
| 2 | White 2025 Toyota Camry | CWN9872 | Arizona |
| 3 | White 2023 Toyota RAV4 | T912KM | Utah |
| 4 | Black 2025 Toyota 4Runner | Z923DA | Utah |
(She read the second plate aloud as "CWNN872" and the third as "TN 12KM"; the on-screen graphics show CWN9872 and T912KM. The graphics are taken as authoritative over the read-out.)
Her closing appeal was a crowdsourcing request rather than an accusation:
Now, to the students at UVU, please check your phones, your pictures from that day because if any of those cars were seen at UVU were around campus on that day, then we're going to be able to suspect something else. Check hotels, maybe gas station, maybe you work somewhere, look at those lights, look for those plates during that time frame from when those cars were there until they departed.
Three cautions belong with this material, and the first is the most important:
- No source is given. The information is attributed to an anonymous tipster ("another mommy sleuth"). No rental agreement, FBO record, or invoice has been published. Duncan Aviation has not commented.
- FBOs routinely arrange rental cars. Sourcing ground transport for arriving crew and passengers is a standard fixed-base-operator service, offered to every customer. That an FBO did so is not itself anomalous.
- These are live license plates on real vehicles. Rental fleet plates rotate among customers constantly; a plate seen anywhere in Utah in that period may have been on a completely unrelated renter's car days later. Nobody associated with these vehicles has been identified, charged, or accused of anything by any authority, and nothing here should be read as suggesting otherwise. Reproducing the plates documents the claim as broadcast; it does not endorse acting on it.
The "Walid Mahmoud" name and a caution about identification
Owens is explicit that the name she reports from her anonymous tipster is a name in use, not a verified identity — "we are dealing with governments… these people just print passports… these are obviously dead ends" — and she floats the innocent possibility that the person was the pilot. That caution needs restating because of what has happened to the name since.
Circulating alongside the SU-BTT material is a screenshot of a Google Scholar profile for Waleed E. Mahmoud, listed as being in the Department of Physics, Faculty of Science, Suez Canal University, Egypt, with a verified email at science.suez.edu.eg and a research area of "Natural science/Physics."
There is no evidence whatsoever connecting that academic to this case. "Waleed Mahmoud" is among the most common name combinations in Egypt — the equivalent of pulling a "James Smith" out of a US faculty directory. An Egyptian materials physicist at a public university has no apparent relationship to a government flight, and none has been alleged by anyone with knowledge. This page names the profile only to mark it as a misidentification and to ask that it stop circulating. He is a private individual, he has not been accused of anything by any authority, and no reader should draw any inference about him from its appearance in this material.
The Provo Airport badge access list
A screenshot of a document hosted at airport.provo.gov circulates in this material — page 4 of 4 of a badge-holder roster, footed "Exported 09/11/25" and "Exported by Inga Jones." The export date is the day after the assassination, which is the reason it draws attention.
The visible rows list organisation, surname, given name, a uniform date of 9/30/2025, and an "x" flag against some entries. Reconstructed from the image, page 4 of 4 holds 37 badge holders across ten organisations:
| Organisation | Badge holders on this page | What it is |
|---|---|---|
| Pilot Makers | 13 | Flight school based at Provo |
| UVU | 7 | Utah Valley University's aviation program, based at PVU |
| Tie-Down | 4 | Aircraft tie-down / ramp services |
| Stone Security | 3 | Security contractor |
| Provo Fire Department | 2 | Municipal fire service |
| Simco Electric | 2 | Electrical contractor |
| Signature Flight | 2 | The FBO — the fixed-base operator that handles transient aircraft |
| Signature Flight / Hangar Tenant | 2 | FBO hangar tenant |
| Smith Detection | 1 | Security screening and detection equipment vendor |
| Westland Construction | 1 | Construction contractor |
| Total, page 4 of 4 | 37 |
Two rows carry an "x" flag — one against a Signature Flight holder and one against a UVU holder. Nothing in the document states what the flag means.
What this document is, and is not:
- It is a badge-holder roster, i.e. a list of people cleared for movement-area access at a public regional airport. It is the sort of record any airport maintains and periodically exports.
- The UVU entries are unremarkable — Utah Valley University runs an aviation program based at Provo Airport, so university staff and students holding ramp badges is expected, not surprising.
- The 9/30/2025 date in every row is not an event date; it appears to be a uniform expiry or review date applied across the roster.
- The 09/11/25 export date is the only genuinely notable feature, and it has at least two readings: someone pulled the list in response to the previous day's events, or the export is a routine periodic one that happens to be dated then. Nothing in the document distinguishes them.
The individual names on this roster are not reproduced here, and that is a deliberate decision rather than an oversight. They are flight instructors, firefighters, electricians, FBO ramp staff, security guards, university students and construction workers, and not one of them has been accused of anything by anyone — not by Candace Owens, not by any poster, not by any investigator, not by law enforcement. They appear in the source solely as rows on an employment access list. There is no allegation here for the word "allegedly" to attach to, and printing thirty-seven private names under a heading about a foreign intelligence aircraft would manufacture the suspicion rather than report it.
Everything in the document that bears on the investigation is in the table above — which organisations held ramp access, how many people each had, the flag column, and the export date. If a specific badge holder is ever publicly named in connection with a specific allegation by a citable source, that name belongs on this site with the allegation attached. Until then it does not.
The document is described so that readers encountering it know what it is: an airport badge list, not a manifest, not a visitor log, and not a record of anyone who was aboard any aircraft. For the full roll of everyone who is named across this material, see Everyone named in the following-planes material.
Bright Star 25 — the US-Egypt exercise running two days before
A slide circulating in this material is a U.S. Air Force news release dated Sept. 8, 2025 — two days before the assassination — from the U.S. Central Command Area of Responsibility:
U.S. Air Force Airmen demonstrated aeromedical evacuation operations to Egyptian Air Force service members during exercise BRIGHT STAR 25, showcasing lifesaving skills in combat and humanitarian environments. The training scenario simulated patient loading and in-flight medical care, giving crews opportunities to rehearse complex, time-sensitive missions.
BRIGHT STAR, first held in 1980, is one of the largest and longest-running military exercises in the Middle East. The aeromedical evacuation training highlighted the U.S.-Egypt partnership.
"It is a great teamwork scenario that requires the crews to work together and mitigate challenges to effectively medically care for patients," said Lt. Col. Jerry M. Earl Jr., an aeromedical evacuation planner assigned to U.S. Air Forces Central Command.
Posters have circulated this release as context for why Egyptian military aircraft would be operating in a US-adjacent posture that week. It cuts in the direction of ordinariness rather than away from it: Bright Star is a forty-five-year-old bilateral exercise, it is conducted in Egypt rather than in the United States, and a routine US-Egypt military relationship is the baseline against which any Egyptian Air Force movement should be read. It establishes that the two air forces work together constantly. It establishes nothing about Provo.
The Egyptian Special Forces spread circulated alongside this tail
A two-page magazine feature titled "Special Forces — Egypt" — part five of a series profiling special forces units around the world — has circulated in this material watermarked @BasedSamParker / @SamParkerSenate. It is background reading an amplifier attached to the Egyptian-aircraft threads, and it is reproduced here in summary so readers can see what was actually shared and weigh it for themselves.
What the article says:
- The Egyptian Armed Forces comprise the Army, Navy, Air Force and Air Defence Command, plus roughly 397,000 paramilitary troops. The Central Security Forces sit under the Ministry of Interior; the Border Guard Forces under the Ministry of Defence.
- Two units operate under the Administration of Special Units — the Paratroopers and Sa'ka ("Thunderbolt").
- Sa'ka was established in the 1950s by Major General Galal Haredi, modelled on his officers' experience training with U.S. Army Rangers.
- Sa'ka selection is described as a pass-or-fail month, with an initial training period of only six weeks — which the article itself says leaves "many of the recruits… of poor standard."
- Unit 777 is profiled with a weapons list: Heckler & Koch MP5, MP7, G36 and USP; Colt M1911; AKM; SIG SG 550.
- The article's case studies are the unit's failures, not its successes — the 1978 Larnaca International Airport operation in Cyprus, where Egyptian commandos were dispatched to a hijacked airliner without Cypriot authorities being notified, were mistaken for terrorist reinforcements, and were fired on by Cypriot forces; and EgyptAir Flight 648.
What this is, and is not. It is a general-interest military profile with no connection to any aircraft, any date, or any person in this case. It names no operator of SU-BTT and places no Egyptian special-forces personnel anywhere near Utah. Its function in the threads was atmospheric — to make an Egyptian government jet at a Utah airfield feel operational — and it should be read that way.
It is worth noting what the article actually argues, because it undercuts the use it was put to: the piece describes a short training pipeline, recruits of uneven standard, and a signature operation that ended in a friendly-fire disaster. That is not a portrait of a service that quietly runs deniable work on American soil. Included here for completeness, not as evidence.
Every US visit by this aircraft, tested against the TPUSA event calendar
The following-plane claim is a claim about co-location — that these aircraft kept turning up where Charlie Kirk, Erika Kirk, or TPUSA were. On Charlie's side that claim is testable, because his speaking itinerary is a matter of public record.
This site keeps that record as a dated event list: 139 rows running 4 January 2022 to 29 October 2025, built from TPUSA postings, campus press, event listings and the Charlie Kirk Show archive, with every row carrying a certainty flag — EVENT_DATE where a real event date is sourced (118 rows), PODCAST_PROXY where only a podcast release date is known (8 rows), SCHEDULED_NOT_HELD (4) and AFTER_DEATH (9). The file is site/docs/Planes/following/tpusa_events.csv, and it is the spine of the Following section.
The test below is deliberately generous to the claim. A ground window counts as an overlap if any event in that calendar happened in the same US state, within three days either side of SU-BTT being parked there. That is roughly the standard Liz Wheeler says the original overlap spreadsheet applied, and it is far looser than "same city, same day."
SU-BTT's six US ground windows
| On the ground | Airport / city | Nearest TPUSA event in that state, any year | Gap |
|---|---|---|---|
| 20 Jul – 26 Jul 2025 | Omaha then Lincoln (LNK), NE | 22 Oct 2024 — Charlie, Omaha, NE — Campaign mobilization | 271 days |
| 26 Jul – 27 Jul 2025 | Wilmington (ILG), DE | 3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour, University of Delaware | 1,027 days |
| 17 Aug – 23 Aug 2025 | Omaha then Lincoln (LNK), NE | 22 Oct 2024 — Charlie, Omaha, NE — Campaign mobilization | 299 days |
| 23 Aug – 24 Aug 2025 | Wilmington (ILG), DE | 3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour, University of Delaware | 1,055 days |
| 4 Sep – 10 Sep 2025 | Provo (PVU), UT | 10 Sep 2025 — Charlie, Orem, UT — The American Comeback Tour, Utah Valley University | 0 days |
| 10 Sep – 11 Sep 2025 | Wilmington (ILG), DE | 3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour, University of Delaware | 1,073 days |
One of six windows produces a hit — and it is the last one. SU-BTT's Provo stay ends on the morning Charlie Kirk was killed roughly seven miles away. Every other US visit by this aircraft misses the nearest same-state TPUSA event by between nine months and three years.
That result cuts both ways, and both readings belong on the page:
- It is the strongest single data point in the whole following claim. The aircraft was at the right small airport in the right week, and it left before the shot. Nothing in the maintenance explanation predicts that week specifically.
- It is also the only one. Read as a pattern, this table does not support the shadowing thesis for SU-BTT. Nebraska in July and Nebraska in August are Duncan Aviation's plant, not a Kirk stop; Wilmington is the outbound customs leg on every rotation and has no TPUSA connection at all in the entire calendar. This is the concrete form of what Liz Wheeler argued: narrow the criteria and "the overlap dwindles to… one. On 9/10 in Utah."
What TPUSA was actually doing while SU-BTT sat in the United States
| SU-BTT on the ground | Charlie Kirk / TPUSA, on those same dates |
|---|---|
| 20 Jul – 27 Jul 2025 (Lincoln, Wilmington) | No sourced event in the calendar for those dates |
| 17 Aug – 24 Aug 2025 (Lincoln, Wilmington) | 20–22 Aug — Dallas, TX, Win the Storm; 21 Aug — North Myrtle Beach, SC, Alex McFarland Speaker Series |
| 4 Sep – 10 Sep 2025 (Provo) | 5–6 Sep — Seoul, Build Up Korea 2025; 7 Sep — Tokyo, Sanseito symposium (his last speech abroad); 10 Sep — Orem, UT, UVU |
| 10 Sep – 11 Sep 2025 (Wilmington) | 10 Sep — Orem, UT, UVU; 11 Sep — Woodland Park, CO (scheduled, not held) |
The September row is the one that matters, and it should be read precisely. For the first five of the six days SU-BTT sat at Provo, Charlie Kirk was on the other side of the Pacific — Korea on the 5th and 6th, Japan on the 7th. The aircraft was already parked in Utah before he was back in the country. Whether that reads as staging or as a jet waiting on a maintenance slot is exactly the question this table cannot close.
What this test does and does not settle
- It tests Charlie's side, not Erika's. In 139 rows, exactly one places Erika Kirk at a TPUSA event before 10 September 2025 — the June 2025 Young Women's Leadership Summit, logged as "Both." The 73-overlap tally was measured against Erika's claimed locations, and her flight logs are reported erased (see Erika's Flight Logs Erased). A thin column here does not refute that tally; it means the tally cannot be reproduced from anything this repository can source, which is a different and more honest statement.
- A gap is not a disproof. The calendar records public events. Private travel, donor meetings, studio days and family movements are not in it, and Charlie Kirk was in the air constantly.
- A hit is not a proof. One same-city, same-week co-location between a foreign VIP jet and a campus event is remarkable. It is not a manifest, a tasking order, or a passenger list, and no public record establishes who was aboard or why.
What this aircraft would cost to buy new today
- Type (FAA-confirmed): Dassault Falcon 7X, built 2014
- Registered owner: Egyptian registry (not in FAA database)
- Still built today? No — 7X built 2007-2021
- Priced against: Dassault Falcon 8X
- Cost to buy new today: ~$58-60 million
Falcon 7X out of production. The Falcon 8X is its direct successor at ~$58M base / ~$60M+ optioned. The 7X itself listed at roughly $40-45M when new, and about $54M at end of production.
List price is for a green airframe — interior completion, avionics options and any mission equipment are extra, and fleet buyers do not pay list. The full table for all 33 priced airframes in this investigation, with the method behind each figure, is on Aircraft Costs.
Flight data recovery
This is the best-covered Egyptian aircraft in the investigation. Two independent volunteer ADS-B networks hold daily tracks for it reaching back to 24 February 2023, and its FlightRadar24 page loads normally today. Nothing about this tail's data situation is unusual.
| Source | What it holds for SU-BTT |
|---|---|
adsb.lol globe_history | 29 days, 2023-02-24 to 2025-10-11 |
| globe.airplanes.live | 37 days, 2023-02-24 to 2026-05-24 |
| ADS-B Exchange monthly sample | 6 days, 2022-05-01 to 2026-03-01 |
| FlightRadar24 page | HTTP 200 in a real browser on 24 Aug 2026 — 56 history rows on the free seven-day tier, everything older paywalled |
| Internet Archive | 0 page snapshots held; 0 flight rows recovered off them |
The browser probe also returned the page's identity block: Dassault Falcon 7X EASy · FA7X · Mode S 0101D3 · listed as "Egypt Government" with operator "Egypt - Air Force". That is an independent confirmation of the hex code this site chose over the conflicting value carried by adsbdb.
Alleged overlaps. This tail carries 53 alleged overlap dates. 16 of them now have a recovered ADS-B track for that day, and 15 of those 16 are consistent with the alleged location. The single inconsistent result is 18 June 2025, alleged at Omaha / Lincoln NE: the recovered track runs Alexandria to El Alamein, both in Egypt. Every date is worked through on Overlap Recovery. The 37 dates with no recovered track are not evidence of anything — a missing track means no volunteer receiver heard the aircraft, not that it did not fly.
Removed from: nothing. No tracking site was found to have removed this aircraft's page. Our scripts recorded HTTP 403 from FlightRadar24, RadarBox and Planespotters, but all three return the identical 403 to unrelated control aircraft asked by the identical script. It is a robot block, not a deletion — see What A 403 Means.
Raw payloads are kept in site/docs/Planes/SU-BTT/data/recovered/, with the source named in every filename and a .meta.json sidecar per file recording source, URL, HTTP status, bytes and date.
More: Flight Data Recovery · Per-Aircraft Status
Interesting In This Area
- Three departure accounts circulate and the flight timeline shows they cannot all hold.
- SU-BND stayed parked while this jet left, per the same trackers.
- A tip places the crews at one named Orem hotel from September 4.
- The shadowing count is where the overlap arithmetic is actually disputed.
Interesting In Other Areas
- The SU-BTT movements timeline lays the 2025 legs against the wider calendar.
- Israel foreign leads examines the routing inference rather than asserting it.
- Foreign-nexus flight records are reportedly withheld from the public record.
- TPUSA event geography is what the overlap counts are measured against.
Other Pages In This Section
One of the five Egyptian-registered jets in the Provo cluster, with almost no standalone reporting behind it. John Cullen's maintenance-contract explanation is set out beside the shadowing reading.
Read this
The Army ISR jet that flew near campus did not lift off from a civilian executive terminal. It reportedly departed an active Army airfield at Fort Bliss, and that military origin is the detail investigators keep returning to.
Read this
Elsewhere In The Investigation
SU-BTT Plane Movements Timeline 2025
Every claimed 2025 movement of one Egyptian-registered Falcon, in date order. It sat at Provo the week of the assassination and left the morning of it, which cuts both ways — and the page says so.
Read this
The leads pointing outside the United States — phones, travel, SIGINT, search patterns — and the prior question of whether the government ran any of them down at all.
Read thisForeign-Nexus Flight Records Withheld (Claims)
Tail numbers, routes and times are all citizen trackers can see; manifests, cargo logs, visas and security waivers are where the foreign-nexus leads stop. A lead testable only with records nobody will release stays permanently open — which is itself the complaint.
Read this
The organization Charlie built, the donors who funded it, and the internal friction in the weeks before September 10. Read it alongside the motive threads; much of the reported pressure ran through here.
Read thisSources
- Candace Owens podcast coverage, including the November 17, 2025 episode "Operation Mocking-Plane: The Charlie Kirk Plot Thickens," and her "flight logs" presentation.
- Public flight-tracking logs and screenshots (FlightRadar24, ADS-B Exchange) circulated by independent researchers.
- X/OSINT investigators including @ProjectConstitu (Project Constitution), @BasedSamParker (Sam Parker), @nihilox (credited with the Israel-flight date compilation), @AnaEscobarShow, Ian Carroll, Ryan Matta, George Webb, and John Cullen (later credited with walking back a strong SU-BTT association).
- Israeli Channel 12 News, for the corroborated October 21, 2025 Cairo-to-Israel flight reportedly carrying Egyptian intelligence chief Hassan Rashad.
- Skeptic rebuttals to the overlap counts circulated on X — the "5 of 8 are wrong" audit and Liz Wheeler's "loose criteria / dwindles to one" critique.
- @ProjectConstitu, X post of August 16, 2026 (Sharm El-Sheikh tarmac claim) with attached 10:45 video including a Candace Owens segment on SU-BTU and an alleged passenger alias — full transcript reproduced above.
- @ProjectConstitu, X post of December 18, 2025 (transponder-off Israel flights) with attached 1:19 Candace Owens clip — full transcript reproduced above.
- Fox News live broadcast coverage of the October 13, 2025 Gaza summit arrivals at Sharm El-Sheikh, as excerpted in the video above.
- @Tut21125150 (Terry Tut), X post of August 16, 2026, "About those Egyptian planes" — 6:25 flight-data analysis covering the Minot AFB routing, the SU-BND May 23–September 14 stay, and the AXL10 ISR passes; full transcript reproduced above. Surfaced by @MysticMuse1o1, who also credits @GlamHamRadio with a separate UVU reserved-parking-spot search finding.
Laws (Charlie Kirk)
- SU-BTT's passenger manifest for the September 4–11 visit, the records authorizing its operation (including any Dugway clearance), and who it met at One Rodney Square in Wilmington are exactly the kinds of records the Charlie Kirk Investigation Laws are designed to force into the open.
Citizen Investigator Claims on X
(Aircraft OSINT and attributed claims — not findings that any pilot, passenger, or official ordered or carried out the assassination.)
- Candace Owens and amplifiers map Egyptian-registered VIP tails (SU-BTT, SU-BND, and related armada entries) overlapping Kirk/TPUSA travel and a ~Sept 4 Provo arrival; critics say the theory was debunked or over-rotated toward Erika-tracking tallies.
- Hotel/FOIA follow-ups (La Quinta Orem tip) and Israel-via-routing claims remain unverified passenger/ops stories — demand for manifests is common; no court has found these aircraft involved in the assassination.
- This page’s focus (SU-BTT Israel/Egyptian Jet) should be read with the Planes overview and Sept 10 flight timeline for cross-checks.
Best understanding of when this happened
Best understanding: flight-tracking discussions focus on SEPT 10 daytime relative to the UVU window (not a multi-month axis).
Date range (working model): SEPT 10 daytime flight-tracking window
The chart below is not a government finding. Bar height is relative likelihood from public claims. Domain is trimmed to non-trivial likelihood.
This website's author is @HolonCitizen on X and YouTube/@HolonCitizen. Follow me there.
X.com posts:
- SU-BTT on Sharm El-Sheikh tarmac near Air Force One
- Egyptian planes fly to Israel with transponders off
- Terry Tut flight analysis: Minot routing and ISR jet
- Terry Tut original: "About those Egyptian planes"
Interesting
- One claim places the Egyptian jets' occupants in an Orem hotel minutes from campus.
- A student says "free trauma counseling" offered to witnesses turned into threats.
- A GRAMA request reportedly returned two buried pre-event warnings, heavily redacted.
Related Areas
Related
Track This Aircraft
Research this aircraft's flight history yourself on both major flight-tracking sites. They differ in one important way:
- FlightRadar24 — SU-BTT — large commercial tracker that honors the FAA's LADD block list, so flights an owner or the government has asked to hide can be missing.
- ADS-B Exchange — SU-BTT — volunteer-fed, unfiltered tracker that does not honor LADD, so it often shows blocked aircraft and tracks the filtered sites leave out.
Note on Registration & Control
This aircraft carries an Egyptian registration — the SU- prefix on its tail number is Egypt's national civil registry, so the Egyptian registration itself is real and not in dispute. What is not settled is who ultimately controlled the jet. If an Egyptian front company was registered as the aircraft's operator, that registration — Egyptian on paper — may have been arranged on behalf of an intelligence service from another country. That open possibility is why this page labels the aircraft "Israel/Egyptian": the label flags the unresolved question of control. It is not a claim that the jet was Israeli-registered or Israeli-owned — the public record does not establish that, and nothing here asserts as fact that any government or person controlled it.
Images
Videos
Footage related to this page. Each card opens that clip's own page, with the video, the full write-up, and its source.
