Skip to main content
← Following

AI Assistant Answers About the Egyptian-Plane Overlaps

This directory already holds three source layers. The broadcasts are where the overlap claim was said. The X posts are where it spread. The press coverage is where it was written up. This page is the fourth layer, and the newest one: what a general-purpose AI assistant says when a member of the public asks it the question directly.

That layer matters for a plain reason. For most people now, the assistant is the first answer and often the only one. Nobody who types the question into Gemini reads the eleven location pages in this directory. They read one paragraph, and that paragraph decides what they think happened.

So the assistant answer gets logged here the same way every other relayed account in this directory gets logged: quoted, dated, sourced, and audited. This directory's standing rule is that a primary record outranks a relayed account. An AI answer is a relayed account. It is downstream of the same broadcasts, posts and write-ups already catalogued on the three pages above — and on the record below, it is downstream of a single note on a public wiki.

This page does not adopt the assistant's framing. It records what the assistant said, in full, and then checks it. One of its factual assertions is contradicted by this site's own primary-record page for the aircraft in question. Several of its figures are real and are already on this site with attribution the assistant dropped. Both of those findings are on this page, because both are true.

The question that was asked​

On 24 August 2026, Google Gemini was asked, in substance:

Look in the content of YouTube videos including YouTuber or Podcaster videos. Also look in all other places for information on Charlie Kirk and the claim that 77 occurrences where Egyptian-registered planes were at airports where either: 1) TPUSA events occurred, or 2) Charlie Kirk and his plane was at the airport, or 3) Erika Kirk was at (or her airplane was at). It could have been 77 occurrences or another number. Or anything in this area. Return as much as possible. Do not summarize.

Three things about that prompt are worth stating before the answer, because they frame what the answer did and did not do:

  1. It asked for the video and podcast layer specifically. YouTube segments and podcast episodes are where most of this claim's audience actually met it — the broadcast page records circulating clip titles such as "Egyptian Military Planes Were Tracking Erika Kirk," "Candace VINDICATED Over Suspicious Egyptian Plane," and "PLANE TRUTH THAT WILL MAKE YOUR JAW DROP #CHARLIEKIRK," plus Jimmy Dore's August 2026 segment.
  2. It asked for maximum recall and explicitly said not to summarize.
  3. It offered 77 as an approximation and invited any nearby number. The number 77 is not invented — two November and December 2025 posts use it, and they are quoted on the X discussions page.

The answer, in full​

Reproduced verbatim so a reader can weigh it without an intermediary. Formatting is as returned; the repeated "Obsidian Publish" lines are the assistant's own inline source attributions and are left in place, because they are the most important thing on this page.

Based on investigations into the conspiracy theories surrounding the assassination of Charlie Kirk on September 10, 2025, the claim you are referring to involves Egyptian-registered aircraft and is primarily associated with the number 73 (often cited as "73 overlaps" or "73 times"), rather than 77. Obsidian Publish

Here is the detailed breakdown of the claims, the sources pushing them, and the subsequent open-source intelligence (OSINT) and official investigations that addressed them:

The Core Claim: The "Egyptian Plane" and the 73 Overlaps

Following the shooting at Utah Valley University (UVU), a prominent theory circulated online claiming that foreign or state-backed aircraft were involved in the assassination or were conducting long-term surveillance on Charlie and Erika Kirk.

The most prominent iteration of this theory was pushed heavily by political commentator Candace Owens. Obsidian Publish

The Initial Allegation: Owens initially claimed that an "Egyptian Air Force plane" bearing the tail number SU-BTT (and later expanded to include SU-BND) flew out of Provo, Utah, immediately around the time of the shooting. Obsidian Publish

The Surveillance Expansion: This claim soon evolved into a much larger conspiracy theory alleging that these Egyptian-registered planes had "shadowed" or stalked Charlie Kirk, his wife Erika Kirk, or Turning Point USA (TPUSA) events 73 times. Proponents of the theory cross-referenced the flight logs of these Egyptian N-numbers/tail numbers with the dates and airport locations of TPUSA events or the movements of the Kirks' personal travel. Obsidian Publish

The OSINT and Official Debunking

Aviation trackers, OSINT analysts, and federal authorities have heavily scrutinized these claims and found them to be mathematically and factually unsupported. Obsidian Publish

1. The "73 Overlaps" Math Was Flawed

