SU-BTU Israel/Egyptian Jet
SU-BTU is an Egyptian-registered jet — described by independent trackers as a Dassault Falcon 7X — named as one of the five aircraft in the "Israel/Egyptian Plane Armada" that public researchers say cycled through Provo, Utah during 2025. Unlike the two lead jets in that cluster — SU-BTT ("the yellow plane") and SU-BND ("the blue plane") — there is very little standalone reporting on SU-BTU. Its significance in the public commentary comes almost entirely from its membership in the fleet pattern, not from any single documented event tied to this tail alone.
Read the Israel/Egyptian Plane Armada hub page first — the bulk of the analysis, the fleet timeline, the source list, and the counterarguments live there. This page collects only what is specific to SU-BTU, and is honest that the standalone record is thin. None of it establishes any link to the afternoon Charlie Kirk was assassinated at Utah Valley University; the cover-up questions raised elsewhere on this site rest on far stronger material than a single foreign tail number's Provo landings.
Aircraft identification
- Tail number: SU-BTU
- Type: Egyptian-registered jet; described by trackers as a Dassault Falcon 7X (long-range business jet)
- Registry / operator: Israel/Egyptian Government / Israel/Egyptian Air Force use (per the framing in public coverage)
- Color label: None. Candace Owens's color-coded shorthand ("yellow plane," "blue plane") was applied to SU-BTT and SU-BND; the master flight-log notes state no color label was attributed to SU-BTU.
- Role in coverage: One of three additional Israel/Egyptian tails (with SU-BTV and SU-BGM) added to the "armada" narrative after the original SU-BTT / SU-BND timeline.
Flight history relevant to the case
Every item below comes from open-source researchers working from public flight-record screenshots. None has been independently verified; treat the dates and routes as reported claims.
- May 27, 2025: Investigation notes record SU-BTU flying into Provo, and those notes allege that one of the passengers aboard was Walid Mahmoud (see Open questions — this is an unverified online claim about a living person).
- June 2, 2025: The notes record the Egyptian passenger "Walid" departing Provo.
- Feb 14, 2025: Provo → Wilmington, DE (per the "five-plane armada" log thread).
- Mar 2, 2025: Detroit → Provo.
- Aug 8, 2025: Minot, ND → Provo.
The log thread that introduced SU-BTU summarized it as making "multiple NE/UT hops tied to TPUSA Faith tours." That phrasing is the researcher's characterization, not a confirmed itinerary.
Alleged Israel trips
Separately from the U.S. overlaps, a flight-log thread compiled by @nihilox and shared by @ProjectConstitu claims SU-BTU made a long run of trips to Israel across one year. The researchers allege the public logs show these as Cairo-to-Cairo (CAI → CAI) or origin-N/A legs, and argue the jets actually landed in Israel with the transponder switched off — so the listed dates are, by their own framing, an inference from a claimed blackout pattern, not confirmed Israel landings. None of this has been independently verified, and the same Cairo-to-Cairo logs are equally consistent with the routine in-country flying of a government VIP jet.
Dates the thread attributes to SU-BTU (one calendar year):
- January: Jan 05, Jan 08, Jan 12
- February: Feb 05, Feb 11, Feb 16, Feb 23
- March: Mar 02, Mar 25
- April: Apr 15
- May: May 10, May 17
- June: Jun 14 (two flights), Jun 21, Jun 24
- July: Jul 02, Jul 05, Jul 06, Jul 08, Jul 13
- September: Sep 20
- December: Dec 14
The same researchers posted parallel Israel-trip lists for SU-BTT and SU-BTV, and present the three lists together as a "consistent and undeniable" pattern. That characterization is the thread's, not an established finding. The only Israel leg with outside corroboration in this material is an SU-BTT flight (not SU-BTU) reported by Israeli Channel 12 News; no comparable corroboration has been published for any SU-BTU date above.
Theories about the aircraft's role
These are framed as open theories raised by independent commentators, not conclusions:
- Fleet-pattern surveillance — that SU-BTU, as part of a recurring multi-jet Israel/Egyptian presence, fits the broader "intel-vacuum" theory that a foreign government may have been monitoring TPUSA events and the Kirk family. This theory lives at the fleet level on the Armada hub; SU-BTU's individual contribution to it is limited.
- A passenger of interest — because the notes place a named Egyptian passenger aboard SU-BTU's May 27 Provo arrival, some threads treat the aircraft as part of the "who was being shuttled through Provo" question. The same name has been floated by other threads in connection with the SU-BTT Wilmington leg, so the sourcing is inconsistent (see below).
Counterpoint — the maintenance-contract explanation
In fairness, the simplest reading of the fleet's recurring Provo visits is a service relationship, not an operation. Provo Municipal Airport hosts Duncan Aviation, a full-service maintenance, repair, and overhaul (MRO) facility, and skeptics — including investigator John Cullen — have argued the Israel/Egyptian jets' repeated appearances are most consistent with an ongoing maintenance / service contract rather than surveillance tasking. A foreign VIP Falcon routing through a known MRO hub is unremarkable on its own. This counterpoint applies to the whole armada and is covered more fully on the hub page; transponder gaps and trackers "snapping" an origin to the nearest public field can also be mundane data artifacts rather than evidence of anything covert.
Open questions
- Is SU-BTU's individual flight record (May 27 arrival, June 2 departure, and the 2025 NE/UT hops) borne out by independent ADS-B history, or are some legs misattributed — as a skeptic's audit alleged for several of the SU-BTT overlaps?
- Who were the passengers on SU-BTU's 2025 Provo visits, and is there any manifest for the May 27 arrival?
- The investigation notes name Walid Mahmoud as a passenger. This is an unverified online claim about a living person who has not been charged with any crime, and the same name appears elsewhere tied to a different jet (SU-BTT). Which, if either, attribution is accurate?
- What is the operational or contractual relationship between SU-BTU and the other four armada tails (SU-BTT, SU-BND, SU-BTV, SU-BGM)?
The registry panel and full 2025 flight record
A Flightradar24 flight-history export for this tail, compiled and watermarked by @WeAre_TheElite, gives the aircraft's identity and its complete recent US pattern. The registry panel:
| Field | Value |
|---|---|
| Aircraft | Dassault Falcon 7X |
| Type code | FA7X |
| Mode S / ICAO hex | 0101D0 |
| Serial number (MSN) | 243 |
| Airline (as listed) | Egypt - Air Force |
| Operator (as listed) | Egypt - Air Force |
| Operator code | EGY |
| Age (2015 build) | 10 years |
Header photographs on the Flightradar24 aircraft-history page captured for this tail are credited to Gilles ASTRE and David Andrade, 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.
SU-BTU is the middle airframe of three consecutive Falcon 7X serials delivered to the same operator — SU-BTT is MSN 239 (2013), SU-BTU is MSN 243 (2015), SU-BTV is MSN 246 (2014). Their hex codes are equally close: 0101D3, 0101D0, 0101D1. Three near-identical aircraft on near-identical routes with registrations differing by one letter is the structural reason this tail is so frequently confused with its siblings, and it is why the hex code should be the matching key in any audit.
The four US rotations in the export
| Date | From | To | Duration | Landed |
|---|---|---|---|---|
| 25 Nov 2024 | Cairo (CAI) | Paris–Le Bourget (LBG) | 4:13 | 12:15 PM |
| 26 Nov 2024 | Paris (LBG) | Omaha (OMA) | 9:12 | 1:45 PM |
| 26 Nov 2024 | Omaha (OMA) | Lincoln (LNK) | 0:19 | 4:28 PM |
| 01 Dec 2024 | Lincoln (LNK) | Wilmington (ILG) | 2:02 | 12:34 PM |
| 03 Dec 2024 | Wilmington (ILG) | Cairo (CAI) | 9:36 | 12:39 AM |
| 16 Jan 2025 | Cairo (CAI) | Paris (LBG) | 4:18 | 12:20 PM |
| 17 Jan 2025 | Paris (LBG) | Omaha (OMA) | 9:10 | 1:07 PM |
| 17 Jan 2025 | Omaha (OMA) | Lincoln (LNK) | 0:15 | 3:27 PM |
| 23 Jan 2025 | Lincoln (LNK) | Wilmington (ILG) | 1:38 | 1:22 PM |
| 24 Jan 2025 | Wilmington (ILG) | Cairo (CAI) | 9:52 | 12:57 AM |
| 15 Feb 2025 | Cairo (CAI) | Paris (LBG) | 4:05 | 12:20 PM |
| 16 Feb 2025 | Paris (LBG) | St. Louis (STL) | 9:10 | 1:07 PM |
| 16 Feb 2025 | St. Louis (STL) | St. Louis Downtown (CPS) | 0:15 | 3:27 PM |
| 22 Feb 2025 | St. Louis (CPS) | Wilmington (ILG) | 1:38 | 1:22 PM |
| 23 Feb 2025 | Wilmington (ILG) | Cairo (CAI) | 9:52 | 12:57 AM |
| 07 Apr 2025 | Cairo (CAI) | Paris (LBG) | 4:20 | 12:28 PM |
| 08 Apr 2025 | Paris (LBG) | Minot (MOT) | 8:11 | 10:14 AM |
| 08 Apr 2025 | Minot (MOT) | Provo (PVU) | 1:43 | 12:32 PM |
| 14 Apr 2025 | Provo (PVU) | Wilmington (ILG) | 3:19 | 11:22 AM |
| 15 Apr 2025 | Wilmington (ILG) | Cairo (CAI) | 10:10 | 12:40 AM |
| 23 Apr 2025 | Cairo (CAI) | Paris (LBG) | 4:12 | 12:17 PM |
| 24 Apr 2025 | Paris (LBG) | Omaha (OMA) | 8:52 | 10:50 AM |
| 24 Apr 2025 | Omaha (OMA) | Lincoln (LNK) | 0:16 | 12:10 PM |
| 30 Apr 2025 | Lincoln (LNK) | Wilmington (ILG) | 2:07 | 10:42 AM |
| 01 May 2025 | Wilmington (ILG) | Cairo (CAI) | 10:57 | 12:50 AM |
What the template shows
Read as a set, these five rotations are the same trip flown five times in six months, and the regularity is the finding:
- Every rotation is Cairo → Paris-Le Bourget → a US arrival airport → a short repositioning hop → sit → Wilmington → Cairo. Not once does it vary in shape.
- The repositioning hop is always 15 to 19 minutes. Omaha→Lincoln three times; St. Louis Lambert→St. Louis Downtown once; Minot→Provo is the outlier at 1:43. The short hops are what an aircraft does when the international arrival airport is not the destination — it clears customs at the big field and then moves to the facility.
- St. Louis Lambert (STL) → St. Louis Downtown (CPS) is a 15-minute hop across the Mississippi. Both are St. Louis. Any overlap spreadsheet that logs "St. Louis, MO" as a location visit is logging a customs stop and a taxi-equivalent flight, not a destination.
- The dwell is six to eight days every time, and Wilmington (ILG) is on the outbound leg every time and only the outbound leg.
- Lincoln, Nebraska is the most frequent endpoint — three of five rotations. As set out on the SU-BTT page, Duncan Aviation's main plant is at Lincoln, and it has held the Egyptian Air Force maintenance account since 1999, under a five-year direct contract signed in October 2015. That is the plain reading of this table.
The one visit that is not Lincoln
April 8–14, 2025 is SU-BTU's only Provo stay in the export. It routes Paris → Minot, North Dakota → Provo — the same Minot-then-Provo entry sequence later flown by SU-BTV on 27 May and by SU-BTT on 4 September. Three different aircraft, three different months, the same two-stop approach into Utah.
That repeated Minot routing is the detail worth pursuing, because Minot is not a normal transatlantic entry point for a business jet — it is a small North Dakota field adjacent to a nuclear-mission Air Force base, and the natural customs stops for a Cairo–Utah trip would be east-coast or Canadian. Whether Minot International (the civil field) or Minot AFB is meant in each case is not resolved by the export, which lists only "Minot (MOT)" — the civil airport code. Claims elsewhere that these aircraft "arrived via Minot Air Force Base" go beyond what MOT in a Flightradar24 export supports; the base is a separate facility with a separate identifier.
The consequence for the "purple plane" identification
Candace Owens's account places a passenger in Provo aboard SU-BTU on 27 May 2025, departing 2 June. This export puts SU-BTU at Provo on 8–14 April, and puts SU-BTV at Provo on exactly 27 May – 2 June. The discrepancy, and what rides on it, is set out in full on the SU-BTT page. It is unresolved, it is checkable, and it should be resolved before the person-across-aircraft inference built on top of it is relied on by anyone.
All five US rotations, tested against the TPUSA event calendar
SU-BTU has the cleanest test case of the five Egyptian tails, because its record is five near-identical rotations across six months. If the shadowing claim is right about this aircraft, the rotations should land where TPUSA was. They do not.
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, event listings and the Charlie Kirk Show archive, each row flagged EVENT_DATE (118 rows), PODCAST_PROXY (8), SCHEDULED_NOT_HELD (4) or AFTER_DEATH (9). It is the spine of the Following section.
The test is deliberately generous: a ground window counts as an overlap if any event in the calendar happened in the same US state within three days either side. That is roughly the criterion Liz Wheeler says the original overlap spreadsheet used, and far looser than "same city, same day."
Ten ground windows, zero overlaps
| On the ground | Airport / city | Nearest TPUSA event in that state, any year | Gap |
|---|---|---|---|
| 26 Nov – 1 Dec 2024 | Omaha then Lincoln (LNK), NE | 22 Oct 2024 — Charlie, Omaha, NE — Campaign mobilization | 35 days |
| 1 Dec – 3 Dec 2024 | Wilmington (ILG), DE | 3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour, University of Delaware | 790 days |
| 17 Jan – 23 Jan 2025 | Omaha then Lincoln (LNK), NE | 22 Oct 2024 — Charlie, Omaha, NE — Campaign mobilization | 87 days |
| 23 Jan – 24 Jan 2025 | Wilmington (ILG), DE | 3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour | 843 days |
| 16 Feb – 22 Feb 2025 | St. Louis (STL → CPS), MO | 19 Oct 2023 — Charlie, Springfield, MO — Live Free Tour, Missouri State University | 486 days |
| 22 Feb – 23 Feb 2025 | Wilmington (ILG), DE | 3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour | 873 days |
| 8 Apr – 14 Apr 2025 | Provo (PVU), UT | 10 Sep 2025 — Charlie, Orem, UT — American Comeback Tour, UVU | 149 days |
| 14 Apr – 15 Apr 2025 | Wilmington (ILG), DE | 3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour | 924 days |
| 24 Apr – 30 Apr 2025 | Omaha then Lincoln (LNK), NE | 22 Oct 2024 — Charlie, Omaha, NE — Campaign mobilization | 184 days |
| 30 Apr – 1 May 2025 | Wilmington (ILG), DE | 3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour | 940 days |
Not one of SU-BTU's ten US ground windows falls within three days of a TPUSA event in the same state. The closest miss is 35 days — Charlie Kirk's October 2024 Omaha campaign stop, five weeks before the aircraft's November arrival at Lincoln. The Delaware column is the starkest: Wilmington appears on the outbound leg of every single rotation, and the only Delaware event anywhere in the calendar is a Candace Owens campus stop in Newark in October 2022 — more than two years before the earliest of these flights and at a different city.
Where Charlie Kirk actually was during the Provo rotation
The 8–14 April 2025 Provo stay is the one that gets cited, because Provo is where the September story happens. Here is the same week on the Kirk side:
| 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 |
He was working the Midwest campus circuit — Illinois, Indiana, Michigan — for the entire week SU-BTU was parked in Utah. Meanwhile SU-BGM was also at Provo on 10 and 16 April: two Egyptian jets, same small field, same week, and no TPUSA presence within 1,000 miles.
What this table means for the SU-BTU case
- It is the strongest evidence on this page for the maintenance reading. The rotations track Lincoln, Nebraska — Duncan Aviation's main plant, holder of the Egyptian Air Force maintenance account since 1999 — three times out of five. They do not track Charlie Kirk at all. A pattern that correlates perfectly with a maintenance contract and not at all with an itinerary is a maintenance pattern.
- It removes SU-BTU from the following claim on its own record. SU-BTU is not in Candace Owens's 68/73 tally to begin with; it was added later by @WeAre_TheElite to make the five-plane framing. This table is why that addition should be treated as fleet-context rather than as evidence.
- It does not touch the September question. Nothing here bears on SU-BTT's 4–10 September Provo stay, which is a separate aircraft on a separate date and is the one window in the whole fleet record that does produce a same-city hit.
The limits of this test
- 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 June 2025 Young Women's Leadership Summit, logged as "Both"). The overlap tallies were counted against her claimed locations, and her flight logs are reported erased — see Erika's Flight Logs Erased. Ten clean misses here do not refute those tallies; they establish that no public source reproduces them for this tail.
- The calendar records public events only — not private travel, donor meetings or studio days.
- The flight record is a tracker export, not a manifest. It shows where the airframe was, not who was aboard or why.
What this aircraft would cost to buy new today
- Type (FAA-confirmed): Dassault Falcon 7X
- Registered owner: Egyptian registry (not in FAA database)
- Still built today? No — out of production
- Priced against: Dassault Falcon 8X
- Cost to buy new today: ~$58-60 million
Falcon 8X successor pricing — same basis as SU-BTT.
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
This tail is the cleanest example in the fleet of two volunteer networks having different coverage of the same aircraft. adsb.lol holds nothing at all for SU-BTU, while globe.airplanes.live holds three days. That is ordinary and is not evidence of anything: the two networks run different feeders, with different antennas, in different places, so an aircraft heard by one can be missed entirely by the other. The monthly ADS-B Exchange sample reaches furthest back, to December 2022.
| Source | What it holds for SU-BTU |
|---|---|
adsb.lol globe_history | nothing — no day held |
| globe.airplanes.live | 3 days, 2026-04-26 to 2026-05-12 |
| ADS-B Exchange monthly sample | 9 days, 2022-12-01 to 2026-03-01 |
| FlightRadar24 page | HTTP 200 in a real browser on 24 Aug 2026 — 56 history rows on the free seven-day tier, everything older paywalled |
| Internet Archive | 1 page snapshot held (31 Aug 2022); 4 flight rows recovered off it |
Alleged overlaps. This tail carries no alleged overlap dates in the overlap register, so there is nothing here to test and nothing recovered. The Egyptian side of the following-planes claim is carried entirely by SU-BTT with 53 alleged dates and SU-BND with 16. See 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-BTU/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 standalone record is thin, like SU-BTV and SU-BGM beside it.
- The alleged Israel dates are inferred from Cairo-to-Cairo logs, as with SU-BTT.
- Only the lead jet has outside corroboration, from Israeli Channel 12 News.
- Provo hosts a maintenance hangar, the counterpoint carried through the whole fleet.
Interesting In Other Areas
- Egyptian jets at Provo frames the cluster as intelligence evidence.
- Mossad and TPUSA is where the organisational claim is set out.
- John Cullen attributes the Provo visits to maintenance contracts instead.
- A Nebraska army base visit in July starts the American leg.
Other Pages In This Section
A Falcon 7X counted in the armada that is rarely discussed on its own. The page is candid that its significance is membership in a pattern, and gives the maintenance-contract counterpoint room.
Read this
One base links the government jet that flew west before September 10 and the aircraft that carried the casket the day after. The page also separates the two tail numbers people keep confusing, 99-0404 and 99-0004.
Read this
Planes Following Charlie or Erika
The biggest allegation in the aircraft angle: that foreign government jets overlapped TPUSA travel for years and tightened in the final two months. The overlap counts disagree with each other, and the page shows exactly where.
Read thisA six-seat Beechcraft logged into Provo on September 10, listed so that no arrival that day goes uncounted. Nothing in the public record ties this aircraft, its crew or its passengers to the shooting.
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 thisA former representative's public allegation, presented as a reported claim and nothing more. The page asks only that the testimony be properly investigated so the truth can come out.
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 this
Nebraska Army Base Visit — SU-BTT (July 20, 2025, Claims)
The whole claim rests on ADS-B screenshots. The same-day tracker post names a civil airfield at Omaha; the later compilations name an Army base. The page shows exactly where the label changed.
Read thisSources
- Raw flight-log screenshots circulated by independent researchers (the "five-plane armada" thread crediting @WeAre_TheElite), amplified on X.
- Candace Owens podcast coverage of the Israel/Egyptian-jet timeline (focused mainly on SU-BTT and SU-BND).
- Public ADS-B / FlightRadar24 tracking data referenced by those researchers.
- Skeptic rebuttals to the overlap counts, and the maintenance-contract counterpoint associated with John Cullen.
The standalone, SU-BTU-specific sourcing is thin. Most of the evidentiary weight is at the fleet level on the Israel/Egyptian Plane Armada page.
Laws (Charlie Kirk)
- SU-BTU's passenger manifests, the records authorizing its Provo access, and any maintenance-contract paperwork that would confirm or refute the innocent explanation are exactly the kinds of records the Charlie Kirk Investigation Laws are designed to force into the open — alongside the other four armada tails.
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-BTU 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
- A Vice President flew the remains home himself on the government's VIP jet.
- A Bates-stamped analysis says Robinson was Mirandized hours before the "surrender".
- No video of the rooftop exists; one officer's later recollection carries the gravel and screwdriver.
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-BTU — 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-BTU — 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.