Skip to main content
← Planes

Israel/Egyptian Plane Armada

Five Egyptian-registered VIP aircraft — SU-BTT, SU-BND, SU-BTU, SU-BTV, and SU-BGM — appear in 2025 flight logs operating in and out of Provo Municipal Airport (PVU), about seven miles from Utah Valley University. Independent researchers describe the pattern as a "five-plane armada" of Israel/Egyptian Air Force Falcons and Gulfstreams routing from Cairo via Paris into Utah, with overlapping presence in the days around Charlie Kirk's September 10, 2025 assassination. This page is the hub for the fleet pattern; each tail has its own page linked below.

The framing comes from Candace Owens (who color-coded the lead jets) and X/OSINT researchers including @ProjectConstitu (Project Constitution), Sam Parker, Ian Carroll, Ryan Matta, and John Cullen. It is contested. The "armada" reading rests on public ADS-B records circulated by amateur trackers; several of the claimed overlaps with the Kirk family have been challenged as inaccurate, and at least one investigator close to the story — John Cullen — has pointed to ordinary maintenance contracts as the explanation. Both the surveillance theory and the innocent explanations are laid out below.

The five tail numbers​

TailTypeOwens colorReported activity in source logs
SU-BTTDassault Falcon 7X"Yellow plane"In/near Provo Sept 4–10; departed Utah the morning of Sept 10 (for Wilmington, DE), left US for Cairo Sept 11. The lead "armada" jet.
SU-BNDGulfstream G550"Blue plane"Flew into Provo ~May 23 and reportedly stayed nearly four months; transponder ON but did not take off at the key moment; Sept 13 Provo → Goose Bay / Paris / Cairo.
SU-BTUDassault Falcon 7X(none)Feb 14 Provo → Wilmington; Mar 2 Detroit → Provo; Aug 8 Minot → Provo. May 27 into Provo carrying a passenger researchers name as "Walid Mahmoud," said to depart June 2. Hops tied by researchers to TPUSA Faith-tour stops.
SU-BTVDassault Falcon 7X(none)Mar 2 and Jul 2 Provo legs; Oct 2 Provo (after the assassination); Oct 29 Cairo local. Provo activity reportedly spikes before September.
SU-BGMGulfstream IV(none)Apr 10 Provo local (~55-min flight); Apr 16 Goose Bay → Paris → Provo (landed ~6 PM). Described as a "spring swarm" during Kirk's Midwest tour.

Per-tail routes above are taken from screenshots of raw flight logs posted by Project Constitution and others; they have not been independently verified and are reproduced here as the researchers' claims, not confirmed records.

Two additional foreign tails​

Beyond the five SU-registered jets, the investigation's aircraft list also flags two further foreign-registered tails — T7ELL and EJM36 — grouped with the Israel/Egyptian fleet for disclosure purposes. Public reporting on these two is minimal; see the dedicated page for investigative status. Ground lodging for jet occupants is tracked separately on Egyptian Crew Hotel (La Quinta Orem tip, Sept 4–13). Minute-by-minute Sept 10 transponder claims live on Sept 10 Flight Timeline.

