Skip to main content
← Planes

SU-BTV Israel/Egyptian Jet

SU-BTV is an Egyptian-registered VIP jet — described in flight logs as a Dassault Falcon 7X — that appears as one of the five tail numbers in what X researchers call the "Israel/Egyptian Plane Armada": a cluster of Israel/Egyptian government Falcons and Gulfstreams (SU-BTT, SU-BND, SU-BTU, SU-BTV, SU-BGM) that trackers say routed through Provo, Utah during 2025.

Be honest about the sourcing: standalone reporting on SU-BTV specifically is thin. It is rarely discussed on its own; its significance is almost entirely as a member of the fleet pattern. The bulk of the analysis — the timeline, the TPUSA-overlap claims, the maintenance counterpoints — lives on the hub page, Israel/Egyptian Plane Armada. This page collects only what public sources say about SU-BTV by name and frames every claim as an open, unverified allegation.

Aircraft identification

  • Tail number: SU-BTV
  • Type: Dassault Falcon 7X (per the flight-log screenshots circulated on X; "Egyptian-registered" in other notes)
  • Registry / operator: Egyptian-registered — described as Israel/Egyptian Government / Israel/Egyptian Air Force use
  • Nickname in coverage: None. Candace Owens color-coded SU-BTT ("yellow plane") and SU-BND ("blue plane"); SU-BTV carries no color label and is listed only in flight-overlap discussions.
  • Reported destination airport in Utah: Provo Municipal Airport (PVU), roughly 7 miles from Utah Valley University.

Flight history relevant to the case

SU-BTV surfaced publicly when raw flight-log screenshots — attributed to the account @WeAre_TheElite and amplified by @ProjectConstitu (Project Constitution) — were used to expand the "two Israel/Egyptian planes" story into a "five-plane armada." The dated legs below are those researchers' published readings of the logs, not independently verified records:

  • March 2, 2025: Provo (PVU) activity logged.
  • July 2, 2025: Provo local flight.
  • October 2, 2025: Provo activity — which one thread speculated, with a question mark, could be "post-assassination cleanup." This is rhetorical speculation, not evidence.
  • October 29, 2025: Cairo local flight.

Researchers characterize the pattern as "Provo spikes pre-September," grouping SU-BTV with the other four tails as recurring 2025 visitors to a non-international US municipal airport. No passenger manifest, tasking, or operator statement for any SU-BTV leg has been made public.

Alleged Israel trips

Separate from the Provo legs, a date list circulated on X claims SU-BTV made repeated 2025 runs into Israel. The list was compiled by @nihilox and shared by @ProjectConstitu (Project Constitution). Researchers allege these flights logged as Cairo-to-Cairo (CAI–CAI) or with the transponder off at points, and they claim the planes actually landed in Israel — an unverified reading of the data, not a confirmed itinerary. The dates as published:

  • January: Jan 05, Jan 08 (two flights), Jan 12 (two flights), Jan 14, Jan 21, Jan 28, Jan 29
  • February: Feb 12, Feb 18, Feb 19
  • March: Mar 02, Mar 09
  • April: Apr 08
  • May: May 10
  • June: Jun 17 (two flights)
  • July: Jul 06, Jul 15, Jul 19
  • August: Aug 10
  • September: Sep 02, Sep 23, Sep 24
  • October: Oct 01, Oct 29
  • November: Nov 04 (two flights), Nov 25
  • December: Dec 04

Treat this list as an OSINT allegation. The same maintenance and data-error counterpoints below apply: a falsified-log or "stealth" reading is one interpretation, but routine VIP movements, transponder artifacts, and miscounted dates are the mundane alternatives. No manifest or operator statement confirms any SU-BTV Israel landing.

Theories about the aircraft's role

All of the following are open theories advanced by independent commentators, not established facts:

  • Fleet-pattern surveillance — that the five Israel/Egyptian tails collectively shadowed TPUSA events and the Kirk family's movements (the "armada" framing). SU-BTV is cited as a data point in that pattern rather than as an individually documented surveillance flight.
  • Foreign orchestration — the @ProjectConstitu thread floated "Mossad proxies via Egypt" and alleged "no-scan DoD badges" dropping "experts" for drone/laser operations. These are unverified assertions made about the fleet as a whole, with no specific evidence tied to SU-BTV.
  • Routine VIP operations — the innocent reading (see the counterpoint below), under which SU-BTV's Provo stops are ordinary maintenance or VIP movements.

