N888KG Provo Vanish
N888KG is the private jet at the center of one of the most-discussed flight theories on X about the Charlie Kirk assassination. It departed Provo Airport (PVU) — about a 10–12 minute drive from UVU — roughly one hour after Charlie Kirk was shot on September 10, 2025, flew south toward Arizona, lost its ADS-B transponder signal mid-flight for an extended gap, then reappeared and returned to Provo. Commentators call this the "Provo Vanish" (and, in an earlier framing, the "Wendover Vanish"). The aircraft's owner, the FAA, and FBI Director Kash Patel have all stated the gap was routine and that the jet is not part of the official investigation. Both the suspicion and the rebuttals are presented below.
Aircraft identification
- Tail number: N888KG
- Type: Bombardier Challenger 300 (BD-100-1A10) — a white-liveried business jet, per independent flight trackers.
- Registered operator/owner: N888KG LLC (reported registered in Lehi, Utah), with Derek Maxfield listed as an associated owner in some public databases. Commentators further associate the entity with the companies/foundations Komigo and the Saprea foundation (reporting links the owner to Komigo / Saprea addresses), and some note reported Israel connections. Per X commentary, the owners are described as a Mormon (Latter-day Saint) couple based in Utah. Separately, some X posts claim the same owners are large Chabad Lubavitch donors / made Chabad Lubavitch donations; this is an unverified claim circulating on X, is not independently confirmed, and is reported here strictly as an allegation, not as fact. These ownership associations are reported by commentators, are not independently confirmed, and naming the entity here is not an accusation against any individual.
- Departure airport: Provo Airport (PVU), Utah.
- Reported route: Provo → toward Page Municipal Airport (PGA), Arizona → return to Provo. (An earlier, less-documented version of the story named Wendover, a desert airstrip on the Utah/Nevada border; later flight-record reporting points to the Page, AZ routing instead.) A separately reported account circulating on X places the mid-flight ADS-B/radar dropout much farther south, near the Arizona/Mexico border area, before the aircraft reappeared and returned to Provo. Timing and location claims vary by source, and this border-area version is reported alongside — not in place of — the Wendover and Page, AZ accounts above.
Flight history relevant to the case
Times are MDT on September 10, 2025 unless noted. Charlie Kirk was struck at approximately 12:23 PM MDT.
- September 9, 2025 (the day before): Per the investigation notes, "n888kg" spiked in Google Trends searches in Utah — a search of the tail number reportedly occurring before the shooting. This pre-event search interest is flagged as a possible foreknowledge signal, though it is unverified and could have innocent explanations.
- ~1:11–1:20 PM (about 45–60 minutes after the shooting): N888KG departed Provo Airport (PVU), heading southeast toward the Arizona/Nevada border at normal cruise speed.
- ~1:43 PM (about 30–46 minutes into the flight): The aircraft's ADS-B transponder went dark near the northern Arizona border, removing it from public radar for an extended gap (reported as roughly 30 to 50-plus minutes).
- ~1:48 PM: Reported to have landed at Page Municipal Airport (PGA), Arizona, after re-acquiring tracking.
- ~2:30 PM: Reappeared on tracking departing Page (PGA) for the return leg to Provo.
- ~3:06 PM: Returned to Provo (PVU) and landed without incident.
- No public flight plan was associated with the dark leg, which trackers label a "ghost flight."
Note on times: the master investigation notes contain a conflicting evening timestamp (a "~7:12 PM" departure). That is inconsistent with the 12:23 PM shooting and the relative "45 minutes / one hour after" descriptions, so the early-afternoon times above are used as the consistent account. The discrepancy is noted for transparency.
Theories about the aircraft's role
These are open theories advanced by commentators, framed as reported allegations, not established facts. Viral X posts framed the jet as "the plane that took off from the Provo Airport 20 minutes after Kirk's murder" (the stated interval varies post-to-post, from ~20 minutes to about an hour, against the consistent flight-record times above) and circulated under headlines such as "Private Jet N888KG Mysteriously Disappears Off Radar After Charlie Kirk's Assassination," often paired with the question "Where is the shooter?" A recurring framing on X is that the flight was "swept under the rug" — that the suspicious departure timing and transponder behavior were dismissed too quickly and never properly investigated. That characterization is a conspiracy-theory claim and an open question, not a finding; the owner and officials' rebuttals appear in the section below.
- Getaway aircraft — that N888KG may have moved the shooter or related personnel out of the area during the transponder blackout. Analysts note that during a 30–50 minute dark window a Challenger 300 could cover roughly 350–400 nautical miles — enough for a drop-off at a remote airstrip such as Page (PGA) or even Tuba City (TBC) before looping back. This is presented as a calculation of what was possible, not proof of what occurred.
- Covert rendezvous / drop-off — that the dark leg allowed an untraceable meeting or an untracked transfer of passengers or cargo. The aviation analyst MonkeyWerx laid out this version, citing the departure timing, the mid-flight blackout, the lack of a filed plan, and the owner's local Utah ties, while acknowledging the jet's otherwise clean flight history (e.g. prior trips to Cancun in May 2024).
- Foreign-intelligence link — that the reported Saprea/Komigo and alleged Israel connections tie the aircraft to the broader foreign-involvement theory of the case. This rests entirely on unconfirmed ownership associations and is the most speculative thread.
- Chabad Lubavitch / "Tucker" framing — some X posts fold the unverified Chabad Lubavitch donor allegation (see Aircraft identification) into a broader narrative, and reference commentary by Tucker Carlson said to "call out" Chabad-related context around the case. To be clear: this is an X-circulated framing, the donor claim itself is unconfirmed, any attributed remarks are reported allegations and not verified quotes, and nothing here asserts wrongdoing by Tucker Carlson, any donor, or any named living person. It is included only to document the theory as it appears on X.
Owner statement and official response
The page presents the rebuttals alongside the suspicions:
- Owner's explanation: The owner has stated the flight was a prescheduled trip, and that the termination of ATC/ADS-B tracking was standard for flights into and out of non-towered airports in rural areas — not an intentional, illegal transponder shutoff. Some reporting adds that radar services were terminated mutually with the Denver FAA center about 10 miles out from Page (PGA), consistent with normal arrival procedure at a non-towered field.
- Account of who boarded: In a post the owner is reported to have shared on Instagram, the explanation states that no one disembarked at Page, and that seven company employees boarded at Page for the return leg to Provo — countering the claim that the stop was a passenger drop-off for a fleeing shooter.
- Rural-coverage explanation: The owner and officials attribute the tracking gap to poor ADS-B ground-station coverage over rural terrain, where aircraft routinely drop off public trackers, rather than to a deliberately disabled transponder.
- FBI Director Kash Patel: Per fact-check reporting, Patel addressed the flight publicly and attributed the ADS-B gap to rural coverage, not an illegal transponder shutoff.
- Not part of the official investigation: Fact-checks report that N888KG is not part of the official investigation into the assassination.
(Readers weighing these explanations may note that elsewhere in this investigation, commentators have challenged other "prescheduled / routine" claims — such as the paving of the crime-scene area. That context is offered for the reader to judge, not as a contradiction of the owner's specific statement here.)
Why a transponder gap draws scrutiny
ADS-B (Automatic Dependent Surveillance-Broadcast) has been FAA-mandated since 2020 for most US aircraft in controlled airspace; it broadcasts position, altitude, and identity in real time. Intentionally disabling ADS-B mid-flight without authorization is illegal and can carry fines of $25,000 or more, with authorized exceptions generally limited to national-security operations or declared emergencies. The key dispute over N888KG is whether the gap was an intentional shutoff (the conspiracy reading) or a routine coverage dropout over rural terrain near a non-towered field (the owner/FAA/Patel reading). That distinction — not merely the existence of a gap — is what the open questions below try to resolve.
Open questions
- Who is the registered operator and beneficial owner of N888KG, and what are the actual corporate ties to Komigo and the Saprea foundation?
- Who was on board the September 10 flight, both outbound and on the return?
- Was the transponder gap a deliberate shutoff or a genuine coverage dropout — and is there radar or FAA data that settles it?
- What was the aircraft's true track during the dark window, and did it land anywhere other than Page (PGA)?
- Have any FAA enforcement records or inquiries been opened on the ADS-B gap?
- Why did the tail number "n888kg" reportedly trend in Utah Google searches on September 9, the day before the shooting?
The owner's statement, in full and unedited
Everything on this page about "the owner's explanation" traces back to a single document: a statement Derek Maxfield posted to social media on the afternoon of September 11, 2025, the day after the shooting. Summaries of it have been quoted, paraphrased, and argued over for months. The full text is short, it is a primary source, and it is reproduced here verbatim so a reader can weigh it without an intermediary. It ran across two images; the first carries a Facebook post header showing the account name, a verified badge, a "1m" timestamp and a public-audience globe icon, with the word "Shelaine" rendered as a blue user tag at the start.
Shelaine and I join our community, our state and our nation in mourning the death of Charlie Kirk and we pray for his family and loved ones during this difficult and tragic time. His death and the way it occurred was both horrifying and senseless. We pray that the extensive efforts by law enforcement to locate Mr. Kirk's killer will be swift and successful.
As often happens, unfortunately, in the wake of such terrifying and public events, a variety of baseless theories and suspicions around Mr. Krik's murder immediately took hold on social media, including one that has unfairly impacted our family. To set the record straight, we provide the following facts.
Yesterday, at approximately 1:20 pm MT a private aircraft owned by one of our companies, with tail # N888KG, departed the Provo Airport (PVU) for Page, AZ, pursuant to a prescheduled flight plan. Occupants at take-off included two pilots and no passengers. N888KG arrived at the Page, AZ Airport (PGA) at approximately 1:55 pm MT, 12:55 pm local time. Upon arrival, I, Derek Maxfield, boarded N888KG, along with 7 additional passengers for the return trip to PVU. N888KG departed PGA at approximately 1:40 pm local time (2:40 pm MT) and arrived at PVU at approximately 3:15 pm MT. Radar services with air traffic control were terminated in mutual agreement between Denver FAA center and N888KG approximately 10 miles from landing at PGA, which is consistent with generally accepted standard practice when flying in and out of non-towered airports like PGA. N888KG pilots followed all FAA requirements and protocols, tower directions and the predetermined flight plan. This roundtrip was made at my request and solely for my purposes. Any suggestion that the flights by N888KG yesterday are in any way connected to the tragic shooting of Mr. Kirk is inaccurate, false and without any credible basis of any kind. To our knowledge, no one associated with yesterday's flights by N888KG has been contacted by law enforcement for any reason.
We ask that the focus remain on praying for and supporting those who have been deeply impacted by yesterday's events and on the critical efforts of law enforcement to bring Mr. Kirk's murderer to justice.
("Krik's" is spelled that way in the original.)
Three things in the statement are more specific than the paraphrases of it:
- It gives times to the minute — five of them — which makes it falsifiable against tracking data rather than merely reassuring. That is the opposite of what a vague denial looks like.
- It states the radar termination point explicitly: "approximately 10 miles from landing at PGA," by "mutual agreement between Denver FAA center and N888KG." Radar service termination on approach to a non-towered field is ordinary; a controller releases the aircraft because there is no tower to hand it to. This is a different thing from a transponder being switched off, and the statement is careful to describe the former.
- It says the aircraft departed Provo with two pilots and no passengers. If true, the outbound leg — the one that departed shortly after the shooting and drew all the attention — carried nobody who could have been fleeing anything.
The times do not line up, and that is worth stating plainly
The owner's statement and the flight-tracking record are the two accounts of the same afternoon, and they disagree on every leg. Neither is a small discrepancy of rounding.
| Event | Owner's statement (Sept 11) | FlightRadar24, as reported by People |
|---|---|---|
| Departs Provo (PVU) | ~1:20 pm MT | ~1:11 pm local |
| ADS-B tracking lost | (described only as radar service terminated ~10 mi from PGA) | ~1:43 pm, near the northern Arizona border |
| Arrives Page (PGA) | ~1:55 pm MT (12:55 pm local) | (not stated — aircraft was off tracking) |
| Departs Page (PGA) | 1:40 pm local = 2:40 pm MT | tracking reappeared "shortly after 2:30 pm" as it departed PGA |
| Arrives back at Provo | ~3:15 pm MT | 3:06 pm |
The gaps are roughly nine minutes on departure, ten minutes on the return, and an ambiguous window on the Page departure. They are small, but they run in a consistent direction — the tracker has the aircraft moving earlier than the owner does at both ends.
There is also a time-zone trap buried in this comparison, and it has caught commentators on both sides of this case. Page, Arizona is on Mountain Standard Time year-round because Arizona does not observe daylight saving, while Provo in September is on Mountain Daylight Time. That is the one-hour offset the owner's statement is carefully spelling out when it writes "1:55 pm MT, 12:55 pm local time." Anyone re-deriving these timings from a tracker must handle that offset, and several published attempts have not. The same daylight-saving error — assuming UTC−7 for Utah on September 10 when the correct offset was UTC−6 — is the error later conceded and corrected in the SU-BTT analysis, and it is the single most common source of bogus "impossible timing" claims across this entire investigation.
None of this resolves whether the gap was routine. It does mean that anyone citing "the flight records" against "the owner's statement" is comparing two accounts that were never reconciled in public.
The aircraft's technical identity
A tracker record card circulated on X, credited © KnightHammer Aviation, gives the airframe identity independent of the registration:
| Field | Value |
|---|---|
| Aircraft | Bombardier Challenger 300 |
| Type code | CL30 |
| Serial number | 20402 |
| Age at capture | 12 years (i.e. a 2013 airframe) |
| Mode S / ICAO hex | AC3C75 |
| Airline | Private owner |
| Operator | N/A |
| Country of registration | United States |
The Mode S code AC3C75 is the durable identifier. It is what allows a claim about this aircraft to be checked against raw ADS-B archives even if the registration were later changed or the tail re-marked, and it is the field that should be quoted in any future audit of the September 10 track.
The aircraft is blocked from public tracking — and that is a formal FAA program, not a cover-up
The most consequential detail in the original X thread has been widely repeated without being understood. A screenshot from FlightAware included in the thread shows:
N888KG - N888KG LLC (LEHI UT)
…8KG) is not available for public tracking per request from th…
That's my airplane! How do I track my airplane on FlightAware?
…aircraft owner/operators with secure access to their own flight data. Cont…
A second capture in the same set — the KnightHammer record card above — shows the flight-history panel returning "No flights found." The X poster's caption on that image read simply: "And they are a ghost as well."
This needs to be stated precisely, because it is the load-bearing fact under the "ghost plane" framing:
- Blocking is a formal, legal, opt-in program. Under the FAA's LADD (Limiting Aircraft Data Displayed) program — and, since the 2024 FAA reauthorisation, an expanded right for private owners to request that their registration data be withheld from public display — an owner may request that their aircraft be suppressed from the public feeds that FlightAware, Flightradar24 and similar services publish. Thousands of business aircraft are enrolled. It is a privacy request filed with the government, not a technical evasion.
- Blocking does not turn off the transponder. A LADD-blocked aircraft still broadcasts ADS-B, is still tracked by ATC, and is still visible to any receiver on the ground — which is exactly why ADS-B Exchange, which by policy does not honour blocking requests, still carries such aircraft.
- Therefore "No flights found" on FlightAware is not evidence of anything about September 10. It is evidence that the owner filed a privacy request at some point. It would return the same result for any date.
That distinction cuts both ways, and honesty requires both halves. It defuses the "ghost plane" rhetoric. But it also means the public record for this aircraft is thin by the owner's own election, and that the only way to check the September 10 timings against a primary source is through ADS-B Exchange's unfiltered archive or through an FAA records request — neither of which any of the circulating posts appears to have done.
The original X post that started it
The thread that launched the entire N888KG discussion was posted by @stellarman22 on the evening of September 10, 2025 — within hours of the shooting. Its text in full:
🚨 A private jet under the tail number N888KG left Provo airport an hour after the shooting
Suspiciously 30 mins into the flight it drops off of ADS-B Illegally and reappears headed back to Provo approx. an hour later
Why did this plane turn off its radar? Where is the shooter?
The post carried four images: two ADS-B Exchange map captures with red annotations, the FlightAware blocking notice quoted above, and a photograph of a white Challenger 300 with a dark blue tail on an apron. The red annotations on the maps read, verbatim:
N888KG - Provo Regional Airport is 5 miles from Utah Valley University
Times in UTC Assassination: 18:10 Take off: 19:12 Illegally turns off ADS-B radar: 19:44
and on the second map:
20:30 UTC - Reappears on ADS-B radar
Converting those UTC figures at UTC−6 (Utah was on Mountain Daylight Time on September 10):
| Annotation | UTC | Utah local (MDT) |
|---|---|---|
| "Assassination" | 18:10 | 12:10 pm |
| Take off | 19:12 | 1:12 pm |
| ADS-B lost | 19:44 | 1:44 pm |
| Reappears | 20:30 | 2:30 pm |
Those converted times land within a minute or two of the FlightRadar24 figures reported by People — 1:11 pm departure, 1:43 pm signal loss, reappearance shortly after 2:30 pm — which is a genuine point in the original poster's favour: the underlying timings he published were sound. The elapsed gap is roughly 46 minutes.
Two of his characterisations, however, do not hold:
- "Illegally." The post asserts illegality as fact. The owner's account, and the ordinary operation of radar-service termination inbound to a non-towered field, both describe a lawful sequence. Nothing published establishes an intentional unauthorised shutoff, which is what would be illegal.
- The distance figure. The annotation says Provo airport "is 5 miles from Utah Valley University." Elsewhere on this page the figure is given as a 10–12 minute drive, and People described PVU as "less than 15 minutes drive from UVU's campus." All three are compatible; five straight-line miles is the shortest of them. The point is only that the number cited in the viral graphic is a straight-line distance, not a driving one.
The Tuba City extension of the theory
A follow-on post the same evening, from @i_aver, pushed the geography further south:
Flight path leads past Page, AZ to super-remote "Tuba City Airport". Perfect for your quick landing and hit team transfer needs.
The attached images showed the same annotated ADS-B Exchange track alongside four Google Maps panels: a listing card for Tuba City Airport (Arizona 86045, phone (800) 992-7433, with a Google "popular times" bar chart), a regional map with a heavy black arrow drawn from the Provo/Salt Lake City area down to a red pin on Tuba City, and a satellite view of a single asphalt strip running northwest-to-southeast through bare desert. The tracker's status bar in that capture is stamped "Date: 2023-09-10, Time: 19:44:00 Z" — the year is wrong in the graphic; the underlying event is September 10, 2025.
Tuba City Airport (TBC) is a real, small, publicly-owned field on the Navajo Nation, roughly 55 miles southeast of Page. The argument being made is one of capability, not evidence: that a remote unattended strip within the dark window's range would be a suitable transfer point. Nothing in the post places the aircraft there. The track shown runs past Tuba City toward Page, which is where the owner's statement says it landed and where tracking re-acquired it on departure.
Treat this as what it is — a map exercise identifying what would have been possible during a 46-minute coverage gap, offered without any positive evidence that it happened.
What People reported, and what it did not
The mainstream account most often cited on this topic is People magazine's "Owner of Plane at Center of Charlie Kirk Shooter Conspiracy Theory Speaks Out," by Colson Thayer, updated September 12, 2025, 10:25 AM EDT. Its reporting is the source of the FlightRadar24 timings in the comparison table above, and it is the source of the widely-repeated line that the plane's FAA registration "shares an address with Maxfield's company Komigo."
Two limits on that article are worth recording, because it is routinely cited as though it settled the matter:
- Its flight timings come from FlightRadar24, a public tracker — the same class of source as the X posts it is reporting on. It did not obtain FAA radar data, ATC tapes, or the flight plan.
- It closes by noting that neither the FBI's Salt Lake City office nor Provo Airport responded to its request for comment. So the two bodies that could confirm or refute the routine-flight account had not done so as of publication.
The article also describes the aircraft, correctly, as departing "about an hour after the shooting, which took place around 12 p.m. local time," and describes Provo (PVU) as "a public-use regional airfield less than 15 minutes drive from UVU's campus."
What this aircraft would cost to buy new today
- Type (FAA-confirmed): Bombardier BD-100-1A10 (Challenger 300), built 2013, serial 20402
- Registered owner: N888KG LLC (Lehi UT)
- Still built today? No — Challenger 300/350 succeeded by Challenger 3500
- Priced against: Bombardier Challenger 3500
- Cost to buy new today: ~$26.7 million
Challenger 3500 is the direct in-production successor at ~$26.7M list. The Challenger 300 listed around $20-30M when new.
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
N888KG is the best-archived aircraft page in this fleet. The Internet Archive holds 22 captures of its tracking pages, and 70 flight rows were recovered off them — more recovered published history than any other aircraft in this investigation. Nothing was found to be missing from any tracking site.
| Source | What it holds for N888KG |
|---|---|
adsb.lol globe_history | 4 days of track, 7 September 2025 to 9 October 2025 |
| globe.airplanes.live | 12 days of track, 7 September 2025 to 28 May 2026 |
| ADS-B Exchange monthly sample | 13 days, 1 March 2022 to 1 February 2026 |
| FlightRadar24 page | HTTP 200 in a browser on 24 August 2026; 0 history rows on the free seven-day tier because the aircraft had not flown in the previous seven days; older history paywalled |
| Internet Archive | 22 page snapshots held — 13 of FlightRadar24, 9 of FlightAware; 70 flight rows recovered off them |
The FlightAware captures reach back to July 2011, which is why the recovered total is so much larger here than elsewhere. That depth is an accident of what the Archive happened to crawl, not a finding about the aircraft.
No tracking site was found to have removed this aircraft's page. Our scripts recorded HTTP 403 from FlightRadar24, RadarBox and Planespotters, but the same script recorded the identical 403 for five unrelated control aircraft, so those are robot blocks and establish nothing about this tail: What A 403 Actually Means. FlightAware and ADS-B Exchange serve scripts normally and returned HTTP 200 for N888KG.
Where a day is absent from an archive, that means the volunteer receiver network heard nothing on that day. It does not mean the aircraft did not fly, and it does not mean a transponder was off. Both free daily archives begin in 2023, so no 2022 date is testable at all.
Raw payloads are saved at site/docs/Planes/N888KG/data/recovered/, with the source named in every
filename and a .meta.json sidecar per file recording the source, URL, HTTP status, byte count and
date.
Method and fleet-wide results: Flight Data Recovery · Per-Aircraft Recovery Status
Interesting In This Area
- It left Provo about an hour after the shooting and later returned.
- Reported Israel ownership ties are how it enters that thread.
- The owner, the FAA and the bureau call the gap routine, unlike the armada tails.
- ADS-B gaps are ordinary, which the section index is careful to state.
Interesting In Other Areas
- Kash Patel briefings are where the bureau addressed this directly.
- The Israel investigation index carries the ownership-tie version.
- Provo Municipal is the departure field for this and several others.
- Candace Owens put most of these tails into wide circulation.
Other Pages In This Section
The weakest-sourced aircraft entry on the site: a turboprop reportedly seen circling near campus, with no tail number and no flight track at all. It is catalogued so the claim is logged and clearly caveated.
Read thisA C-37A Gulfstream tracked into Fort Huachuca two days before the shooting, tied by an anonymous tipster to a reported meeting of about twelve lieutenant colonels. The flight is public record; the meeting is not.
Read thisThe 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
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 thisElsewhere In The Investigation
The "Valhalla" remark, the repeated "33 hours," and a roof clip one commentator compared to 1973 VHS. Counted from the shot, 33 hours lands hours after the reported 6:25 PM Miranda time.
Read thisThe working memo for this whole section, sorted into a motive layer, an execution-adjacent layer and a response layer. Read it first if you want the map before the individual claims.
Read this
The airfield ten minutes from campus, where a badge-access list was reportedly updated the day after the shooting and an Egypt-registered Falcon had sat since September 4. Reported questions, not established facts.
Read this
The single largest independent engine driving this investigation into public view. Several of the document trails cited across this site surfaced first on her episodes.
Read thisSources
- MonkeyWerx aviation-tracking analysis identifying N888KG, its Provo departure, and the mid-flight ADS-B blackout; includes his call for the FBI (Kash Patel and Dan Bongino) to seize the aircraft and interview the pilots/owner.
- MJTruthUltra video analysis of the flight (reported to have drawn millions of views) walking through the departure timing, the radar blackout, and the distances covered during the dark leg — one of the posts that drove the "vanish" framing across X.
- Public ADS-B Exchange and similar flight-tracking history and screenshots circulated by independent investigators tracking post-event movements.
- Fact-check reporting attributing the tracking gap to rural coverage and stating N888KG is not part of the official investigation, including remarks by FBI Director Kash Patel.
- Investigation notes recording the September 9 Google Trends search spike for the tail number in Utah.
Laws (Charlie Kirk)
- The registered owner and passenger manifest of N888KG, who (if anyone) authorized any transponder interruption, and any FAA enforcement records for the ADS-B gap are exactly the kinds of records that the Charlie Kirk Investigation Laws could force into the open.
Citizen Investigator Claims on X
(Aircraft OSINT and attributed claims — not findings that any pilot, passenger, or official ordered or carried out the assassination.)
- Citizen OSINT tracks N-numbers near TPUSA events, Provo FBO activity, and foreign VIP tails; flight logs ≠ intent.
- Competing tallies exist for “shadowing” Charlie vs Erika; debunk and counter-debunk cycles continue on X.
- This page’s focus (N888KG Provo Vanish) 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
- The aircraft making low passes near UVU came from a Fort Bliss Army airfield.
- The county reportedly found zero bodycam covering the surrender.
- The state's biggest message exhibit came from a roommate's phone, extracted by an Israeli firm.
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 — N888KG — 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 — N888KG — volunteer-fed, unfiltered tracker that does not honor LADD, so it often shows blocked aircraft and tracks the filtered sites leave out.
Images