Pattern of presence​

  • The aircraft are described in public reporting as VIP Falcons and Gulfstreams from Cairo via Paris, with multiple stops at Provo Municipal Airport throughout 2025.
  • Researchers report that SU-BTT and SU-BND have been observed near TPUSA events for years before September 10, 2025, with the claimed overlaps spanning roughly 2022 through 2025.
  • Candace Owens's team claims a cumulative 73 documented occurrences near Erika Kirk's travel and about 23 near Charlie Kirk across the United States — Omaha, Wichita, Provo, plus domestic and international legs. These tallies are disputed (see fact-checks below) and are reported here as the trackers' allegations, not as established fact.
  • The overlap count varies by source. Different X posts cite 73, 72, 70+, or 68 Erika-Kirk overlaps for the lead jets (SU-BTT and SU-BND). One widely shared post claimed: "72 times those exact planes followed Erika Kirk… That is statistically near impossible without intent." The inconsistency in the tallies is itself part of the dispute.
  • Candace Owens has clarified that no one is alleging the Kirks flew on these planes. Per Owens, the claim is only that the aircraft were in the same cities or regions as Erika Kirk, Charlie Kirk, or a TPUSA event — not that either Kirk was a passenger. She has said she shared the screenshots and spreadsheets on her show, called the pattern suspicious, and stated she sent the information to the FBI.
  • One independent analysis cited by researchers describes the US overlaps as concentrating in five states — Missouri, Delaware, Utah, Nebraska, and Kansas. This geographic clustering is offered by the trackers as supporting their theory; it has not been independently verified.
  • Researchers credit @nihilox with compiling much of the raw flight-log data, which was then amplified by Project Constitution and others.
  • A separate tracker tally circulated on X claims that the blue plane (SU-BND) and yellow plane (SU-BTT) together showed 68 overlaps with Erika Kirk's locations from 2022 through September 2025 — including overseas trips — of which 29 also coincided with Charlie Kirk. Like the Owens figures, these are unverified researcher counts, not confirmed records.
  • Some posters note the claimed overlaps begin around 2022, which they say aligns with the Kirk marriage timeline, and that several overlaps involve international/overseas legs alongside the Kirks rather than only domestic stops.
  • Researchers also report that the jets routinely fly in and out of Israel, a detail some threads fold into the broader "foreign-intel" framing. This is reported as a pattern observation, not as proof of any purpose.
  • Some threads further allege that the lead jet SU-BTT logged legs near Dugway Proving Ground — the U.S. Army chemical/biological test range in Utah — and cite recent stops at Wichita, Kansas as part of the same pattern. The Dugway claim is an unverified OSINT reading of public logs; the Wichita stops, by contrast, are explained by skeptics as routine Dassault servicing (see fact-checks below). Both are reported here as claims, not findings.

Assassination-day transponder activity​

Reported as a claim from the tracking threads, not a confirmed record:

  • On the day of the assassination, researchers say one of the jets' transponder came on around 9:05 AM and switched off around 10:34 AM. They claim it came back on roughly 17 minutes after the 12:40 PM shooting and stayed on until about 1:29 PM while the aircraft sat on the tarmac/runway rather than flying.
  • Posters have raised questions about whether the aircraft had encrypted communications or satellite capability, and whether it was "waiting for someone." These are open questions advanced by trackers, not established facts; transponder on/off behavior is also consistent with the mundane data and tracking artifacts described in the fact-checks below.
  • A related claim, attributed on X to @AnaEscobarShow, alleges that N102DZ — a jet associated in coverage with the Kirk party — "linked up" with SU-BND at Duncan Aviation after N102DZ's own ~3:30 PM Provo landing, with SU-BND described as "still there on and running." This is an unverified reading of two aircraft parked at the same maintenance ramp; co-location at a busy MRO field is not, by itself, evidence of any coordination. See the SU-BND page for detail.

Theories about the fleet's role​