Independent analysis of the flight-tracking data dismantled the "73 times" surveillance claim. Analysts found that approximately 66% of the claimed plane-location overlaps were entirely incorrect. In many instances, the data used to claim the Egyptian aircraft was at the same airport as a TPUSA event or Erika Kirk actually placed the aircraft on a completely different continent at the time. The "overlaps" relied heavily on manipulated or misread public flight data. Obsidian Publish

2. The Provo Airport Timeline Error

The foundational claim that the Egyptian plane (SU-BTT) fled Provo right after the shooting was debunked due to a basic time zone error. The Egyptian plane did depart from Provo's general-aviation airport, but it left at approximately 7:00 a.m. local time — more than five hours before the shooting occurred at 12:23 p.m. Analysts pointed out that Owens and others misread UTC (Coordinated Universal Time) on the flight logs as local "Utah time," artificially aligning the plane's departure with the murder. Obsidian Publish

3. Erika Kirk's Response

The persistent spread of the stalking theories prompted Charlie Kirk's widow, Erika Kirk, to publicly intervene. She directly and publicly told Candace Owens to stop pushing the narrative that she and her husband were being shadowed by these planes. Obsidian Publish

Context: The Broader "Plane" Conspiracy Ecosystem

The "Egyptian Plane" theory is just one of three major aircraft-related conspiracy theories that emerged due to UVU's close proximity (about 5 miles) to Provo's general-aviation airport, which sees routine private, military, and government traffic. The other two prominently debunked claims include: Obsidian Publish

The "Fleeing Jet" (N888KG): A theory claimed a private Bombardier Challenger 300 jet "turned off its transponder" and fled Provo immediately after the shooting. The aircraft actually belongs to Utah businessman Derek Maxfield. FBI Director Kash Patel and DOT Secretary Sean Duffy confirmed that the FAA never lost radar contact. The "turned off transponder" was simply a routine ADS-B reception dead zone over the mountainous terrain near Page, Arizona. Obsidian Publish

The "HADES Spy Plane" (N1098L): A claim that a military ISR (Intelligence, Surveillance, Reconnaissance) jet flew 204 feet over the murder scene. Flight data confirmed the Leidos-operated Army training jet was actually on a routine morning run from El Paso, Texas, to Kalispell, Montana, and was nowhere near Utah at 12:23 p.m. Obsidian Publish

The sourcing audit — twelve citations, one source​

Every substantive assertion in that answer carries the same citation: "Obsidian Publish." That is not a news outlet, an aviation authority, an ADS-B provider, a court filing, or a federal statement. It is the publishing feature of a personal note-taking application — a public web page generated from somebody's private notes.

The assistant pulled a single wiki-style note and rendered it as twelve separately-cited findings. That is exactly the pattern the press coverage page documents one layer down, where twelve bylines across Sportskeeda, IBTimes, Factually, the Economic Times, the Times of India, the Hindustan Times, Document and the Daily Wire all turn out to be re-narrations of one broadcast. Twelve citations that resolve to one page is one source, not twelve.

What the answer citesWhat that isIndependent verification it represents
Obsidian Publish ×12One public note pageNone.
ADS-B history pulled and checkedNot presentNone.
A named OSINT analystNot present — "aviation trackers" and "analysts" are unnamedNone.
A named federal document or statementOnly "FBI Director Kash Patel and DOT Secretary Sean Duffy" in the N888KG paragraph, undated and unquotedNot checkable as given.
A YouTube or podcast episodeNot one, despite the question asking for them by nameNone.

The video and podcast layer — the thing the question actually asked for — came back empty. Not "we searched and found little." Nothing was returned from it at all. That is a real gap and it is worth naming: the layer where this claim reached the most people is the layer the assistant indexed least. This directory has to build that layer itself, and the broadcast page's video section is where it starts.

Where the answer is checkably wrong​

This is the part that decides how much weight the rest of it carries.

N1098L "was nowhere near Utah"​

The answer states that the HADES aircraft "was actually on a routine morning run from El Paso, Texas, to Kalispell, Montana, and was nowhere near Utah at 12:23 p.m."

The El Paso to Kalispell routing is correct. "Nowhere near Utah" is not. This site's own aircraft page, N1098L, documents the leg as: departed Biggs Army Airfield (KBIF), El Paso, at approximately 07:48 MDT, logged into Glacier Park International (KGPI), Kalispell, at approximately 10:38 MDT — and the Utah low passes fall along that corridor. The widely-shared investigator description has the aircraft descending over Orem, then repeating the manoeuvre later that morning.

