Skip to main content
← Planes

SU-BTV Israel/Egyptian Jet

SU-BTV is an Egyptian-registered VIP jet — described in flight logs as a Dassault Falcon 7X — that appears as one of the five tail numbers in what X researchers call the "Israel/Egyptian Plane Armada": a cluster of Israel/Egyptian government Falcons and Gulfstreams (SU-BTT, SU-BND, SU-BTU, SU-BTV, SU-BGM) that trackers say routed through Provo, Utah during 2025.

Be honest about the sourcing: standalone reporting on SU-BTV specifically is thin. It is rarely discussed on its own; its significance is almost entirely as a member of the fleet pattern. The bulk of the analysis — the timeline, the TPUSA-overlap claims, the maintenance counterpoints — lives on the hub page, Israel/Egyptian Plane Armada. This page collects only what public sources say about SU-BTV by name and frames every claim as an open, unverified allegation.

Aircraft identification​

  • Tail number: SU-BTV
  • Type: Dassault Falcon 7X (per the flight-log screenshots circulated on X; "Egyptian-registered" in other notes)
  • Registry / operator: Egyptian-registered — described as Israel/Egyptian Government / Israel/Egyptian Air Force use
  • Nickname in coverage: None. Candace Owens color-coded SU-BTT ("yellow plane") and SU-BND ("blue plane"); SU-BTV carries no color label and is listed only in flight-overlap discussions.
  • Reported destination airport in Utah: Provo Municipal Airport (PVU), roughly 7 miles from Utah Valley University.

Flight history relevant to the case​

SU-BTV surfaced publicly when raw flight-log screenshots — attributed to the account @WeAre_TheElite and amplified by @ProjectConstitu (Project Constitution) — were used to expand the "two Israel/Egyptian planes" story into a "five-plane armada." The dated legs below are those researchers' published readings of the logs, not independently verified records:

  • March 2, 2025: Provo (PVU) activity logged.
  • July 2, 2025: Provo local flight.
  • October 2, 2025: Provo activity — which one thread speculated, with a question mark, could be "post-assassination cleanup." This is rhetorical speculation, not evidence.
  • October 29, 2025: Cairo local flight.

Researchers characterize the pattern as "Provo spikes pre-September," grouping SU-BTV with the other four tails as recurring 2025 visitors to a non-international US municipal airport. No passenger manifest, tasking, or operator statement for any SU-BTV leg has been made public.

Alleged Israel trips​

Separate from the Provo legs, a date list circulated on X claims SU-BTV made repeated 2025 runs into Israel. The list was compiled by @nihilox and shared by @ProjectConstitu (Project Constitution). Researchers allege these flights logged as Cairo-to-Cairo (CAI–CAI) or with the transponder off at points, and they claim the planes actually landed in Israel — an unverified reading of the data, not a confirmed itinerary. The dates as published:

  • January: Jan 05, Jan 08 (two flights), Jan 12 (two flights), Jan 14, Jan 21, Jan 28, Jan 29
  • February: Feb 12, Feb 18, Feb 19
  • March: Mar 02, Mar 09
  • April: Apr 08
  • May: May 10
  • June: Jun 17 (two flights)
  • July: Jul 06, Jul 15, Jul 19
  • August: Aug 10
  • September: Sep 02, Sep 23, Sep 24
  • October: Oct 01, Oct 29
  • November: Nov 04 (two flights), Nov 25
  • December: Dec 04

Treat this list as an OSINT allegation. The same maintenance and data-error counterpoints below apply: a falsified-log or "stealth" reading is one interpretation, but routine VIP movements, transponder artifacts, and miscounted dates are the mundane alternatives. No manifest or operator statement confirms any SU-BTV Israel landing.

Theories about the aircraft's role​

All of the following are open theories advanced by independent commentators, not established facts:

  • Fleet-pattern surveillance — that the five Israel/Egyptian tails collectively shadowed TPUSA events and the Kirk family's movements (the "armada" framing). SU-BTV is cited as a data point in that pattern rather than as an individually documented surveillance flight.
  • Foreign orchestration — the @ProjectConstitu thread floated "Mossad proxies via Egypt" and alleged "no-scan DoD badges" dropping "experts" for drone/laser operations. These are unverified assertions made about the fleet as a whole, with no specific evidence tied to SU-BTV.
  • Routine VIP operations — the innocent reading (see the counterpoint below), under which SU-BTV's Provo stops are ordinary maintenance or VIP movements.

John Cullen's maintenance-contract counterpoint​

Independent researcher John Cullen has pushed back on the foreign-operation reading of the Israel/Egyptian jets. His counterpoint — applied to the fleet, and therefore to SU-BTV as one of its members — is that the recurring Provo presence is best explained by a maintenance / service-contract relationship with the jet-service hub at Provo Municipal Airport, not by a covert tasking. Provo hosts Duncan Aviation, a full-service maintenance, repair, and overhaul (MRO) facility (airframe, engine, avionics, paint, interior). A foreign VIP Falcon cycling through Provo for service is, on this view, unremarkable.

Other mundane explanations also weigh against the sinister reading: a skeptic's audit of Owens's overlap counts reportedly found several of the cited dates wrong, transponder/track artifacts can mimic "stealth" behavior, and the companion "blue plane" SU-BND reportedly sat in Provo for months — more consistent with a long maintenance or storage stay than a surgical operation. These counterpoints are covered in full on the Israel/Egyptian Plane Armada hub.

Open questions​

  1. Who were the passengers, and is there any manifest for SU-BTV's 2025 Provo visits?
  2. Is SU-BTV's reported type (Falcon 7X) confirmed by registry records, or only inferred from screenshots?
  3. What is the operational relationship, if any, between SU-BTV and the other four armada tails (SU-BTT, SU-BND, SU-BTU, SU-BGM)?
  4. Does SU-BTV's Provo presence reconcile with a Duncan Aviation service record, as John Cullen's maintenance-contract reading suggests?
  5. Who authorized recurring Israel/Egyptian-government access to a non-international US municipal airport?

Sources​

  • Flight-log screenshots attributed to @WeAre_TheElite, amplified by @ProjectConstitu (Project Constitution) on X (the "five-plane armada" post).
  • SU-BTV Israel-trip date list compiled by @nihilox, shared by @ProjectConstitu on X.
  • Candace Owens podcast coverage of the broader Israel/Egyptian-jet pattern (SU-BTT / SU-BND focus).
  • Public ADS-B / flight-tracking data (FlightRadar24, ADS-B Exchange) circulated by independent researchers.
  • John Cullen — maintenance-contract counterpoint to the foreign-operation reading.
  • Additional OSINT coverage by Sam Parker, Ian Carroll, Ryan Matta, and Zeb Boykin.

Laws (Charlie Kirk)​

  • SU-BTV's full flight records, passenger manifests, and the records authorizing Israel/Egyptian-government access to Provo — alongside the rest of the fleet — are exactly the kinds of documents the Charlie Kirk Investigation Laws are designed to force into the open, so the maintenance vs. surveillance question can be settled with evidence rather than screenshots.

Track This Aircraft​

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

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