John Cullen's maintenance-contract counterpoint

Independent researcher John Cullen has pushed back on the foreign-operation reading of the Israel/Egyptian jets. His counterpoint — applied to the fleet, and therefore to SU-BTV as one of its members — is that the recurring Provo presence is best explained by a maintenance / service-contract relationship with the jet-service hub at Provo Municipal Airport, not by a covert tasking. Provo hosts Duncan Aviation, a full-service maintenance, repair, and overhaul (MRO) facility (airframe, engine, avionics, paint, interior). A foreign VIP Falcon cycling through Provo for service is, on this view, unremarkable.

Other mundane explanations also weigh against the sinister reading: a skeptic's audit of Owens's overlap counts reportedly found several of the cited dates wrong, transponder/track artifacts can mimic "stealth" behavior, and the companion "blue plane" SU-BND reportedly sat in Provo for months — more consistent with a long maintenance or storage stay than a surgical operation. These counterpoints are covered in full on the Israel/Egyptian Plane Armada hub.

Open questions

  1. Who were the passengers, and is there any manifest for SU-BTV's 2025 Provo visits?
  2. Is SU-BTV's reported type (Falcon 7X) confirmed by registry records, or only inferred from screenshots?
  3. What is the operational relationship, if any, between SU-BTV and the other four armada tails (SU-BTT, SU-BND, SU-BTU, SU-BGM)?
  4. Does SU-BTV's Provo presence reconcile with a Duncan Aviation service record, as John Cullen's maintenance-contract reading suggests?
  5. Who authorized recurring Israel/Egyptian-government access to a non-international US municipal airport?

The registry panel and the fullest US record of the five aircraft

A Flightradar24 flight-history export for this tail, compiled and watermarked by @WeAre_TheElite, gives both the aircraft's identity and the longest continuous US pattern of any jet in the Provo cluster.

FieldValue
AircraftDassault Falcon 7X
Type codeFA7X
Mode S / ICAO hex0101D1
Serial number (MSN)246
Airline (as listed)Egypt - Air Force
Operator (as listed)Egypt - Air Force
Operator codeEGY
Age (2014 build)11 years

Header photographs on the Flightradar24 aircraft-history page captured for this tail are credited to Chris Gimmillaro and Dave Potter, 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.

Eight US rotations, December 2024 to October 2025

DateFromToDuration
07 Dec 2024Cairo (CAI)Paris–Le Bourget (LBG)4:22
08 Dec 2024Paris (LBG)Wichita (ICT)9:57
10 Dec 2024Wichita (ICT)Wilmington (ILG)2:09
15 Dec 2024Wilmington (ILG)Cairo (CAI)10:38
02 Feb 2025Cairo (CAI)Paris (LBG)4:21
03 Feb 2025Paris (LBG)Detroit (DTW)8:29
03 Feb 2025Detroit (DTW)Lincoln (LNK)1:46
09 Feb 2025Lincoln (LNK)Wilmington (ILG)1:52
10 Feb 2025Wilmington (ILG)Cairo (CAI)10:19
16 Mar 2025Cairo (CAI)Paris (LBG)4:19
17 Mar 2025Paris (LBG)Omaha (OMA)8:39
17 Mar 2025Omaha (OMA)Lincoln (LNK)0:18
23 Mar 2025Lincoln (LNK)Wilmington (ILG)2:02
24 Mar 2025Wilmington (ILG)Cairo (CAI)10:29
29 Mar 2025Cairo (CAI)Paris (LBG)4:05
30 Mar 2025Paris (LBG)Detroit (DTW)8:03
30 Mar 2025Detroit (DTW)Wichita (ICT)1:55
03 Apr 2025Wichita (ICT)Wilmington (ILG)2:11
06 Apr 2025Wilmington (ILG)Cairo (CAI)11:11
26 May 2025Cairo (CAI)Paris (LBG)4:10
27 May 2025Paris (LBG)Minot (MOT)8:21
27 May 2025Minot (MOT)Provo (PVU)1:35
02 Jun 2025Provo (PVU)Wilmington (ILG)3:37
03 Jun 2025Wilmington (ILG)Cairo (CAI)10:26
29 Jul 2025Cairo (CAI)Paris (LBG)4:04
30 Jul 2025Paris (LBG)Wichita (ICT)9:58
03 Aug 2025Wichita (ICT)Wilmington (ILG)2:22
06 Aug 2025Wilmington (ILG)Cairo (CAI)10:01
04 Oct 2025Cairo (CAI)Paris (LBG)4:13
05 Oct 2025Paris (LBG)Omaha (OMA)9:20
05 Oct 2025Omaha (OMA)Lincoln (LNK)0:19
11 Oct 2025Lincoln (LNK)Wilmington (ILG)2:15
12 Oct 2025Wilmington (ILG)Cairo (CAI)10:53
29 Oct 2025Cairo (CAI)Cairo (CAI)0:16