The two facts are not alternatives. The Utah passes happened on the El Paso-to-Kalispell leg. An answer that offers the routing as proof the aircraft was not there has substituted the endpoints of a flight for its track.

The separate question of what those passes were remains genuinely open and is argued in both directions on the N1098L page — routine drone-retrieval training on one side, ISR tasking on the other, with the airframe-configuration dispute in between. This page takes no position on that. It records only that the specific sentence "nowhere near Utah" does not survive the flight record.

The time-zone correction is presented as a debunk of a claim that was publicly corrected ten months earlier​

The answer presents the UTC-versus-local error as a finding that "debunked" the departure claim. The correction is real and this site carries it. Brick Suit caught it on the morning of 12 October 2025; Candace Owens stood corrected the same day, on air and in posts — the broadcast page logs the ~12 October show as the one carrying "the time-zone correction to the departure time that critics have cited ever since."

A correction the claimant made herself, publicly, on day one, is not a later debunking by "analysts." What the correction actually removed is the narrow "wheels-up after the shot" framing. It removed nothing else — not the six days on the ground, not the second aircraft, not the transponder cycles, not the multi-year tally.

The same daylight-saving trap has caught commentators on both sides of this case: Arizona stays on Mountain Standard Time year-round while Utah in September is on Mountain Daylight Time, which is the one-hour offset the N888KG owner's statement spells out explicitly. It is the single most common source of bogus timing claims in this entire investigation, in both directions.

"Debunked" is doing work the cited evidence does not support​

The answer's own body describes the 66 percent figure as an audit of a spreadsheet — of the published list. An audit that finds rows in a list to be wrong is a finding about that list. It is not a finding about whether a foreign state VIP aircraft sat at a small Utah municipal field for the six days before the assassination. That fact is not in the audited spreadsheet's disputed rows. It is not disputed by anybody, including the auditors.

The number — 77, 73, and everything between​

The answer opens by correcting the questioner's 77 to 73. The correction is partly right and mostly incomplete.

73 is the headline figure, from Owens's team, and it is in the master investigation file as "Egyption Planes had 73 overlaps with Erika. Only ~23 with Charlie." But 73 is one of at least eight published figures, and this directory's rule is that the disagreement is itself the finding — it is never averaged and never silently reconciled:

FigureWho published itWhat it counts
77@Thebasilisk79 (29 Nov 2025); @sgtd33 (10 Dec 2025)Egyptian planes intersecting Erika and Charlie 77 times over 44 months
73 / ~23Owens team; the investigation file73 with Erika, only about 23 with Charlie
73–77Grok-on-X, 22 Nov 2025The only assistant reply in the record that uses the band including 77
72@JustTheTweets17, 18 Nov 2025"72 times those exact planes followed Erika Kirk"
70+ / around 70Shadow of Ezra; David Nino Rodriguez; later restatementsRounded
68 / 29Morgan Ariel, 17 Nov 2025Blue and yellow jets together, 2022–Sept 2025; 29 also including Charlie
65–75Liz Wheeler's paraphraseSame spreadsheet
1Liz WheelerSame-airport, same-day rule applied

So 77 was not a mistake to be corrected away. It is a figure two accounts published, and Grok-on-X's earliest reply in this record uses 73–77 as a range. The honest answer to "was it 77?" is: 77 is in the record, 73 is the most-repeated, and no dated checkable table has ever been published behind any of them.

What the answer got right, with the attribution restored​

Several of the answer's figures are real. What it stripped out was who said them, which is the difference between a finding and a claim.

The answer saysThe record saysWhere it is on this site
"Approximately 66% of the claimed overlaps were entirely incorrect"KanekoaTheGreat, an X account, published the audit — 66 percent of plane locations wrong, 60 percent on the wrong continent. It is one researcher's audit of one spreadsheet, and it has never been published as a checkable table either. Other counts: @CBarrett47 (50 of 70), @truecrimejes (70 percent).X discussions
"Independent analysis... analysts... aviation trackers"Unnamed in the answer. Named in the record: Kanekoa, Liz Wheeler, Brick Suit, @CBarrett47, @truecrimejes, Glamhamradio, John Cullen.X discussions
SU-BTT, later expanded to SU-BNDCorrect — and incomplete. The fleet in this record is SU-BTT, SU-BND, SU-BTU, SU-BTV and SU-BGM — five tails, not two.Provo
Left "approximately 7:00 a.m. local"The published departure times are 07:08 MT in the investigation file and 07:14 in the flight record. The one-minute-scale dispute is unresolved; the hour is not in dispute.Provo
Shooting at 12:23 p.m.Matches the site's day-of record.Sept 10 flight timeline
UVU "about 5 miles" from Provo airportConsistent — the N888KG page puts it at a 10–12 minute drive.N888KG
Window: long-term surveillance of Charlie and ErikaThe record dates the claimed window 2022 through September 2025, which is closer to three years than to the "18 months" the claim is often titled with. That range dispute is unresolved and is stated as a range, never picked.Following overview
Cross-referencing flight logs against TPUSA event dates and Kirk travelCorrect description of the method — and the method's weak point is the Kirk side, not the plane side.Erika flight logs erased

