Skip to main content
← Planes

SU-BGM Israel/Egyptian Jet

SU-BGM is an Egyptian-registered Gulfstream IV that independent open-source researchers count as the fifth aircraft in what they call the "Israel/Egyptian Plane Armada" — a group of Israel/Egyptian government Falcons and Gulfstreams (SU-BTT, SU-BND, SU-BTU, SU-BTV, and SU-BGM) that public flight logs show routing through Provo, Utah during 2025. Standalone reporting on this specific tail is thin: SU-BGM has drawn far less individual attention than the lead jets SU-BTT ("the yellow plane") and SU-BND ("the blue plane"). Its significance in the case is almost entirely as a member of the fleet pattern, not as a separately documented aircraft. The full analysis of the armada theory lives on the hub page — see Israel/Egyptian Plane Armada — and everything below should be read as one tail within that larger, still-unverified picture.

Aircraft identification​

  • Tail number: SU-BGM
  • Type: Gulfstream IV (long-range business jet), per the flight-log thread that catalogued the fleet
  • Registry / operator: Egyptian-registered — described in coverage as Israel/Egyptian Government / Israel/Egyptian Air Force use
  • Color nickname: None. Unlike SU-BTT (yellow) and SU-BND (blue), Candace Owens's color-coded shorthand assigned no color label to SU-BGM; it "appears in flight logs" without one.
  • Role in coverage: One of the "three more" Israel/Egyptian jets (with SU-BTU and SU-BTV) added to the original two-plane story to make the "five-plane armada" framing.

Flight history relevant to the case​

The only tail-specific legs published for SU-BGM come from a single raw-flight-log thread (attributed to @WeAre_TheElite and amplified by @ProjectConstitu / Project Constitution and Sam Parker). They describe spring 2025 activity, not the September window:

  • April 10, 2025: A Provo local flight of roughly 55 minutes (a short out-and-back from Provo Municipal Airport).
  • April 16, 2025: Goose Bay → Paris → Provo, reported as landing at Provo around 6:00 PM — the classic transatlantic routing (Cairo/Paris via Canada) the researchers attribute to the whole fleet.

The thread characterizes this as a "spring swarm during Kirk's Midwest push," placing SU-BGM in Provo months before the September 10 assassination rather than in the immediate days around it. No passenger manifest, crew list, or purpose for either leg has been publicly established. These two legs are the entirety of the tail-specific public record for SU-BGM; the rest of its relevance is inherited from the fleet pattern described on the hub page.

It is worth flagging one absence: unlike SU-BTT, SU-BTV, and SU-BTU — for which @nihilox and others published month-by-month lists of alleged Cairo-to-Israel flights — no Israel-flight date list was ever compiled for SU-BGM. Its only published role is being named as the fifth tail in the Provo "armada," and posters mainly cited it to urge Candace Owens to investigate the group further. No specific overlap between SU-BGM and a documented Erika Kirk, Charlie Kirk, or TPUSA event location has been demonstrated.

Theories about the aircraft's role​

Because so little is published about SU-BGM on its own, the theories attached to it are the fleet-level theories, framed here as open allegations rather than conclusions:

  • Recurrent foreign-fleet presence — that five distinct Israel/Egyptian government jets cycling through a single US municipal airport across 2025, overlapping with TPUSA event geography, is itself the anomaly worth investigating. SU-BGM is cited as evidence of the pattern's breadth, not for any single suspicious flight.
  • Surveillance / "intel-vacuum" reading — the same foreign-monitoring theory applied to the lead jets is extended to the whole armada by association.
  • Pre-event staging — the spring-2025 legs are read by the thread's author as part of a build-up ("circling Utah like predators pre-strike"). This is speculative narrative framing, not documented fact.

Counterpoints and innocent explanations​

