T7ELL & EJM36 (Flagged Tails)
When researchers expanded the Egypt story from two jets (SU-BTT, SU-BND) to a five-plane armada, Project Constitution's post also flagged two additional foreign tails: T7ELL and EJM36. Public route detail for these two is thin compared to the SU-registered fleet — they appear in source notes as "more planes" grouped for disclosure purposes.
Source: @ProjectConstitu on X amplifying the five-plane Provo swarm narrative.
What is documented publicly
| Tail | Public detail level |
|---|---|
| T7ELL | Named in CK_FILE and Egyptian Armada fleet list; no standalone ADS-B timeline published on this site yet |
| EJM36 | Same — flagged for manifest review under proposed Fix Laws |
Unlike SU-BTT/SU-BND, these tails do not yet have independent per-tail pages with verified Provo legs on September 10. They are catalogued so the fleet picture matches the research record and law drafts.
Investigative status
Open questions:
- Aircraft type and registry state for each tail
- Any Provo Municipal (PVU) appearances in 2025 flight logs
- Passenger overlap with SU-BTT Sept 4 drop-off claims
- Whether either tail routes through Israel per Israel Planes methodology
Until ADS-B screenshots or FOIA manifests surface, treat T7ELL and EJM36 as placeholder flags — not established participants in the assassination.
Laws (Charlie Kirk)
Full flight records, crew, and passengers for T7ELL and EJM36 are explicitly requested alongside the SU- armada in the Charlie Kirk Investigation Laws.
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 (T7ELL & EJM36 (Flagged Tails)) should be read with the Planes overview and Sept 10 flight timeline for cross-checks.
What the two identifiers actually are
Both tails were carried into this investigation as if they were two more Egyptian airframes alongside the SU- fleet. Neither identifier supports that reading, and the difference matters enough to state before anything else on this page.
| T7ELL | EJM36 | |
|---|---|---|
| Format | Aircraft registration | Aircraft callsign |
| Prefix / designator | T7- | EJM |
| What that prefix means | The civil registration prefix of the Republic of San Marino | The ICAO three-letter operator designator for Executive Jet Management, a United States operator (a NetJets company) |
| Is it Egyptian? | No. Egyptian civil registrations use SU- | No. It is a US operator's flight identifier |
| Published legs on this site or in the source threads | None | None |
| Airport, date or Kirk/TPUSA pairing ever published | None | None |
Two consequences follow, and this site should state both rather than carry the fleet-list framing unexamined:
- "Five Egyptian planes plus two more" is not what the identifiers say. The five SU- tails (SU-BTT, SU-BND, SU-BTU, SU-BTV, SU-BGM) are Egyptian-registered. T7ELL is San Marino-registered. EJM36 is a US callsign that may not be a distinct airframe at all — a callsign can belong to an aircraft already on the list under a different identity, which is exactly the kind of double-count that inflates a fleet tally.
- A fleet-list mention with no sourced leg is a placeholder, not an overlap. Neither identifier contributes anything to the following-pattern claim, because neither has a date, an airport, or a movement attached to it anywhere in the public record.
The T7- prefix is not a dead end — it is a documented Egyptian intelligence pattern
The San Marino prefix would ordinarily end the inquiry. It does not, because there is a separate, sourced, non-hypothetical case of an Egyptian intelligence aircraft carrying a T7- registration, and it is worth setting out precisely — while being clear it is a different tail.
On 29 August 2024, the aviation-tracking account @Dinlas3 posted:
#T7EGY Bombardier BD-700 w/ reg. 🇸🇲 T7-EGY utilized by The head of the 🇪🇬 Egyptian General Intelligence, Abbas Kamel, from Cairo, Egypt to 🇸🇩 Port Sudan on 8/23, and went to 🇨🇩 Brazzaville, Congo on 8/26 and 🇰🇪 Nairobi, Kenya before heading back to El-Alamein. #500215 @Borrowed7Time
The attached tracking panel shows a white-and-gold Bombardier Global 7500, "T7-EGY" on the rear fuselage, "7500" on the tail fin, sourced to Planespotters.net.
Two months later, on 21 October 2024, the analyst @doyaksec (Donato Yaakov Secchi) posted on the same subject:
#Egypt #Intelligence — Al #Sisi has removed the head of intelligence, Abbas #Kamel, appointed advisor to the pres and replaced by his deputy, General Hassan Mahmoud Rashad. #CIA and #Mossad have leaked #disturbance for the removal of Kamel. Come on! Al Sisi changes his strategies?
What this establishes, and what it does not:
- It establishes that the T7- San Marino register is used to carry an Egyptian government intelligence aircraft. San Marino has no meaningful domestic aviation industry; the T7- register is widely used as a flag of convenience for privately and state-operated business jets, and at least one aircraft on it was publicly identified as the ride of Egypt's General Intelligence Service chief.
- It does not establish that T7ELL is such an aircraft. T7ELL and T7-EGY are different registrations. No source has published a type, an operator, an owner, a flight, or a date for T7ELL. Anyone reading this page should treat the connection as what makes the tail worth a records request, not as a finding.
- It does not name anyone as a suspect. Abbas Kamel and Hassan Mahmoud Rashad are named here only because they are publicly identified officeholders in reporting about the aircraft's use, and no wrongdoing by either is established or alleged.
Tested against the TPUSA event calendar: nothing to test
Every other tail in this fleet gets a co-location test on its page against site/docs/Planes/following/tpusa_events.csv — the 139-row dated record of Charlie Kirk and TPUSA appearances from 4 January 2022 to 29 October 2025 that is the spine of the Following section.
| Tail | US ground windows in the public record | Windows tested | Overlaps with a TPUSA event in the same state within 3 days |
|---|---|---|---|
| SU-BTT | 6 | 6 | 1 — Provo, 4–10 Sep 2025 |
| SU-BND | 1 (113 days) | 1 | 1, on day 111 of 113 |
| SU-BTU | 10 | 10 | 0 |
| SU-BTV | 14 | 14 | 0 |
| SU-BGM | 1 | 1 | 0 |
| T7ELL | 0 | 0 | not testable |
| EJM36 | 0 | 0 | not testable |
That is the honest entry for these two tails, and it should stay on the page in that form. They cannot be shown to have followed anyone, because no source has ever published a single flight for either identifier. Carrying a gap openly is worth more than filling it.
What would move either tail out of placeholder status
- A type and owner for T7ELL from the San Marino Civil Aviation Authority register — the register is small and the record is obtainable.
- A single dated ADS-B leg for T7ELL at any airport, from any tracker, with a screenshot.
- The airframe behind EJM36. Executive Jet Management files hundreds of flights under EJM callsigns; resolving EJM36 to a specific N-number would establish whether it is a distinct aircraft or a duplicate of one already listed.
- An FBO or ramp record at Provo Municipal, Lincoln, Wichita or Wilmington naming either identifier — the Fix Laws manifest-disclosure provision is written to compel exactly this.
What this aircraft would cost to buy new today
Not estimable. No aircraft type has been established for this tail in any sourced record so no comparable can be selected. EJM36 is an operator callsign format rather than a tail number so no single airframe can be priced.
Every other aircraft in this investigation is priced on Aircraft Costs. These two are the only entries on that table with no figure, and the reason is the same reason they have no published flight legs: there is not enough established about them to work with.
Flight data recovery
The recovery sweep covered T7-ELL — EJM36 is an operator callsign, not a registration, so there is no aircraft page anywhere to probe for it. T7-ELL turns out to be well recorded, and what the archives hold argues against grouping it with the Egyptian SU- tails rather than for it.
| Source | What it holds for T7-ELL |
|---|---|
adsb.lol globe_history | 5 days, 3 Sep 2025 – 11 Oct 2025 |
| globe.airplanes.live | 26 days, 3 Sep 2025 – 29 May 2026 |
| ADS-B Exchange monthly sample | 12 days, 1 Feb 2022 – 1 Aug 2026 |
| FlightRadar24 page | HTTP 200 in a browser on 24 August 2026, identity block intact — GLEX · Mode S 50018A, operator "Falcon Luxe" / "Falcon Luxe San Marino". 0 history rows on the free seven-day tier, meaning it had not flown in that window; older history paywalled. |
| Internet Archive | 0 page snapshots held; 0 flight rows recovered. |
An operator correction worth recording. This repo's fleet file cites the community database adsbdb giving the operator as Solairus Aviation. FlightRadar24's own page, read in a browser on 24 August 2026, gives Falcon Luxe / Falcon Luxe San Marino. Both are commercial charter operators and neither is an Egyptian government entity, which is consistent with the recovered traces — a Dubai- and Van Nuys-based global charter pattern, set out on Flight Data Recovery.
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/T7-ELL/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
- Both were flagged when the story grew from two jets to five.
- Neither has a Provo timeline like SU-BND or SU-BTV.
- Both are named for manifest review in the Israel routing methodology.
- Treat them as placeholder flags in the working memo, not participants.
Interesting In Other Areas
- Egyptian jets at Provo is the argument these tails were added to.
- Israel foreign leads separates routing inference from documented legs.
- Foreign-nexus flight records are exactly what would settle both tails.
- The four proposed laws request manifests and crew lists by name.
Other Pages In This Section
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 thisA tail described in commentary as one TPUSA insiders used, named in the draft disclosure laws over a reported October 2025 Fort Huachuca to Kalispell leg. Standalone sourcing is thin, and naming an aircraft accuses nobody.
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 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 this
Four federal laws modeled on the Epstein Files Act, drafted to force disclosure and mandate a real investigation. Every unanswered question in the aftermath is downstream of records nobody can compel today.
Read thisThis website's author is @HolonCitizen on X and YouTube/@HolonCitizen. Follow me there.
Interesting
- What passed over Orem was a purpose-built spy platform, not a passing business jet.
- One analysis calls the C2 entry wound mathematically impossible at the claimed roof angle.
- UVU hosted a CIA drone-ethics lecture six years to the day beforehand.