Erika Kirk's response — what the answer says, and what the record holds​

The answer states that Erika Kirk "directly and publicly told Candace Owens to stop pushing the narrative." It gives no date, no venue, and no quote.

The record on this site is more specific, and it is not quite that sentence:

  • 10 December 2025 — Owens bills a show around Erika Kirk going after "conspiracy theorists (read: me)" and around what Erika reportedly told Bari Weiss about the planes.
  • 14 December 2025 — the on-air exchange after Erika Kirk's on-camera response, quoted in full on the broadcast page, including the In-N-Out remark and Owens's reply that "literally NO ONE accused Erika or Charlie of flying on Egyptian planes."
  • A CBS town hall and further press responses, on the press coverage page, disputing the specific trip dates and locations.
  • 15 December 2025 — per Grok-on-X, Owens and Erika Kirk met, and both described the meeting as productive.

Her dispute is real and it is on this site in three places. What the record does not support is a clean "told her to stop" framing: what she disputed was the location claims about herself, and Owens's public response was that a denial of flying aboard the aircraft does not address the allegation that the aircraft turned up where she was.

Her denial still deserves more weight than a denial usually gets, for a structural reason this site states plainly: she is the only person who could produce the itinerary the 73-count was measured against, and the count was built without it. Her flight logs are reported as erased. Nobody on either side is working from her actual travel record — see Erika Flight Logs Erased.

The two aircraft it folded in — and why they stay separate​

The answer bundles the Egyptian fleet, N888KG and N1098L into one "plane conspiracy ecosystem." This directory's standing rule is DO NOT MERGE THE THREADS. These are different aircraft, different operators, different claims and different evidence, and merging them is how all of them get dismissed at once. The assertions are recorded here; the pages that own them are linked.

N888KG — full page:

  • The answer calls it a Bombardier Challenger 300, owned by Utah businessman Derek Maxfield. The site records the registered operator as N888KG LLC, reported in Lehi, Utah, with Maxfield listed as an associated owner in public databases.
  • The answer says FBI Director Kash Patel and DOT Secretary Sean Duffy confirmed the FAA never lost radar contact. Patel is on the site: per fact-check reporting he attributed the ADS-B gap to rural coverage and stated the jet is not part of the official investigation. Sean Duffy does not appear anywhere in this repo's plane record. That attribution is new here, undated, unquoted, and unverified; it is recorded as the answer's claim, not as a finding.
  • The answer says the gap was "a routine ADS-B reception dead zone over the mountainous terrain near Page, Arizona." The primary record is narrower and better: Maxfield's own 11 September 2025 statement says radar services were terminated by mutual agreement between Denver FAA center and the aircraft roughly 10 miles from landing at Page, which he describes as standard practice into a non-towered field. A primary statement beats a paraphrase of it, and the paraphrase drifts.

N1098L — full page:

  • The answer calls it a Leidos-operated Army training jet. The site records a Bombardier Global 6500 operated by LASAI Aviation II LLC, an Army ISR contractor whose control fell under Leidos in 2021, publicly documented as part of the Army's HADES program. "Training jet" is the benign reading of a documented ISR airframe, stated as if it were the registration.
  • The answer's "204 feet" figure matches the altitude circulating in the investigation. Investigator descriptions on the site give roughly 200–300 feet AGL at about 115–150 knots, twice, over Orem.
  • "Nowhere near Utah at 12:23 p.m." is the sentence addressed above, and it is the one factual assertion in the whole answer that this site's primary-record page contradicts outright.

John Cullen — who argues hardest that the Egyptian planes are the less important thread — makes the same split from the opposite direction. His position, quoted on the X discussions page, is that the Egyptian jets were not airborne at 200 feet over the scene and do not deploy UAVs, and that N1098L is the aircraft that matters. That is an argument for keeping the threads apart, which is what this directory does. Both claims get logged. Neither is allowed to swallow the other.