This is the page where the maintenance reading is hardest to argue against

Eight rotations in eleven months, all identical in shape, and the destination cities are a maintenance itinerary rather than a political one:

  • Lincoln, Nebraska — three visits (Feb, Mar, Oct). Duncan Aviation's main plant, holder of the Egyptian Air Force maintenance account since 1999 (see SU-BTT).
  • Wichita, Kansas — three visits (Dec, Mar–Apr, Jul–Aug). The "Air Capital of the World," and home to Yingling Aviation, an FAA Part 145 facility that services Dassault Falcon aircraft.
  • Detroit (DTW) — two arrivals, both used as the transatlantic entry point before hopping onward (to Lincoln in February, to Wichita in March).
  • Provo, Utah — one visit, 27 May to 2 June 2025.
  • Wilmington (ILG) on the outbound leg of all eight rotations, and only ever outbound.

Two of the three US destinations this aircraft visits are the two best-documented Falcon maintenance centres in North America, and the operator has a publicly-announced, decades-old contract with one of them. A tally that scores each of these arrivals as a "location overlap" with a Kirk or TPUSA event in Nebraska or Kansas is scoring a maintenance rotation.

The 27 May – 2 June Provo stay, and why it matters beyond this page

SU-BTV's Provo window — arrival 27 May, departure 2 June 2025 — matches, to the day, the visit that Candace Owens attributes to SU-BTU in her August 2026 segment, and on which she builds the "purple plane" passenger link across aircraft. The same export puts SU-BTU at Provo six weeks earlier, on 8–14 April.

If the export is right, the aircraft in Provo in late May was this one. The full comparison and what rides on it is set out on the SU-BTT page. It is unresolved and it is checkable: SU-BTV is hex 0101D1, SU-BTU is hex 0101D0, and the raw ADS-B archive for 27 May 2025 would settle it in minutes.

This page takes no position on which is correct. It records that the question is open, that it has not been asked publicly before, and that a chain of inference about a named individual currently rests on the answer.

The Minot approach, again

Like SU-BTU in April and SU-BTT in September, SU-BTV entered Utah via Minot (MOT), North Dakota — Paris → Minot (8:21), then Minot → Provo (1:35), both on 27 May. Three separate aircraft used the same unusual two-stop approach into Provo across three separate months.

Note that MOT is the civil Minot International Airport identifier. Claims that these aircraft routed through Minot Air Force Base are a step beyond what the export shows; the base is a distinct facility. What the export does support is that a small North Dakota field was repeatedly used as the North American entry point for Utah-bound legs by an operator whose other US trips entered through Omaha, Detroit, or St. Louis. Why Minot for the Provo runs and not for the Lincoln ones is an open question with no published answer.

All seven US rotations, tested against the TPUSA event calendar

SU-BTV has the fullest US record of any of the five Egyptian tails — seven complete rotations between December 2024 and October 2025, covering Kansas, Nebraska, Michigan, Utah and Delaware. That breadth makes it the best available test of whether the fleet's American movements track TPUSA's calendar.

