Skip to main content
← Planes

SU-BTU Israel/Egyptian Jet

SU-BTU is an Egyptian-registered jet — described by independent trackers as a Dassault Falcon 7X — named as one of the five aircraft in the "Israel/Egyptian Plane Armada" that public researchers say cycled through Provo, Utah during 2025. Unlike the two lead jets in that cluster — SU-BTT ("the yellow plane") and SU-BND ("the blue plane") — there is very little standalone reporting on SU-BTU. Its significance in the public commentary comes almost entirely from its membership in the fleet pattern, not from any single documented event tied to this tail alone.

Read the Israel/Egyptian Plane Armada hub page first — the bulk of the analysis, the fleet timeline, the source list, and the counterarguments live there. This page collects only what is specific to SU-BTU, and is honest that the standalone record is thin.

Aircraft identification​

  • Tail number: SU-BTU
  • Type: Egyptian-registered jet; described by trackers as a Dassault Falcon 7X (long-range business jet)
  • Registry / operator: Israel/Egyptian Government / Israel/Egyptian Air Force use (per the framing in public coverage)
  • Color label: None. Candace Owens's color-coded shorthand ("yellow plane," "blue plane") was applied to SU-BTT and SU-BND; the master flight-log notes state no color label was attributed to SU-BTU.
  • Role in coverage: One of three additional Israel/Egyptian tails (with SU-BTV and SU-BGM) added to the "armada" narrative after the original SU-BTT / SU-BND timeline.

Flight history relevant to the case​

Every item below comes from open-source researchers working from public flight-record screenshots. None has been independently verified; treat the dates and routes as reported claims.

  • May 27, 2025: Investigation notes record SU-BTU flying into Provo, with a passenger identified in those notes as Walid Mahmoud aboard (see Open questions — this is an unverified online claim about a living person).
  • June 2, 2025: The notes record the Egyptian passenger "Walid" departing Provo.
  • Feb 14, 2025: Provo → Wilmington, DE (per the "five-plane armada" log thread).
  • Mar 2, 2025: Detroit → Provo.
  • Aug 8, 2025: Minot, ND → Provo.

The log thread that introduced SU-BTU summarized it as making "multiple NE/UT hops tied to TPUSA Faith tours." That phrasing is the researcher's characterization, not a confirmed itinerary.

Alleged Israel trips​

Separately from the U.S. overlaps, a flight-log thread compiled by @nihilox and shared by @ProjectConstitu claims SU-BTU made a long run of trips to Israel across one year. The researchers allege the public logs show these as Cairo-to-Cairo (CAI → CAI) or origin-N/A legs, and argue the jets actually landed in Israel with the transponder switched off — so the listed dates are, by their own framing, an inference from a claimed blackout pattern, not confirmed Israel landings. None of this has been independently verified, and the same Cairo-to-Cairo logs are equally consistent with the routine in-country flying of a government VIP jet.

Dates the thread attributes to SU-BTU (one calendar year):

  • January: Jan 05, Jan 08, Jan 12
  • February: Feb 05, Feb 11, Feb 16, Feb 23
  • March: Mar 02, Mar 25
  • April: Apr 15
  • May: May 10, May 17
  • June: Jun 14 (two flights), Jun 21, Jun 24
  • July: Jul 02, Jul 05, Jul 06, Jul 08, Jul 13
  • September: Sep 20
  • December: Dec 14

The same researchers posted parallel Israel-trip lists for SU-BTT and SU-BTV, and present the three lists together as a "consistent and undeniable" pattern. That characterization is the thread's, not an established finding. The only Israel leg with outside corroboration in this material is an SU-BTT flight (not SU-BTU) reported by Israeli Channel 12 News; no comparable corroboration has been published for any SU-BTU date above.

Theories about the aircraft's role​

These are framed as open theories raised by independent commentators, not conclusions:

  • Fleet-pattern surveillance — that SU-BTU, as part of a recurring multi-jet Israel/Egyptian presence, fits the broader "intel-vacuum" theory that a foreign government may have been monitoring TPUSA events and the Kirk family. This theory lives at the fleet level on the Armada hub; SU-BTU's individual contribution to it is limited.
  • A passenger of interest — because the notes place a named Egyptian passenger aboard SU-BTU's May 27 Provo arrival, some threads treat the aircraft as part of the "who was being shuttled through Provo" question. The same name has been floated by other threads in connection with the SU-BTT Wilmington leg, so the sourcing is inconsistent (see below).

Counterpoint — the maintenance-contract explanation​

In fairness, the simplest reading of the fleet's recurring Provo visits is a service relationship, not an operation. Provo Municipal Airport hosts Duncan Aviation, a full-service maintenance, repair, and overhaul (MRO) facility, and skeptics — including investigator John Cullen — have argued the Israel/Egyptian jets' repeated appearances are most consistent with an ongoing maintenance / service contract rather than surveillance tasking. A foreign VIP Falcon routing through a known MRO hub is unremarkable on its own. This counterpoint applies to the whole armada and is covered more fully on the hub page; transponder gaps and trackers "snapping" an origin to the nearest public field can also be mundane data artifacts rather than evidence of anything covert.

Open questions​

  1. Is SU-BTU's individual flight record (May 27 arrival, June 2 departure, and the 2025 NE/UT hops) borne out by independent ADS-B history, or are some legs misattributed — as a skeptic's audit alleged for several of the SU-BTT overlaps?
  2. Who were the passengers on SU-BTU's 2025 Provo visits, and is there any manifest for the May 27 arrival?
  3. The investigation notes name Walid Mahmoud as a passenger. This is an unverified online claim about a living person who has not been charged with any crime, and the same name appears elsewhere tied to a different jet (SU-BTT). Which, if either, attribution is accurate?
  4. What is the operational or contractual relationship between SU-BTU and the other four armada tails (SU-BTT, SU-BND, SU-BTV, SU-BGM)?

Sources​

  • Raw flight-log screenshots circulated by independent researchers (the "five-plane armada" thread crediting @WeAre_TheElite), amplified on X.
  • Candace Owens podcast coverage of the Israel/Egyptian-jet timeline (focused mainly on SU-BTT and SU-BND).
  • Public ADS-B / FlightRadar24 tracking data referenced by those researchers.
  • Skeptic rebuttals to the overlap counts, and the maintenance-contract counterpoint associated with John Cullen.

The standalone, SU-BTU-specific sourcing is thin. Most of the evidentiary weight is at the fleet level on the Israel/Egyptian Plane Armada page.

Laws (Charlie Kirk)​

  • SU-BTU's passenger manifests, the records authorizing its Provo access, and any maintenance-contract paperwork that would confirm or refute the innocent explanation are exactly the kinds of records the Charlie Kirk Investigation Laws are designed to force into the open — alongside the other four armada tails.

Track This Aircraft​

Research this aircraft's flight history yourself on both major flight-tracking sites. They differ in one important way:

  • FlightRadar24 — SU-BTU — 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-BTU — 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.