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 — one compilation specifically identifies it as a Gulfstream IV-SP, serial number 1332, built 2014, a designation reported by trackers and not independently confirmed)
- 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
- Why did SU-BND remain parked at Provo for nearly four months in 2025, and what work order or contract covered the stay?
- Who were the crew and any passengers associated with the aircraft during the Provo period?
- 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?
- Do the "73 overlaps" with Erika Kirk survive a documentary audit, given the skeptic's claim that several cited dates are wrong?
- Does John Cullen's maintenance-contract explanation fully account for SU-BND, or are there flight legs it does not explain?
The registry panel — and why this aircraft is different from the other four
A Flightradar24 flight-history export for this tail, compiled and watermarked by @WeAre_TheElite, carries a registry panel that separates SU-BND from the rest of the Provo cluster in two important ways:
| Field | Value |
|---|---|
| Aircraft | Gulfstream 4SP |
| Type code | GLF4 |
| Mode S / ICAO hex | 01003E |
| Serial number (MSN) | 1332 |
| Airline (as listed) | Private owner |
| Operator (as listed) | (blank) |
| Age (1998 build) | 27 years |
Header photographs on the Flightradar24 aircraft-history page captured for this tail are credited to Augustin Piffard and Gilles ASTRE, via Jetphotos. The credits are reproduced because uncredited use of a photographer's work is its own small wrong, and because they are part of what shows the screenshot is a genuine tracker page rather than a composite. Every person named across this material is indexed on Named people.
Compare that with its four companions, whose panels all read "Egypt Government" and "Egypt - Air Force" with operator code EGY:
| Tail | Type | Hex | MSN | Listed airline | Listed operator | Build |
|---|---|---|---|---|---|---|
| SU-BND | Gulfstream 4SP | 01003E | 1332 | Private owner | (none) | 1998 |
| SU-BTT | Dassault Falcon 7X | 0101D3 | 239 | Egypt Government | Egypt - Air Force | Nov 2013 |
| SU-BTU | Dassault Falcon 7X | 0101D0 | 243 | Egypt - Air Force | Egypt - Air Force | 2015 |
| SU-BTV | Dassault Falcon 7X | 0101D1 | 246 | Egypt - Air Force | Egypt - Air Force | 2014 |
| SU-BGM | Gulfstream IV | 010070 | 1048 | Egypt Goverment (sic) | (none) | — |
Two things follow, and they pull in opposite directions:
- SU-BND is not listed as a government or air-force aircraft at all. Flightradar24's database records it as a private owner with no operator entry. Everything on this page and elsewhere that describes it as "an Egyptian military plane" is using the SU- registration prefix (Egypt's civil registration block) plus its company in the Provo cluster as the basis for that description, not a registry entry. That is a meaningful weakening of the "foreign military aircraft" framing as applied to this specific airframe.
- But its hex code sits inside the same block. 01003E, 010070, 0101D0, 0101D1 and 0101D3 are all in Egypt's allocated ICAO 24-bit range, and the three Falcon 7Xs are consecutive serials (239, 243, 246) delivered 2013–2015 — a fleet purchase. SU-BND and SU-BGM are the older Gulfstreams. So the five are plainly related as a fleet even though the database describes two of them differently.
The honest formulation is that SU-BND is an Egyptian-registered Gulfstream IV-SP of 1998 vintage whose public database entry does not identify a government operator. A 27-year-old Gulfstream is also, bluntly, the kind of aircraft that generates long maintenance downtime — which matters for what follows.
The full Provo stay: 113 days, and only three flights in all of it
The same export gives SU-BND's complete movements around its Utah stay. This is the record that the "four months at a regional airport" claim rests on, and it is more striking in full than in summary:
| Date | From | To | Duration |
|---|---|---|---|
| 22 May 2025 | Cairo (CAI) | Paris–Le Bourget (LBG) | 4:18 |
| 23 May 2025 | Paris (LBG) | Goose Bay (YYR) | 5:48 |
| 23 May 2025 | Goose Bay (YYR) | Minot (MOT) | 3:44 |
| 23 May 2025 | Minot (MOT) | Provo (PVU) | 1:52 |
| 10 Jun 2025 | Provo (PVU) | Provo (PVU) | (no duration logged) |
| 05 Sep 2025 | Provo (PVU) | Provo (PVU) | 1:08 |
| 13 Sep 2025 | Provo (PVU) | Goose Bay (YYR) | 5:10 |
| 13 Sep 2025 | Goose Bay (YYR) | Paris (LBG) | 5:09 |
| 15 Sep 2025 | Paris (LBG) | Cairo (CAI) | 4:08 |
Arrival 23 May, departure 13 September: 113 days on the ground at a regional airport in Utah. In that entire span the aircraft logged exactly two flights, both of them Provo→Provo round-robins that landed where they started — one on 10 June and one on 5 September.
That record is the strongest single fact on this page, and it is genuinely double-edged:
- It argues hard for maintenance. A jet that sits for nearly four months and flies twice is not conducting operations. It is being worked on, or waiting for parts, or in storage. A 1998 Gulfstream IV in for a heavy check plus paint plus an avionics upgrade would look exactly like this. Duncan Aviation's Provo facility does precisely that work.
- But the 5 September flight is 1 hour 8 minutes long and lands back at Provo. That is not a five-minute post-maintenance run-up. It is a substantial sortie flown five days before the assassination by an aircraft that had not moved in nearly three months, and it is the flight described elsewhere on this page as a possible corridor run north of Provo. A maintenance test flight after a heavy check is entirely normal and often runs about an hour. So is a survey pattern. The duration alone distinguishes nothing — but the fact that this was one of only two flights in 113 days is why it draws attention at all.
The 10 June round-robin is logged with no duration recorded, meaning the tracker captured a departure and an arrival without a continuous track — the sort of gap that produces both innocent explanations (poor low-altitude coverage in the valley) and less innocent ones. It is unresolved.
The departure sequence, and the 19-hour question
The export's timings for the September 13 departure are worth setting out because they are the source of the "19-hour delay" claim:
| Leg | Scheduled (STD) | Actual (ATD) | Arrival (STA) | Status |
|---|---|---|---|---|
| Provo → Goose Bay | 6:07 PM | 12:57 PM | 9:07 PM | Landed 9:07 PM |
| Goose Bay → Paris | 9:10 PM | 9:57 PM | 7:06 AM | Landed 8:05 AM |
| Paris → Cairo (15 Sep) | 2:26 PM | 10:18 AM | 2:26 PM | Landed 2:26 PM |
Note that the tracker's scheduled and actual columns are not necessarily in the same time reference, which is a well-known reading hazard on these exports and the source of more than one erroneous claim in this investigation. Taken at face value the Provo departure is early against its scheduled time rather than late. Any assertion built on a delay at this airport should be checked against the raw track before it is relied on.
Note too that the export dates the departure to 13 September, whereas the independent analysis quoted elsewhere on this page gives 14 September. One of the two is wrong by a day, and neither has been reconciled against the raw ADS-B archive.
Why "the plane that stayed" matters more than the plane that left
Public attention went to SU-BTT because it departed on the morning of the assassination. The record above suggests the more interesting aircraft may be this one, for a reason that has nothing to do with drama:
SU-BND was on the ground at Provo for the entire period in which every other event on this site occurred. It arrived nearly four months before the assassination and left three days after it. Every arrival and departure of every other Egyptian jet in the cluster — SU-BGM through 16 April, SU-BTU in April, SU-BTV in late May, SU-BTT in September — happened at an airport where this aircraft was already parked.
That makes SU-BND the fixed point of the pattern rather than a participant in it, and it raises a question the shadowing framing does not ask: if a foreign fleet were rotating aircraft through Provo for maintenance, one airframe sitting there long-term is exactly what you would expect to see, and it would draw the others in. A four-month heavy check on one aircraft is a reason for the operator's other aircraft to use the same facility. The alternative reading — that a long-term parked aircraft was a standing platform of some kind — requires evidence about what was aboard it, and no such evidence has been published.
The 113-day Provo stay, tested against the TPUSA event calendar
SU-BND is the hardest tail to test this way, because it did not move. It landed at Provo on 23 May 2025 and left on 13 September 2025 — one continuous 113-day ground window with two local sorties in the middle of it. Any co-location test therefore asks a different question for this aircraft than for the Falcons: not did it follow him, but what was happening while it sat there.
The calendar used is site/docs/Planes/following/tpusa_events.csv — 139 dated rows, 4 January 2022 to 29 October 2025, built from TPUSA postings, campus press and event listings, each row flagged EVENT_DATE, PODCAST_PROXY, SCHEDULED_NOT_HELD or AFTER_DEATH. It is the spine of the Following section.
The one ground window
| On the ground | Airport | Nearest TPUSA event in Utah, any year | Gap |
|---|---|---|---|
| 23 May – 13 Sep 2025 (113 days) | Provo (PVU), UT | 10 Sep 2025 — Charlie, Orem, UT — The American Comeback Tour, Utah Valley University | 0 days |
The gap is zero — but only because the window is four months long. The Utah event fell on day 111 of 113. Read the other way, SU-BND was parked seven miles from Utah Valley University for 110 days during which no TPUSA event took place anywhere in Utah, and it was still parked there on the day one did.
Everything TPUSA did while SU-BND sat on the Provo ramp
| Dates | Who | Where | Event |
|---|---|---|---|
| 13–15 Jun 2025 | Both Charlie and Erika | Grapevine, TX | Young Women's Leadership Summit 2025 (10th anniversary) |
| 9–11 Jul 2025 | Charlie | Tampa, FL | Chapter Leadership Summit 2025 |
| 10–13 Jul 2025 | Charlie | Tampa, FL | Turning Point Academy Educators' Summit 2025 |
| 11–13 Jul 2025 | Charlie | Tampa, FL | TPUSA Student Action Summit 2025 |
| 6–8 Aug 2025 | Charlie | Rancho Palos Verdes, CA | Faith Forward Pastors Summit, Terranea Resort |
| 20–22 Aug 2025 | Charlie | Dallas, TX | Win the Storm |
| 21 Aug 2025 | Charlie | North Myrtle Beach, SC | Alex McFarland Speaker Series |
| 5–6 Sep 2025 | Charlie | Seoul, Korea | Build Up Korea 2025 |
| 7 Sep 2025 | Charlie | Tokyo, Japan | Sanseito symposium — his last speech abroad |
| 10 Sep 2025 | Charlie | Orem, UT | The American Comeback Tour, Utah Valley University |
| 11 Sep 2025 | Charlie | Woodland Park, CO | Truth and Liberty Conference (scheduled, not held) |
Eleven TPUSA events in eleven weeks, in Texas, Florida, California, South Carolina, Korea and Japan — and the aircraft did not move for any of them. Including the one event in the whole window that this repository can place Erika Kirk at: the June Young Women's Leadership Summit in Grapevine, Texas. SU-BND was on the ground in Utah, 1,000 miles away, for all three days of it.
This is the single most important thing on this page for anyone assessing the shadowing claim, and it points in an uncomfortable direction for that claim:
- A stationary aircraft cannot follow anyone. For 113 days SU-BND had exactly one location. Every "overlap" credited to it in that period is an artifact of Erika Kirk being alleged to have passed through Utah, not of the aircraft going anywhere.
- It is also why the maintenance reading is strongest here. A jet that sits for four months and flies twice — both times Provo→Provo — is in a hangar, not on a mission. The SU-BND registry panel puts the airframe at 27 years old (MSN 1332, 1998 build), which is exactly the age at which a Gulfstream IV goes in for a heavy check, paint and an avionics refit.
- And it is why the one date still matters. Whatever explains the other 110 days, on 10 September 2025 this aircraft's transponder came on, seven miles from UVU, and it did not take off. That is on this page's departure sequence section, and this table does not explain it away.
The limits of this test
- This tests Charlie's side, not Erika's. Of 139 rows, exactly one places Erika Kirk at a TPUSA event before 10 September 2025. The 68-and-73-overlap tallies were measured against her claimed locations, and her flight logs are reported erased — see Erika's Flight Logs Erased. This table cannot refute those tallies. It can only report that no public source reproduces them.
- The calendar records public events only. Private travel is invisible to it.
- The window is the aircraft's, not a person's. A 113-day window will collide with almost anything; the honest number here is not "one overlap" but "one overlap out of 111 possible days before it happened."
What this aircraft would cost to buy new today
- Type (FAA-confirmed): Gulfstream G550 (trackers also cite Gulfstream IV-SP)
- Registered owner: Egyptian registry (not in FAA database)
- Still built today? No — G550 ended 2021
- Priced against: Gulfstream G600
- Cost to buy new today: ~$58.8 million
G550 out of production; the G600 is Gulfstream's in-production aircraft in that cabin and range class. If the G-IV subtype is correct instead, the nearest new equivalent is the G500 at ~$45M.
List price is for a green airframe — interior completion, avionics options and any mission equipment are extra, and fleet buyers do not pay list. The full table for all 33 priced airframes in this investigation, with the method behind each figure, is on Aircraft Costs.
Flight data recovery
Coverage for this tail is moderate and begins on 3 May 2023, the day of the first alleged overlap. Its FlightRadar24 page loads normally, and two archived copies of that page were recovered from the Internet Archive — the only Egyptian tail here for which archived flight rows exist.
| Source | What it holds for SU-BND |
|---|---|
adsb.lol globe_history | 19 days, 2023-05-03 to 2025-09-15 |
| globe.airplanes.live | 27 days, 2023-05-03 to 2026-06-04 |
| ADS-B Exchange monthly sample | 6 days, 2022-01-01 to 2026-07-01 |
| FlightRadar24 page | HTTP 200 in a real browser on 24 Aug 2026 — 14 history rows on the free seven-day tier, everything older paywalled |
| Internet Archive | 2 page snapshots held (12 Oct 2025, 18 Nov 2025); 11 flight rows recovered off them |
Alleged overlaps. This tail carries 16 alleged overlap dates. 7 of them now have a recovered ADS-B track for that day, and 6 of those 7 are consistent with the alleged location. The single inconsistent result is 12 May 2023, alleged at St. Louis MO: the recovered track runs Paris Le Bourget to Inshas Air Base, Egypt. The strongest confirmations run the other way — 19 April 2024 and 23 May 2025 both end 1.4 km from Provo Municipal, and the 10 September 2025 track both starts and ends at Provo. A nearest-airport label is geometry, not a landing record, so the distances travel with the claim. Working shown on Overlap Recovery.
Removed from: nothing. No tracking site was found to have removed this aircraft's page. Our scripts recorded HTTP 403 from FlightRadar24, RadarBox and Planespotters, but all three return the identical 403 to unrelated control aircraft asked by the identical script. It is a robot block, not a deletion — see What A 403 Means.
Raw payloads are kept in site/docs/Planes/SU-BND/data/recovered/, with the source named in every filename and a .meta.json sidecar per file recording source, URL, HTTP status, bytes and date.
More: Flight Data Recovery · Per-Aircraft Status
Interesting In This Area
- Its departure is dated three different ways in the sources, unlike SU-BTT.
- Trackers allege it linked up with N102DZ at the Duncan Aviation ramp.
- A screenshot claims its transponder woke only three times on September 10.
- It is the best-documented secondary tail, ahead of SU-BTU and SU-BTV.
Interesting In Other Areas
- Egyptian jets at Provo is the intelligence framing of the same ground record.
- Israelis at UVU is a separate presence claim with its own sourcing.
- Candace Owens named the blue and yellow planes and drove the coverage.
- The SU-BTT movements timeline sets the fleet against the 2025 calendar.
Other Pages In This Section
A C-32A Air Force Two airframe logged into Las Vegas on May 27, 2025, three and a half months before the killing. It sits in the catalogue as an open question about a VIP movement, not as an allegation against anyone.
Read this
A tip reportedly from inside the booking process places the occupants of the Egyptian jets in one named Orem hotel from September 4. Folios and camera servers could settle it in a week.
Read this
A Bombardier Global 6500 flown by an Army ISR contractor, callsign AXLE10, ran an unusual low and slow profile near Orem on September 10. No track, tasking order, or sensor product from it has appeared in the prosecution.
Read thisElsewhere In The Investigation
Egyptian Jets — Provo Sept 4–10
Egyptian Air Force aircraft sat at Provo Municipal from September 4 and left the morning of September 10. The flight record is public; the reason is not.
Read thisThe contested claim of Israeli presence on campus on September 10, split into SIGINT, sightings and search patterns. Presence near an event does not establish participation in it.
Read this
She called Charlie her best friend and brother, then ran the largest independent probe of his death. She also published the texts, the tipline and the SUV photographs the rest of the case now argues over.
Read this
SU-BTT Plane Movements Timeline 2025
Every claimed 2025 movement of one Egyptian-registered Falcon, in date order. It sat at Provo the week of the assassination and left the morning of it, which cuts both ways — and the page says so.
Read thisSources
- 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.
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 (SU-BND Blue Plane) should be read with the Planes overview and Sept 10 flight timeline for cross-checks.
This website's author is @HolonCitizen on X and YouTube/@HolonCitizen. Follow me there.
Interesting
- That C-32A airframe type resurfaced the day after the killing, carrying the casket.
- A since-deleted security-firm post said another firm wanted to "remain in the shadows."
- Greg Shaffer said he was "stabbed in the back" over the last-minute security switch.
Related Areas
Related
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.
Images
Videos
Footage related to this page. Each card opens that clip's own page, with the video, the full write-up, and its source.