The calendar used is site/docs/Planes/following/tpusa_events.csv139 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 window counts as an overlap if any event happened in the same US state within three days either side. That is roughly the criterion Liz Wheeler says the original overlap spreadsheet applied.

Fourteen ground windows, zero overlaps

On the groundAirport / cityNearest TPUSA event in that state, any yearGap
8 Dec – 10 Dec 2024Wichita (ICT), KS13 Sep 2024 — Charlie, Manhattan, KS — Kansas State University86 days
10 Dec – 15 Dec 2024Wilmington (ILG), DE3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour799 days
3 Feb – 9 Feb 2025Detroit then Lincoln (LNK), NE22 Oct 2024 — Charlie, Omaha, NE — Campaign mobilization104 days
9 Feb – 10 Feb 2025Wilmington (ILG), DE3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour860 days
17 Mar – 23 Mar 2025Omaha then Lincoln (LNK), NE22 Oct 2024 — Charlie, Omaha, NE — Campaign mobilization146 days
23 Mar – 24 Mar 2025Wilmington (ILG), DE3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour902 days
30 Mar – 3 Apr 2025Detroit then Wichita (ICT), KS13 Sep 2024 — Charlie, Manhattan, KS — Kansas State University198 days
3 Apr – 6 Apr 2025Wilmington (ILG), DE3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour913 days
27 May – 2 Jun 2025Provo (PVU), UT10 Sep 2025 — Charlie, Orem, UT — American Comeback Tour, UVU100 days
2 Jun – 3 Jun 2025Wilmington (ILG), DE3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour973 days
30 Jul – 3 Aug 2025Wichita (ICT), KS13 Sep 2024 — Charlie, Manhattan, KS — Kansas State University320 days
3 Aug – 6 Aug 2025Wilmington (ILG), DE3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour1,035 days
5 Oct – 11 Oct 2025Omaha then Lincoln (LNK), NE22 Oct 2024 — Charlie, Omaha, NE — Campaign mobilization348 days
11 Oct – 12 Oct 2025Wilmington (ILG), DE3 Oct 2022 — TPUSA, Newark, DE — Live Free Tour1,104 days

Zero out of fourteen. Across ten months and five states, not one SU-BTV ground window falls within three days of a TPUSA event in the same state. The closest is 86 days.

Three specifics are worth pulling out because they are routinely cited the other way:

  • Kansas. Kansas is one of the five states in the clustering claim, and SU-BTV visited Wichita three times. The only Kansas event in the entire 139-row calendar is a September 2024 stop at Kansas State University in Manhattan — a different city, 130 miles away, and 86 days before the earliest of those visits. Wichita is a major Falcon service and aerospace hub; that is what the three visits track.
  • Detroit. SU-BTV entered the US via Detroit twice (3 February and 30 March 2025), and Turning Point Action's People's Convention was held in Detroit — in June 2024, eight and nine months earlier respectively. No source connects them.
  • The 27 May – 2 June Provo stay. This is the visit Candace Owens attributes to SU-BTU and to a named passenger. The flight logs put SU-BTV on those exact dates instead — the attribution conflict is set out in full on the SU-BTT page. Either way, the nearest Utah event is 100 days later, and the calendar shows no TPUSA event anywhere in the world on 27 May – 2 June 2025.

What this table means for the SU-BTV case

  • The pattern it fits is Duncan Aviation's, not TPUSA's. Lincoln, Nebraska three times; Wichita three times; Wilmington on the outbound leg of all seven rotations. Those are maintenance and customs geography. This is the page where, as noted above, the innocent explanation is hardest to argue against — and this table is why.
  • SU-BTV is not in the 68/73 tally. It was added by @WeAre_TheElite to build the five-plane framing. This test is the reason it should be carried as fleet context rather than as evidence of shadowing.
  • The October rotation is after the assassination. The 5–12 October 2025 window sits three-and-a-half weeks after 10 September, and the same Omaha→Lincoln→Wilmington shape repeats unchanged. A rotation that continues identically after the event is evidence the rotation was never about the event.

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 overlap tallies were counted against her claimed locations, and her flight logs are reported erased — see Erika's Flight Logs Erased. Fourteen 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.
  • The flight record is a tracker export, not a manifest.

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

