Skip to main content
← Planes

SU-BND Blue Plane

An Egyptian-registered Gulfstream (tail number SU-BND) — referred to on Candace Owens's podcast as "the blue plane" — is reported to have flown into Provo, Utah in spring 2025 and stayed for nearly four months, still parked there in the window around Charlie Kirk's September 10, 2025 assassination. According to the notes circulating in public coverage, its transponder was switched ON but it did not take off at the key moment. It is the companion aircraft to SU-BTT ("the yellow plane") in what X researchers call the "Israel/Egyptian Plane Armada". SU-BND is the strongest-documented of the secondary Israel/Egyptian jets — but it is also the tail for which the innocent maintenance explanation is strongest, and that counterpoint is laid out prominently below. Every claim here comes from independent open-source researchers working from public ADS-B data; little of it has been independently verified.

Aircraft identification​

  • Tail number: SU-BND
  • Type: Gulfstream (described in coverage as a Gulfstream G550; some notes also reference Gulfstream-class / Gulfstream IV airframes within the broader Israel/Egyptian fleet)
  • Registry / operator: Egyptian-registered — described as Israel/Egyptian Government / Israel/Egyptian Air Force use
  • Nickname in coverage: "The blue plane" (Candace Owens's color-coded shorthand; SU-BTT was "the yellow plane")
  • Base in Utah window: Provo Municipal Airport (PVU), ~7 miles from Utah Valley University, where Duncan Aviation runs a full-service maintenance hangar
  • Part of a larger fleet: Trackers say SU-BND is one of at least five Israel/Egyptian Air Force jets (alongside SU-BTT, SU-BTU, SU-BTV, and SU-BGM) that they allege cycled in and out of Provo around the event — the cluster X researchers call the "Israel/Egyptian Plane Armada". The fleet count is the trackers' claim, not an official tally.

Flight history relevant to the case​

The dated bullets below reflect the published timelines of independent trackers, amplified by Candace Owens. They have not been independently confirmed and are reported here as claims:

  • May 23–25, 2025: SU-BND is reported to have flown into Provo and then stayed there for nearly four months — trackers describe local "Provo locals" test flights around May 25.
  • Through summer 2025: The aircraft reportedly remained parked at Provo across the entire window leading up to September 10.
  • September 10, 2025 (day of the assassination): Per the notes, SU-BND's transponder was turned ON but the aircraft did not take off at the key moment, in contrast to SU-BTT, which departed. One account describes this "second Egyptian plane" as having left roughly three hours after the assassination, while other logs place its outbound legs days later.
  • September 11, 2025: A separate compilation states that SU-BND sat on the ground at Provo with power and transponder on the entire day of September 10 and then departed on September 11 — the day after the assassination.
  • The N102DZ "link-up" claim: Some trackers allege that N102DZ — a jet associated in coverage with the Kirk party — reportedly "linked up" with SU-BND at Duncan Aviation after N102DZ's own landing at Provo at roughly 3:30 PM on the day in question. The claim is attributed on X to @AnaEscobarShow, who is quoted describing SU-BND as "still there on and running" when N102DZ arrived. This is an unverified OSINT reading of ground positions and aircraft states at a shared maintenance ramp; two aircraft parked at the same MRO facility is exactly what a busy service hub looks like, and no record ties the two tails together operationally.
  • September 13, 2025: Reported departure Provo → Goose Bay → Paris → Cairo (described by trackers as the "lag plane" that stayed for months).

These accounts of when SU-BND left — "three hours after," a September 11 departure, and a September 13 departure — are not consistent with one another in the source material, and all are reported here as competing claims rather than settled fact.

The "transponder ON only three times" screenshot claim​

The most heavily shared SU-BND item is a single screenshot circulated on X with the caption that "this Egyptian plane doesn't move for days and the transponder ONLY goes on THESE 3 TIMES." The screenshot poster lines those three transponder pings up against three arrivals on September 10:

  • 10:05 AM — when Erika Kirk allegedly lands at Provo.
  • 1:40 PM — when a man the screenshot names only as "Andrew" allegedly lands at Scottsdale, Arizona, in what the poster captions as a pickup of Erika Kirk's cell phone.
  • 2:29 PM — when Tyler Robinson allegedly lands at Provo.

This is an unverified screenshot claim, not an established sequence of events, and it should be read with strong caution. The "Andrew picks up Erika Kirk's phone in Scottsdale" element in particular is an accusatory assertion about living private individuals that no source has corroborated; it is reported here only as the content of a referenced screenshot, and no wrongdoing by any named person is established or implied. Several skeptical counterpoints apply directly:

  • The "transponder only on three times" framing assumes the pings are meaningful signals. A parked aircraft on ground power, or one being repositioned on the ramp by maintenance crews, can produce intermittent transponder activity for entirely mundane reasons — the same innocent reading that applies to the broader "transponder ON, no takeoff" detail.
  • The timestamps mix arrivals at two different airports (Provo and Scottsdale) and depend on the screenshot's own time labels, which other reviewers have flagged across the Israel/Egyptian-plane material as prone to UTC-versus-local-time errors.
  • No public record ties SU-BND's ground activity to any phone, person, or vehicle; the linkage exists only in the screenshot's captions.

Liz Wheeler's "narrowed parameters" rebuttal​

Commentator Liz Wheeler has publicly challenged the overlap math behind SU-BND and SU-BTT, arguing the tallies rely on loose criteria — counting a "match" when an Israel/Egyptian jet was within a broad region (tens of miles) and within a few days of one of Erika Kirk's locations, rather than 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." Her rebuttal is reported here for balance; it disputes the methodology behind the 68- and 73-overlap counts above rather than the raw ADS-B data itself.

Long-term tracking pattern (2022–2025)​

Beyond the September window, Owens and independent trackers group SU-BND with SU-BTT as "two Egyptian Air Force intelligence jets" that they allege shadowed the Kirk family for years:

  • Their tallies claim the two jets logged roughly 73 documented overlaps with Erika Kirk across the United States — Omaha, Wichita, Provo, plus domestic and international legs.
  • A separate dual-plane count circulated on X claims 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 differs from the 73-overlap tally above; both are independent researchers' claims, not reconciled numbers.
  • Trackers also note that the Israel/Egyptian jets routinely fly in and out of Israel, which they fold into theories of the fleet monitoring Erika Kirk, the wider family, or TPUSA events. The Israel-routing claim rests on the same public ADS-B records and is reported here as an allegation.
  • Trackers point to public ADS-B records they say show the aircraft appearing near the family's locations with unusual frequency over 2022 through 2025.

As with SU-BTT, these claims rest entirely on public ADS-B screenshots circulated by independent researchers and have not been independently confirmed.

Theories about the aircraft's role​

Researchers covering SU-BND have floated several interpretations, framed here as open theories rather than conclusions:

  • Foreign surveillance / "intel vacuum" — that a foreign-government aircraft may have been monitoring Charlie Kirk, Erika Kirk, or TPUSA events. Owens's framing describes the Israel/Egyptian jets as "Deep State vacuums" harvesting phones, faces, and plates at rallies.
  • A staged or support role on Sept 10 — built on the detail that the transponder was powered up but the aircraft never left, which some readers interpret as a standby or signaling role and others as simple ground-power during maintenance.
  • Drone association — John Cullen has speculated that the Israel/Egyptian aircraft were tied to drones; the same counter-UAS testing claims attached to SU-BTT have been extended by some posters to the fleet generally.

John Cullen's maintenance-contract dismissal​

In the interest of fairness, the most prominent skeptic of tying SU-BND to the assassination is open-source investigator John Cullen (@I_Am_JohnCullen) — himself a major figure in the broader plane investigation, who put forward the N1098L and N55906 surveillance-aircraft theories. Cullen has dismissed a strong association between the Israel/Egyptian jets and the assassination, citing long-standing Falcon and VIP-jet maintenance contracts at Provo dating back to roughly 1999. In his reading, a foreign government fleet routing through a U.S. MRO (maintenance, repair, and overhaul) facility is a decades-old, routine arrangement — not evidence of an operation.

This is significant precisely because Cullen is otherwise willing to chase aggressive surveillance theories. When even he flags the Israel/Egyptian-jet angle as likely innocent, that carries weight. SU-BND's own flight profile fits the maintenance reading better than SU-BTT's does: a jet that flies in and then sits in one place for nearly four months looks far more like a long maintenance or storage stay than a surgical operation timed to a single day.

The page presents both readings side by side. The surveillance theory and the routine-maintenance explanation are both live, and as of now neither has been confirmed or ruled out by any official source.

Counterpoints and innocent explanations​

Several facts cut against the sinister reading of SU-BND specifically:

  • Provo is a legitimate jet-service hub. Duncan Aviation operates a full-service MRO facility at Provo Municipal Airport — airframe, engine, avionics, paint, and interior work. A foreign VIP Gulfstream parking there for an extended service is not inherently suspicious. (Duncan's local connections have been noted in coverage, including reporting that a former Duncan Aviation VP, Tom Burt, is tied by family relationship to figures discussed in the case — a detail offered without any established wrongdoing.)
  • The four-month stay fits maintenance, not an op. The companion "yellow plane" SU-BTT moved in and out quickly; SU-BND did the opposite, which is the hallmark of a heavy-maintenance or storage booking.
  • A skeptic's audit disputed the overlap counts. At least one reviewer who pulled a year of FlightRadar history said "5 of the 8" overlaps Owens cited were wrong — claiming the plane "hadn't even left Egypt" on some of the listed dates — and noted that Erika Kirk herself said she stayed home in Arizona on Sept 10 rather than traveling. That reviewer found that the SU-BND-specific entries on May 23 and one other date were accurate, but could not source one of the July dates at all.
  • Erika Kirk has disputed the overlap claims. In later interviews and public statements, Erika Kirk reportedly pushed back on the narrative that the Israel/Egyptian jets shadowed her movements, including saying she stayed home in Arizona on Sept 10. Her denial is reported here for fairness; the overlap tallies remain the trackers' claims and have not been confirmed.
  • Transponder ON, no takeoff is exactly what a parked aircraft running ground power or being moved on the ramp would show — a mundane reading at least as plausible as a standby-signal interpretation.

Open questions​

  1. Why did SU-BND remain parked at Provo for nearly four months in 2025, and what work order or contract covered the stay?
  2. Who were the crew and any passengers associated with the aircraft during the Provo period?
  3. Which departure account is correct — a departure roughly three hours after the assassination, a September 11 departure, or the September 13 Provo → Goose Bay → Paris → Cairo routing?
  4. Do the "73 overlaps" with Erika Kirk survive a documentary audit, given the skeptic's claim that several cited dates are wrong?
  5. Does John Cullen's maintenance-contract explanation fully account for SU-BND, or are there flight legs it does not explain?

Sources​

  • Candace Owens podcast coverage, including the November 17, 2025 episode "Operation Mocking-Plane: The Charlie Kirk Plot Thickens," and her "nuclear flight logs" presentation describing the two Israel/Egyptian jets.
  • Public flight-tracking logs and screenshots (FlightRadar24, ADS-B Exchange) circulated by independent researchers.
  • X/OSINT investigators including @ProjectConstitu (Project Constitution), @BasedSamParker (Sam Parker), @WeAre_TheElite, Ian Carroll, Ryan Matta, and George Webb.
  • John Cullen (@I_Am_JohnCullen), who dismissed a strong assassination link by citing long-standing Falcon/VIP maintenance contracts at Provo dating to ~1999.
  • Skeptic rebuttal to the overlap counts circulated on X (the "5 of 8 are wrong" audit).
  • Liz Wheeler, who argued the overlap tallies use loose region/date criteria and that strict same-day, same-location parameters reduce the overlap to one (9/10 in Utah).
  • Unverified X screenshot alleging SU-BND's transponder activated only three times on Sept 10 (the Erika Kirk 10:05 AM / "Andrew" Scottsdale 1:40 PM / Tyler Robinson 2:29 PM claim).
  • @AnaEscobarShow on X — cited for the claim that N102DZ "linked up" with SU-BND at Duncan Aviation after N102DZ's ~3:30 PM landing, describing SU-BND as "still there on and running" (an unverified ground-positioning reading).

Laws (Charlie Kirk)​

  • SU-BND's full Provo work orders, the crew and passenger records for its multi-month 2025 stay, and the ADS-B history needed to settle the "73 overlaps" dispute are exactly the kinds of records the Charlie Kirk Investigation Laws are designed to force into the open — so the maintenance explanation and the surveillance theory can both be tested against documents 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-BND — 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-BND — 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.