Several considerations cut against reading SU-BGM as sinister, and they should be weighed prominently given how thin the tail-specific record is:

  • John Cullen's maintenance-contract dismissal. Independent investigator John Cullen, who has pushed hard on other aircraft in this case (notably N1098L and N55906), has discounted the Israel/Egyptian-jet armada theory, attributing the Provo visits to routine aircraft maintenance contracts rather than to an operation. Provo Municipal Airport hosts Duncan Aviation, a full-service maintenance, repair, and overhaul (MRO) facility, and a foreign VIP Gulfstream cycling through for service — including short local post-maintenance test flights like the April 10 "Provo local" — is an ordinary explanation that fits the data.
  • Spring timing, not the kill window. SU-BGM's documented legs are in April 2025, roughly five months before the assassination. They do not place this tail in Provo in the September 4–10 window that gives the lead jets their weight.
  • Data artifacts. Transatlantic VIP routing via Goose Bay and Paris, and short local hops, are exactly what maintenance ferrying and crew positioning look like on ADS-B; none of it is unique to a covert mission.
  • Skeptic audit of the overlap counts. At least one reviewer who pulled a year of FlightRadar history said most of the "overlaps" Owens cited for the lead jets were wrong. That skepticism applies with even more force to a secondary tail like SU-BGM, for which no specific Kirk-event overlap has been demonstrated at all.
  • Liz Wheeler's "loose criteria" rebuttal. Commentator Liz Wheeler argued that the overlap spreadsheets counted a "match" whenever an Israel/Egyptian jet was within roughly three days and the same broad region (50–100 miles) as Erika Kirk — not the same day at the same airport. Per Wheeler, when the parameters are narrowed to an Israel/Egyptian plane landing the same day in the same location, "the overlap dwindles to… one. On 9/10 in Utah." Under that stricter test SU-BGM produces no qualifying overlap at all.
  • Erika Kirk's denial. Erika Kirk has pushed back on the broader Israel/Egyptian-plane theory, and in remarks attributed to her she said she "had no idea there were Egyptian planes" and that "it could very well just be a coincidence," disputing being in the claimed locations. Her response addresses the fleet narrative generally rather than this specific tail.

Open questions​

  1. Who were the passengers and crew on SU-BGM's April 16, 2025 arrival into Provo, and what was the purpose of the April 10 local flight?
  2. Was SU-BGM serviced at Duncan Aviation's Provo MRO, and do maintenance records account for both legs?
  3. What is the operational relationship, if any, between SU-BGM and the other four Israel/Egyptian tails (SU-BTT, SU-BND, SU-BTU, SU-BTV)?
  4. Is there any SU-BGM presence in the September 2025 window, or is its record genuinely confined to the spring?
  5. Who authorized recurring Israel/Egyptian Air Force VIP access to a non-international US municipal airport across 2025?

Sources​

  • Raw flight-log thread cataloguing the five-tail fleet (attributed to @WeAre_TheElite; amplified by @ProjectConstitu / Project Constitution and @BasedSamParker / Sam Parker) — the origin of SU-BGM's April 10 and April 16 legs and the "Gulfstream IV" type.
  • Candace Owens podcast coverage and color-coded flight-log presentation (which assigned SU-BGM no color label).
  • Public ADS-B tracking data and historical flight-record screenshots (FlightRadar24, ADS-B Exchange).
  • John Cullen, independent investigator — cited for the maintenance-contract counterpoint to the armada theory.
  • Liz Wheeler — cited for the "loose overlap criteria" rebuttal (three-day / same-region matching) of the spreadsheet overlap counts.
  • Erika Kirk public remarks — cited for her denial that she was in the claimed locations and her "could very well just be a coincidence" response.

Laws (Charlie Kirk)​

  • SU-BGM's full flight records, passenger manifests, crew lists, and the authorization for Israel/Egyptian Air Force access to Provo are precisely the kinds of records the Charlie Kirk Investigation Laws are designed to force into the open — confirming or dispelling the armada theory rather than leaving it to compete 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-BGM — 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-BGM — 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.