Archive coverage for this tail is thin — a single day on adsb.lol, seven on airplanes.live, two monthly samples — and it is thin for the ordinary reason. These are volunteer receiver networks, not a registry: they hold whatever their feeders happened to hear. An absent day means nobody heard the aircraft, not that it did not fly and not that a transponder was off. The FlightRadar24 page itself loads normally.

SourceWhat it holds for SU-BTV
adsb.lol globe_history1 day, 2025-10-11
globe.airplanes.live7 days, 2025-10-11 to 2026-05-24
ADS-B Exchange monthly sample2 days, 2022-10-01 to 2025-10-01
FlightRadar24 pageHTTP 200 in a real browser on 24 Aug 2026 — 54 history rows on the free seven-day tier, everything older paywalled
Internet Archive0 page snapshots held; 0 flight rows recovered off them

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-BTV/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 published legs are March, July and October 2025, thinner than SU-BTT.
  • One thread called the October visit cleanup, which the page marks as rhetoric, not evidence.
  • Its Israel date list came from the same compiler as SU-BTU and SU-BGM.
  • No colour label was ever assigned to it, unlike the blue plane.

Interesting In Other Areas

Other Pages In This Section

September 10 Flight Timeline

The minute-by-minute aviation timeline for September 10 — the transponder window, the afternoon arrival, the hospital timing conflict. It is where the aircraft claims either line up with the clock or fail to.

Read this
This image shows a man dressed in green medical scrubs and a white lab coat being escorted outdoors by two security officers or law enforcement officials, with a third guard…

Roland R. Wright Air National Guard Base

The Utah Air National Guard base beside Salt Lake City International, where Air Force Two received the casket on September 11. A documented, respectful transport, recorded for the record rather than for suspicion.

Read this
This is a promotional graphic or digital collage showcasing "The Armstrong Williams Show" across multiple media devices.

ISR Program Context

What intelligence, surveillance and reconnaissance aviation actually does, and why a contractor structure keeps crews and tasking orders out of public reach. Read it before judging any single ADS-B track.

Read this

N55906 Cullen Flight

John Cullen calls this the gorilla in the room next to the N1098L elephant. Public reporting on the tail is thin, so the page records it as a lead worth pulling records on rather than a finding.

Read this

Elsewhere In The Investigation

Foreign-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 this
Google Trends screenshot: search term 645 W 925 S, region filter Israel, past 5 years, showing a flat line with one spike to 100 in April 2022

Israel Google Trends Spike for "645 W 925 S"

A Trends chart for one Orem address, filtered to Israel, is flat for five years except a single April 2022 spike. Two caveats land immediately: it is a different house on the same block, and Trends plots relative interest, not counts.

Read this

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
This image is a digital screenshot of a social media post on X (formerly Twitter) by user John Cullen.

John Cullen

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

Sources

  • Flight-log screenshots attributed to @WeAre_TheElite, amplified by @ProjectConstitu (Project Constitution) on X (the "five-plane armada" post).
  • SU-BTV Israel-trip date list compiled by @nihilox, shared by @ProjectConstitu on X.
  • Candace Owens podcast coverage of the broader Israel/Egyptian-jet pattern (SU-BTT / SU-BND focus).
  • Public ADS-B / flight-tracking data (FlightRadar24, ADS-B Exchange) circulated by independent researchers.
  • John Cullen — maintenance-contract counterpoint to the foreign-operation reading.
  • Additional OSINT coverage by Sam Parker, Ian Carroll, Ryan Matta, and Zeb Boykin.

Laws (Charlie Kirk)

  • SU-BTV's full flight records, passenger manifests, and the records authorizing Israel/Egyptian-government access to Provo — alongside the rest of the fleet — are exactly the kinds of documents the Charlie Kirk Investigation Laws are designed to force into the open, so the maintenance vs. surveillance question can be settled with evidence 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-BTV 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

Track This Aircraft

Research this aircraft's flight history yourself on both major flight-tracking sites. They differ in one important way:

  • FlightRadar24 — SU-BTV — 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-BTV — 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.