Skip to main content
← Planes

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.

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.

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​

  1. 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?
  2. Who were the passengers, and is there any manifest for the Sept 4 arrival and Sept 10 departure?
  3. Which of the three Sept 10 departure timelines (7:08 AM, the 9:05 AM "go dark," or the Dugway origin) is correct?
  4. What was the purpose of the Wilmington destination on the day of the assassination?
  5. Do the "counter-UAS" and "DoD Liaison" witness claims survive any documentary check, or are they unsupported?

Sources​

  • 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.

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.

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.