Framed as open theories, each attributed to the people advancing it:

  • Foreign surveillance / intel-vacuum — Candace Owens and Project Constitution argue the jets were "Deep State vacuums" allegedly harvesting phones, faces, and plates at TPUSA rallies, not maintenance stops. Owens has cited a Provo hangar she says shut in 2021 and a 2024 French lease as evidence she believes the "maintenance" account is a cover.
  • A possible joint operation — tied to SU-BTT's Sept 10 routing to Wilmington, DE and unconfirmed "DoD Liaison" contractor claims at Duncan Aviation. See the SU-BTT page for that detail, which remains uncorroborated. As part of this framing, Candace Owens posted a claim that an Israel/Egyptian jet landed in Delaware and stayed the night of Sept 10, and that "a foreign dignitary was picked up after arriving from Provo the morning of Charlie's assassination on the Egyptian plane, and then transferred to 920 King for some joint operation" — a reference to 920 N. King St., Wilmington, which she said houses a joint DHS/FBI/DEA office. This is presented strictly as Owens's posted allegation; it is unverified, names no individual, and asserts no proven wrongdoing.
  • Counter-drone or drone role — John Cullen has speculated at points that one of the jets was associated with drones; this sits awkwardly beside his maintenance-contract explanation, and the disagreement shows the researchers themselves do not have a single account.
  • Israel / broader-plot links — because researchers say the fleet routinely transits Israel, some threads extend the theory to alleged Israeli or other foreign-intelligence involvement, or to links with broader plots to monitor Erika Kirk, the wider family, and TPUSA. Some posters have urged TPUSA to publicly address the flight-tracking story. No evidence ties any specific tail to such a plot; this is reported framing, not fact.
  • Fringe / unverified variants (flagged as such). A minority of X posts push the theory further, alleging Mossad ties or other foreign-intel control of the fleet, and a few even allege Erika Kirk's own involvement or claim that "files" have been released. These are unverified fringe conspiracy claims with no substantiation, recorded here only to document what is circulating online. Erika Kirk is a living person; the defamation caution applies in full, and no claim of wrongdoing by her or any named individual is established.

Innocent explanations and fact-checks​

Balance is essential here. Several facts cut against the "armada" reading, and some come from the same investigative circle:

  • John Cullen's maintenance-contract dismissal. Cullen has pointed to ordinary maintenance contracts as the explanation for the Israel/Egyptian jets at Provo — Falcon servicing through Duncan Aviation, whose Provo relationship for this kind of work is described as long-standing (reportedly dating to 1999). Under this reading, a foreign VIP Falcon parked at a full-service MRO field is routine, not operational.
  • Duncan Aviation is a legitimate jet hub. Duncan runs a full-service maintenance, repair, and overhaul facility at Provo Municipal Airport — airframe, engine, avionics, paint, and interior work. A foreign VIP Falcon or Gulfstream stopping there for service is not inherently suspicious.
  • A skeptic's audit of the overlaps. At least one reviewer who pulled a year of FlightRadar history reported that "5 of the 8" overlaps Owens cited were wrong — claiming the plane had not even left Egypt on some of the cited dates — and disputed the "73 overlaps" framing entirely.
  • Erika Kirk's own account. According to that audit, Erika Kirk reportedly said she stayed home in Arizona on September 10 rather than being in the Nebraska/Delaware locations some overlap claims placed her near, and she has reportedly disputed some of the overlap claims in later interviews. Erika Kirk is a living person; all claims about tracking her movements are allegations by third parties, not established fact, and her stated denials are included here in fairness.
  • SU-BND stayed for months. The "blue plane" reportedly sat in Provo for nearly four months, which fits a long maintenance or storage stay more than a surgical operation.
  • Tracking artifacts. 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 covert flights.
  • Liz Wheeler's "dwindles to one" rebuttal. Commentator Liz Wheeler argued the overlap spreadsheets use loose criteria — counting a match when an Israel/Egyptian jet was within roughly 50–100 miles ("the same region") and within plus-or-minus three days, rather than at the same airport on the same day. Per Wheeler, "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." On her reading, the headline counts collapse once the criteria are tightened.
  • Misattribution and time-zone errors. Independent reviewers claim a large share of the cited overlaps — by some accounts roughly 60 to 66 percent — are simply wrong: UTC-versus-local-time mistakes (for example in the Provo departure timing), aircraft placed on the wrong continent, and routine maintenance legs misread as surveillance.
  • Wichita explained as a maintenance stop. SU-BTT (a Dassault Falcon) is reported to have made "no fewer than 8 stops" in Wichita, Kansas — but Wichita is the "Air Capital of the World," home to aviation maintenance hubs including Yingling Aviation, an FAA Part 145 facility that services Dassault jets and has had a Dassault relationship since 2015. Critics say this explains repeated Wichita stops as ordinary servicing rather than tracking of any person.
  • Grok / ADS-B caveat. Asked about the theory, the AI assistant Grok reportedly noted that public ADS-B data shows the aircraft were active but does not prove any surveillance or assassination link, and that the official investigation centers on a lone shooter. The flight data is publicly viewable on FlightRadar24 and ADS-B Exchange, subject to coverage limits for certain aircraft.

