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. That distance matters: a spring flight is a long way from the afternoon Charlie Kirk was killed, and readers should weigh it against the account of how he actually died rather than treat proximity in a log as proximity to the act. 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
- 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?
- Was SU-BGM serviced at Duncan Aviation's Provo MRO, and do maintenance records account for both legs?
- 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)?
- Is there any SU-BGM presence in the September 2025 window, or is its record genuinely confined to the spring?
- Who authorized recurring Israel/Egyptian Air Force VIP access to a non-international US municipal airport across 2025?
The registry panel and the Provo record
A Flightradar24 flight-history export for this tail, compiled and watermarked by @WeAre_TheElite, gives both the aircraft's identity and the short slice of its record that puts it in Utah.
| Field | Value |
|---|---|
| Aircraft | Gulfstream IV |
| Type code | GLF4 |
| Mode S / ICAO hex | 010070 |
| Serial number (MSN) | 1048 |
| Airline (as listed) | Egypt Goverment (spelled that way in the source) |
| Operator (as listed) | (blank) |
| Photo credits on the type images | © Paun Florin Laurentiu / Jetphotos; © Stephen J Stein / Jetphotos |
SU-BGM pairs with SU-BND as the two older Gulfstreams in an otherwise Falcon 7X fleet. Like SU-BND, its export carries no operator entry — a database detail worth noting whenever this aircraft is described as "Egyptian military," which is an inference from the SU- registration prefix and from its company in the Provo cluster rather than something the registry states.
The logged Provo legs
The export shows three consecutive legs, and all three involve Provo:
| Date | From | To | Duration | STD | ATD | STA | Status |
|---|---|---|---|---|---|---|---|
| 10 Apr 2025 | Provo (PVU) | Provo (PVU) | 0:55 | 4:11 PM | 3:16 PM | 4:11 PM | Landed 4:11 PM |
| 16 Apr 2025 | Provo (PVU) | Goose Bay (YYR) | 4:55 | 5:10 PM | 12:14 PM | 8:10 PM | Landed 8:10 PM |
| 16 Apr 2025 | Goose Bay (YYR) | Paris–Le Bourget (LBG) | 5:06 | 9:01 PM | 9:16 PM | 7:09 AM | Landed 7:22 AM |
Three details in that short table carry more weight than their length suggests.
Two Egyptian jets were at Provo simultaneously in April 2025
SU-BTU was on the ground at Provo from 8 April to 14 April 2025. SU-BGM flew a Provo→Provo sortie on 10 April and did not depart Utah until 16 April.
So for roughly a week in April, two Egyptian-registered jets were parked at the same small Utah regional airport at the same time — and a third, SU-BND, would arrive on 23 May and stay until September. This is five months before the assassination, and it has not previously been set out on this site.
That simultaneity is genuinely double-edged, and both readings deserve stating:
- It strengthens the maintenance explanation. Operators send aircraft to the facility they have a relationship with. Two airframes from the same fleet overlapping at the same MRO is ordinary — it is what a shop with an account looks like.
- It weakens the "one anomalous visit" framing in both directions. The September 2025 Provo stay is not an isolated event to be explained; it is the fourth or fifth in a series stretching back to at least April. That undercuts the reading of September as uniquely significant, and it also means the Provo relationship is deeper and longer-running than the assassination-window coverage implies.
The 10 April Provo→Provo round-robin
A 55-minute flight that departs Provo and lands back at Provo is the same signature that SU-BND produced on 5 September 2025 with a 1-hour-8-minute Provo→Provo sortie. Two different Egyptian jets, five months apart, each flew one closed-loop local flight out of Provo.
The mundane reading is a post-maintenance functional check flight — an aircraft coming out of a heavy inspection is flown for roughly an hour to verify systems before release, and it returns to the shop that did the work. Two of them is exactly what two completed maintenance visits produce. The less mundane reading is a local pattern flight of some other kind. The tracker log alone cannot separate them, and this page does not claim to.
What can be said is that if the 5 September SU-BND flight is treated as anomalous, consistency requires treating the 10 April SU-BGM flight the same way — and an April closed-loop, five months before the event, is very hard to fit into any narrative about the assassination.
Goose Bay, not Wilmington
SU-BGM leaves North America via Goose Bay, Newfoundland, not via Wilmington, Delaware. So does SU-BND on both its inbound (23 May) and outbound (13 Sep) transits.
That is a clean split in the fleet's routing, and it maps onto aircraft type rather than onto anything else:
- The three Falcon 7Xs (SU-BTT, SU-BTU, SU-BTV) route out through Wilmington (ILG) on every single rotation.
- The two Gulfstream IVs (SU-BGM, SU-BND) route through Goose Bay (YYR).
The Falcon 7X is a long-range trijet with roughly 5,900 nm of range; the Gulfstream IV is an older design with materially less. Goose Bay is the classic North Atlantic tech stop for aircraft that cannot make the crossing in one leg. The split is a range-and-fuel split, not a mission split — which is worth knowing, because the recurring Wilmington stop has been read on this site and elsewhere as significant in itself. On this evidence it is significant only for the aircraft that need less fuel to reach it, and the fleet's other half does not use it at all.
The April window, tested against the TPUSA event calendar
SU-BGM has the thinnest US record of the five Egyptian tails — one Provo local sortie on 10 April 2025 and a departure on 16 April 2025. Testing it against Charlie Kirk's public itinerary takes one row, and the answer is unambiguous.
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 carrying a certainty flag. It is the spine of the Following section.
The one ground window
| On the ground | Airport | Nearest TPUSA event in Utah, any year | Gap |
|---|---|---|---|
| 10 Apr – 16 Apr 2025 | Provo (PVU), UT | 10 Sep 2025 — Charlie, Orem, UT — The American Comeback Tour, Utah Valley University | 147 days |
There is no overlap. The nearest TPUSA event in the state of Utah is the UVU appearance five months later — the one at which Charlie Kirk was killed. In the whole 139-row calendar there is no Utah event in April 2025, and none within three months of SU-BGM being there.
Where Charlie Kirk actually was that week
| Date | Where | Event |
|---|---|---|
| 8 Apr 2025 | Urbana, IL | American Comeback Tour — University of Illinois Urbana-Champaign |
| 8 Apr 2025 | Normal, IL | American Comeback Tour — Illinois State University |
| 10 Apr 2025 | West Lafayette, IN | American Comeback Tour — Purdue University |
| 11 Apr 2025 | East Lansing, MI | American Comeback Tour — Michigan State University |
On 10 April 2025 — the day SU-BGM flew its 55-minute closed loop out of Provo Municipal — Charlie Kirk was on stage at Purdue, in Indiana, roughly 1,500 miles away. The next day he was in Michigan. He was not in Utah at any point in that week, and neither was any TPUSA event.
That is worth stating plainly on a site that argues the following pattern is real: for this tail, on this evidence, the pattern is not there. SU-BGM's presence in the Provo cluster is a fact about the fleet's relationship with Provo Municipal Airport, not a fact about Charlie Kirk's movements. Adding it to a "five-plane armada" headline without this test attached is how a real anomaly — the September window — gets dismissed along with the padding around it.
What this test does and does not settle
- It tests Charlie's side, not Erika's. Of 139 rows, exactly one places Erika Kirk at a TPUSA event before 10 September 2025. The tallies that produced the 68/73 numbers were measured against her claimed locations, and her flight logs are reported erased — see Erika's Flight Logs Erased. Nothing here refutes those numbers; it records that no public source reproduces them for this tail.
- The calendar records public events only. It does not capture private travel, and it cannot rule out that someone connected to the case was in Utah that week.
- A clean miss is still a finding. It is the reason this page treats SU-BGM as evidence about the breadth of the Provo relationship and not as evidence about the assassination.
What this aircraft would cost to buy new today
- Type (FAA-confirmed): Gulfstream IV
- Registered owner: Egyptian registry (not in FAA database)
- Still built today? No — G-IV built 1985-2002
- Priced against: Gulfstream G500
- Cost to buy new today: ~$45 million
Gulfstream IV out of production. The G500 is the closest in-production Gulfstream by cabin class at ~$45M list; the larger G600 runs ~$58.8M.
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
SU-BGM has the thinnest archive coverage of any of the Egyptian tails, and that is a coverage problem rather than a removal. A foreign-registered jet spends most of its life outside the range of the volunteer receivers that feed these archives, so the days they hold are simply the days it happened to fly within earshot of one. An absent day means nobody heard the aircraft; it does not mean the aircraft did not fly, and it does not mean a transponder was off.
| Source | What it holds for SU-BGM |
|---|---|
adsb.lol globe_history | 2 days, 6 Sep 2025 and 16 Sep 2025 |
| globe.airplanes.live | 5 days, 6 Sep 2025 – 16 May 2026 |
| ADS-B Exchange monthly sample | 1 day, 1 Aug 2023 — a single sample, the sparsest in the fleet |
| FlightRadar24 page | HTTP 200 in a browser on 24 August 2026, identity block intact — GLF4 · Mode S 010070 · Egypt Government. 0 history rows on the free seven-day tier, meaning it has not flown in that window; older history paywalled. |
| Internet Archive | 1 page snapshot held — a FlightRadar24 page captured 7 May 2020 — and 6 flight rows were recovered off it. That table is the only page-derived flight history this tail has. |
Removed from: nothing. No tracking site was found to have removed this aircraft's page. Our scripted probe recorded HTTP 403 from FlightRadar24, RadarBox and Planespotters, and those 403s are robot blocks rather than removals — five unrelated control aircraft got the identical 403 from the identical script, and all of them load normally in a browser. See What A 403 Actually Means.
Raw files: site/docs/Planes/SU-BGM/data/recovered/ — the source is in every filename, and each
file has a .meta.json sidecar recording source, URL, HTTP status, bytes and date.
Fleet-wide: Flight Data Recovery · Per-Aircraft Recovery Status
Interesting In This Area
- Its only published legs are April 2025, months before September 10.
- Unlike SU-BTT and SU-BTV, no Israel date list was ever compiled.
- Provo hosts a maintenance hangar, the counterpoint running through every armada tail.
- It was given no colour label, unlike the blue plane.
Interesting In Other Areas
- Egyptian jets at Provo argues the fleet claim as intelligence evidence.
- Israel foreign leads collects what the Israel thread actually rests on.
- John Cullen pushes hard on other aircraft yet discounts this fleet.
- Foreign-nexus flight records are reportedly among the withheld material.
Other Pages In This Section
An Egyptian-registered aircraft that flight-trackers pulled into the case. The page separates what the ADS-B record actually shows from what the threads made of it.
Read this
Utah Cox Foreign Meetings (Claims)
Commentary alleges the Utah governor held back-to-back closed-door meetings with Egyptian and French figures thirteen days after the killing. The page records the claim and states plainly that no wrongdoing by any official or diplomat has been shown.
Read this
The Kirk family aircraft, reported flying Scottsdale into the Salt Lake City area on the morning of September 10. It matters because it anchors where the party was in the hours before the event.
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 this
The leads pointing outside the United States — phones, travel, SIGINT, search patterns — and the prior question of whether the government ran any of them down at all.
Read this
The open-source investigator who put aircraft at the centre of this case — ADS-B tracks, altitude and speed profiles, departure fields. The page also documents where his claims cut against him.
Read thisForeign-Nexus Flight Records Withheld (Claims)
Tail numbers, routes and times are all citizen trackers can see; manifests, cargo logs, visas and security waivers are where the foreign-nexus leads stop. A lead testable only with records nobody will release stays permanently open — which is itself the complaint.
Read thisSources
- 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.
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-BGM Israel/Egyptian Jet) 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
- An Army ISR jet reportedly dove to roughly 204 feet near campus minutes after the shot.
- Studies show RDX survives on nylon and cotton — yet the shirt was never publicly tested.
- On an alleged 911 call someone reportedly says "get that off of him".
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-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.