Why this page does not adopt the answer's conclusion​

The answer's organising word is "debunked." Six of its paragraphs are built to land on it. This page records every factual item it contains and declines the conclusion, for reasons that are all on the record above:

  1. Its entire evidentiary base is one note page, cited twelve times. No ADS-B was pulled. No analyst was named. No document was quoted.
  2. One of its factual assertions fails against this site's primary-record page — N1098L was on the corridor that carried it over Utah, not absent from the state.
  3. It presents a self-correction as an external debunking, ten months after the claimant published the correction herself.
  4. It treats an audit of a spreadsheet as an audit of the underlying question. The 66 percent finding is about rows in a published list. The Provo week is not one of the disputed rows.
  5. It answers a different question than the one asked. It was asked for the video and podcast layer and returned none of it.
  6. It corrects 77 to 73 without saying that 77 is published, that 73–77 is a published band, or that no dated list exists behind any figure in the range.

What survives every audit on this site — Kanekoa's, Wheeler's, the press layer's and now the assistant's — is the same narrow core: a foreign state VIP aircraft sat at a small Utah municipal field for the six days before the assassination, departed the morning of it, a second one sat beside it with its transponder cycling, and nobody has published who was aboard either. No answer on this page touches that.

Counterargument​

Required on every page in this directory, and here it is the strongest form of the assistant's case, stated without the framing:

  • The wide tally is genuinely unsupported. No dated, checkable list of 77, 73, 72, 70, 68 or 23 has ever been published by anybody. The spreadsheet that circulated uses a ±3-day window and a 50–100 mile radius, contains duplicated rows that were counted, and reads "No" in its own Charlie Present column on 32 of 35 visible rows. An assistant that calls that unsupported is describing it accurately.
  • The Erika side cannot be reproduced. This repo holds one sourced Erika-at-a-TPUSA-event date for the entire multi-year window the 73-count covers. The assistant's scepticism about the Erika overlaps is the same scepticism this directory applies to itself.
  • The innocent explanations are real and largely documented. Duncan Aviation has held the Egyptian Air Force account since about 1999; Wichita is a Falcon service hub; Wilmington is a customs and fuel stop used on the outbound leg only, 21 times in three years; Omaha is a twenty-minute stop before Lincoln; Cairo is where every rotation begins and ends, which is exactly what "wrong continent" means. Four of the five clustered states resolve to a maintenance or clearance function.
  • The time-zone correction is correct. "Wheels up after the shot" does not survive it, and this site says so on every page that touches the departure.
  • ADS-B has holes and they cut both ways. An absence is not proof of a covert leg; a presence is not proof of intent.
  • No official investigation has linked any of these aircraft to the killing, and no public record establishes who tasked any of them, in either direction.

A page that stopped at the 73 would be propaganda. A page that stopped at "debunked" would also be propaganda. The claim that has to be tested is the same-airport, same-day or one-day-off log at specific fields — which is what the eleven location pages in this directory are for.

What we do not know​

  • What "Obsidian Publish" note the assistant read, who wrote it, when, or what it sourced from. The citation is unresolvable as given.
  • Whether DOT Secretary Sean Duffy ever said anything about N888KG. No date, venue or quote was supplied, and nothing in this repo corroborates it.
  • What the video and podcast layer actually contains, in full. The assistant returned none of it. The broadcast page's video section holds the clip titles this repo has so far, and that list is known to be partial.
  • The dated list behind any figure — 77, 73, 72, 70, 68, 29 or 23. Still unpublished by anyone, on either side.
  • Erika Kirk's actual itinerary for any disputed date. Neither side has published it.
  • The passenger manifests for the Provo week. Never published, never requested in public, by anyone.
  • How the assistants' answers change over time. This is one capture on one date from one assistant. Grok-on-X's parallel replies are catalogued on the X discussions page and they are not identical to this one.

This website's author is @HolonCitizen on X and YouTube/@HolonCitizen. Follow me there.

Interesting​

  • The Provo page is the one location no audit on this page dissolves — 113 continuous days of parked foreign aircraft.
  • Sharm el-Sheikh put SU-BTT beside Air Force One, which removes "some charter operator" from the list of explanations.
  • Minot is where customs actually happened on every Provo-bound leg — and nobody has requested those records.