Why this pattern still draws scrutiny​

A single foreign-government aircraft at a US municipal airport is unremarkable, and the maintenance explanation may well account for most of it. What keeps researchers asking questions is the combination they describe — multiple aircraft from one foreign air force, recurrent visits over months, claimed overlap with TPUSA event geography, and presence in Provo in the days preceding a high-profile assassination. That combination, if the underlying logs hold up, is the basis for calls to investigate the operators, passengers, and tasking of all five tails. Whether it survives a documentary check is exactly what the open records below would settle.

Open questions​

  1. Who in the US authorized recurring access for Israel/Egyptian VIP/Air Force jets to a non-international US municipal airport?
  2. Who were the passengers on each aircraft during the 2025 visits, and is there any manifest?
  3. Do Duncan Aviation's maintenance records account for the full set of Provo stops, as John Cullen suggests?
  4. Which of the claimed Erika/Charlie Kirk overlaps are accurate once cross-checked against full flight history — the trackers' tallies or the skeptic's "5 of 8 wrong" audit?
  5. What is the operational relationship, if any, between SU-BTT, SU-BND, SU-BTU, SU-BTV, and SU-BGM?

Sources​

  • Candace Owens podcast coverage and screenshots of raw flight logs circulated by independent researchers.
  • X/OSINT investigators: @ProjectConstitu (Project Constitution), Sam Parker, Ian Carroll, Ryan Matta, George Webb, and John Cullen (who has offered the maintenance-contract explanation).
  • Public ADS-B / FlightRadar24 tracking data and historical flight-record screenshots, plus the skeptic rebuttal disputing the overlap counts ("5 of 8 are wrong").
  • Liz Wheeler's "dwindles to one" rebuttal on the loose +/-3-day, same-region overlap criteria; @nihilox (data compilation); and a Grok response noting ADS-B activity does not prove a surveillance or assassination link.
  • Background on Duncan Aviation's Provo MRO facility.

Laws (Charlie Kirk)​

  • Passenger manifests for the five Israel/Egyptian jets, the maintenance records that would confirm or refute the routine-service explanation, and who authorized Israel/Egyptian Air Force access to Provo are exactly the kinds of records the Charlie Kirk Investigation Laws are designed to force into the open — settling the dispute one way or the other.

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 (Israel/Egyptian Plane Armada) should be read with the Planes overview and Sept 10 flight timeline for cross-checks.

Track These Aircraft​

Each jet in the armada can be researched on both major flight-tracking sites. FlightRadar24 honors the FAA's LADD block list (flights an owner or the government has asked to hide can be missing); ADS-B Exchange is volunteer-fed and unfiltered (it often shows blocked aircraft and tracks the filtered sites leave out).

Tip: These are foreign (Egyptian) military registrations, which are frequently sparse or absent on FlightRadar24. ADS-B Exchange — fed by volunteer receivers near the actual flight paths — is usually the better source for them.

Note on Registration & Control​

These five aircraft carry Egyptian registrations — the SU- prefix on each tail number is Egypt's national civil registry, so the Egyptian registrations themselves are real and not in dispute. What is not settled is who ultimately controlled the jets. If Egyptian front companies were registered as their operators, those registrations — Egyptian on paper — may have been arranged on behalf of an intelligence service from another country. That open possibility is why these pages label the fleet "Israel/Egyptian": the label flags the unresolved question of control. It is not a claim that the aircraft were Israeli-registered or Israeli-owned — the public record does not establish that, and nothing here asserts as fact that any government or person controlled them.