Skip to main content
← Following

Provo (KPVU) — April 2024 to September 2025

All five Egyptian-registered aircraft in this investigation — SU-BTT, SU-BND, SU-BTU, SU-BTV and SU-BGM — landed at Provo Municipal Airport, a regional field seven miles from Utah Valley University, across a seventeen-month window ending three days after Charlie Kirk was killed there. For 113 consecutive days of that window, at least one of them was continuously parked on the ramp. This is the one location in the shadowing claim that survives the sceptics' own line-by-line audit intact.

Everything below is drawn from Flightradar24 flight-history exports compiled by @WeAre_TheElite and from a researcher timeline circulated on X. It is public ADS-B data read by independent researchers. It is not an official record, and no manifest for any of these flights has ever been published.

The airport​

NameProvo Municipal Airport
IdentifiersKPVU (ICAO) / PVU (IATA)
City / StateProvo, Utah County, Utah
ClassPublic-use regional / municipal airport
Field elevation~4,500 ft MSL
Distance to UVU~5 miles straight line, described by People as "less than 15 minutes drive from UVU's campus"
MRO on fieldDuncan Aviation — full-service airframe, engine, avionics, paint and interior facility

How unusual is a foreign government jet here​

Genuinely unusual, and the reason has nothing to do with runway length. Provo has a runway that will take a Falcon 7X or a Gulfstream IV without difficulty. What Provo does not have is the thing a foreign state aircraft normally needs: it is not a routine international port of entry for this class of movement. Diplomatic and state aircraft ordinarily arrive at major hubs where customs, protocol and handling infrastructure exist.

The flight record shows how that was solved, and the answer is the most-overlooked fact about this whole cluster: every one of these aircraft entered the United States somewhere else and reached Provo on a domestic leg. Four of the five came in via Minot, North Dakota; one came via Salt Lake City. US customs processing for every person aboard happened at the entry field, not at Provo.

So the honest form of the "why a small airport" question is not how did they clear customs there — they didn't — but why choose a Utah regional field as the domestic destination. And there the ordinary answer is on the airport diagram: Duncan Aviation runs an MRO on the field, and the same company has held the Egyptian Air Force's maintenance account since 1999.

The foreign side — every arrival and departure​

AircraftTypeHexArrivedEntered US viaDepartedDays on ground
SU-BNDGulfstream 4SP01003E19 Apr 2024Goose Bay → Salt Lake City12 Jul 2024 (reported)~84
SU-BTTFalcon 7X0101D323 Apr 2024Paris → Williston, ND (XWA)28 Apr 20245
SU-BGMGulfstream IV010070(on field by 10 Apr 2025)—16 Apr 2025 → Goose Bay≥6
SU-BTUFalcon 7X0101D08 Apr 2025Paris → Minot (MOT)14 Apr 2025 → Wilmington6
SU-BNDGulfstream 4SP01003E23 May 2025Paris → Goose Bay → Minot13 Sep 2025 → Goose Bay113
SU-BTVFalcon 7X0101D127 May 2025Paris → Minot (MOT)2 Jun 2025 → Wilmington6
SU-BTTFalcon 7X0101D34 Sep 2025Paris → Minot (MOT)10 Sep 2025, 07:14 → Wilmington6

Three things in that table that are new​

1. Two Egyptian jets were parked here simultaneously in April 2025. SU-BTU was on the ground 8–14 April. SU-BGM flew a Provo→Provo sortie on 10 April and did not leave Utah until 16 April. Five months before the assassination, two foreign-registered jets shared this ramp for the better part of a week. That has not previously been set out anywhere on this site, and it cuts hard in both directions — it deepens the Provo relationship, and it makes the September stay look like the fifth in a series rather than a singular event.

2. From 23 May to 13 September 2025 — 113 days — a foreign-registered jet was continuously parked here. SU-BND arrived on 23 May and did not leave until 13 September. Every other arrival in that period, including SU-BTT's September stay, happened at an airport where SU-BND was already sitting.

3. In those 113 days, SU-BND flew exactly twice. Both were Provo→Provo round-robins that landed where they started: one on 10 June (no duration logged) and one on 5 September, lasting 1 hour 8 minutes — five days before the assassination. A jet that sits for four months and flies twice is not conducting operations. But a 68-minute closed-loop sortie by an aircraft that had not moved in three months is also not nothing, and it is the single flight on this page that nobody has adequately explained.

A fourth point, which is the counter to the third. SU-BGM flew the same signature on 10 April 2025 — a 55-minute Provo→Provo round-robin. Two different Egyptian jets, five months apart, each flew exactly one closed-loop local flight out of Provo. The ordinary explanation for both is a post-maintenance functional check flight, which is what an aircraft does after a heavy inspection before it is released: roughly an hour, and back to the shop that did the work. Two completed maintenance visits produce exactly two of these. If the 5 September flight is treated as anomalous, consistency requires treating the 10 April one the same way — and an April closed-loop five months before the event is very hard to fit into any narrative about the assassination.

The Kirk / TPUSA side​

This is the weakest half of the pairing and it should be read that way. The event dates below come from a researcher-compiled timeline circulated on X; almost none carry a citation.

DateKirk / TPUSA eventNearest aircraft movementGap
23 Apr 2024Charlie Kirk "Prove Me Wrong" event at the University of Utah, Salt Lake CitySU-BTT lands at Provo, 12:13 pmSame day
19 Apr 2024—SU-BND arrives Provo, 3:33 pm—
28 Apr 2024—SU-BTT departs Provo for Wilmington—
5 Apr 2023TPUSA Faith event, Salt Lake City (Kirk discusses gun deaths)no aircraft at Provo—
23 May 2025—SU-BND lands Provo 2:38 pm. The timeline compiler's own note: "This looks like a legitimate maintenance stop"—
5–6 Sep 2025Charlie Kirk speaking at the Build Up Korea conference, Seoul, South KoreaSU-BND flies its 68-minute Provo round-robin, 5 SepDifferent continent
10 Sep 2025Charlie Kirk is shot at Utah Valley University, ~12:23 pmSU-BTT departs Provo 07:14 am, ~5 hours earlier. SU-BND on the ground, transponder reported active, no takeoff.Same day

The pairing that actually holds, and the one that does not​

23 April 2024 is the strongest documented pairing anywhere in the pre-2025 record. Charlie Kirk was at the University of Utah in Salt Lake City doing a Prove Me Wrong event. SU-BTT landed at Provo — 45 miles south — at 12:13 pm the same day, having flown Cairo → Paris → Williston, North Dakota → Provo. Same day, same metropolitan region, documented on both sides. The independent audit marks this flight accurate (its index 26: "Acc 4/22-23. Williston code XWA").

The September 2025 pairing does not hold in the way it is usually presented. During the six days SU-BTT sat at Provo, Charlie Kirk was in Seoul, South Korea on 5 and 6 September, per the same researcher timeline that supplies the April pairing. Erika Kirk has reportedly said she stayed home in Arizona on 10 September. Neither Kirk is documented at Provo at any point during the fleet's September presence. What is documented is that an event was scheduled at UVU on 10 September and that the aircraft was on the field for six days beforehand and left that morning.

That is a real fact and it does not need inflating. It is also not the same claim as "the plane was following him."

The overlap table​

One row per claimed pairing at this location. Both timestamps stated where known.

DateForeign tailForeign movement + timeKirk / TPUSA side + timeGapArrived fromDeparted toTransponderConfidence
19 Apr 2024SU-BNDArrives Provo 3:33 pm(none identified)—Paris → Goose Bay → SLC—onFlight leg audited accurate; no Kirk pairing
23 Apr 2024SU-BTTArrives Provo 12:13 pmKirk at U. of Utah, SLC, same daySame dayParis → Williston (XWA)—onAudited accurate. Strongest pre-2025 pairing
28 Apr 2024SU-BTTDeparts Provo———Wilmington → Cairo 30 ApronAudited accurate
8–14 Apr 2025SU-BTUArrives 8 Apr, departs 14 Apr(none identified)—Paris → MinotWilmington → CairoonExport only; no Kirk pairing offered
10–16 Apr 2025SU-BGMProvo→Provo 55 min on 10 Apr; departs 16 Apr(none identified)——Goose Bay → ParisonExport only; no Kirk pairing offered
23 May 2025SU-BNDArrives Provo 2:38 pm(none identified)—Paris → Goose Bay → Minot—onAudited accurate. Compiler notes "legitimate maintenance stop"
27 May – 2 Jun 2025SU-BTV (disputed — see below)Arrives 27 May, departs 2 Jun(none identified)—Paris → MinotWilmington → CairoonTail number disputed
10 Jun 2025SU-BNDProvo→Provo, no duration logged————gap in trackUnexplained
5 Sep 2025SU-BNDProvo→Provo, 1 h 08 mKirk in Seoul, Korea 5–6 SepDifferent continent——onUnexplained sortie
4 Sep 2025SU-BTTArrives Provo 12:46 pmUVU event scheduled 10 Sep6 days beforeParis → Minot 11:03 am—onAudited accurate
10 Sep 2025SU-BTTDeparts Provo 07:14 amKirk shot at UVU ~12:23 pmSame day, ~5 h before—Wilmington (ILG)onAudited accurate (origin corrected from "Paris" to Provo)
10 Sep 2025SU-BNDOn ground. Transponder reported active. No takeoff.SameSame day——on, stationaryReported
13 Sep 2025SU-BNDDeparts Provo 12:57 pm3 days after——Goose Bay → Paris → CairoonAudited accurate

The 27 May tail-number dispute​

The 27 May – 2 June 2025 row is attributed to two different aircraft by two different sources, and something substantial rides on which is right.

  • The Flightradar24 export puts SU-BTV at Provo from 27 May to 2 June, and puts SU-BTU at Provo six weeks earlier, 8–14 April.
  • Candace Owens's August 2026 segment puts SU-BTU at Provo on 27 May, departing 2 June, and builds a chain of inference on it: a name allegedly in use aboard the 10 September flight was, she says, also in Provo in late May aboard SU-BTU — which she then links to the Egyptian presidential fleet via a claimed record of President el-Sisi flying aboard SU-BTU to Riyadh in April 2023.

If the tail is wrong, that entire chain dissolves. SU-BTU and SU-BTV differ by one character; they are consecutive serial numbers (243 and 246) of the same aircraft type, delivered a year apart, flying near-identical routes. Owens's own segment acknowledges tail numbers being conflated in this coverage.

This page takes no position on which is correct. It records that the question is open, has not been asked publicly before, and is settleable in minutes by anyone with archive access: SU-BTV is hex 0101D1, SU-BTU is hex 0101D0, and the raw ADS-B record for 27 May 2025 into KPVU carries one of them.

The counterargument​

Every innocent explanation for this location, stated at full strength.

  • Duncan Aviation operates a full-service MRO on this field, and the same company has held the Egyptian Air Force's aircraft maintenance account since 1999, under a five-year direct contract announced in an October 2015 trade press release. Duncan's own manager anticipated the objection in that release: the EAF "has chosen to fly over closer maintenance companies" to reach its facilities. A foreign VIP fleet routing through a Duncan facility is a documented, decades-old arrangement.
  • A 113-day stay is a maintenance stay, not an operation. A 1998-build Gulfstream IV in for a heavy check, paint and an avionics upgrade looks exactly like SU-BND's record: arrive, sit for four months, fly one functional check flight, leave. The independent auditor of the overlap sheet — a hostile reviewer — volunteers the same explanation unprompted, writing "ACCURATE POSS BROKEN JET GROUNDED IN PROVO."
  • The two Provo→Provo round-robins fit post-maintenance check flights. 55 minutes and 68 minutes, by two different aircraft, five months apart, each landing where it started.
  • The six-day dwell is constant across every visit and every city. Provo, Lincoln, Lincoln, Wichita — six to eight days every time regardless of destination. A tasking following a person would produce dwells that track that person's schedule.
  • John Cullen, an investigator central to the plane research, dismissed a strong association between the Egyptian jets and the assassination, citing the long-standing Provo maintenance contracts and characterising some legs as routine ferrying.
  • Neither Kirk is documented here. Charlie Kirk was in Seoul during part of the September stay; Erika Kirk reportedly stayed in Arizona on 10 September.

And the counter to the counterargument​

Fairness runs in both directions, and three things the maintenance reading does not settle:

  1. Why Provo rather than Lincoln in September. Every other 2025 rotation by this fleet that was clearly maintenance went to Lincoln — the main plant, three times — or to Wichita. The September visit went to Provo. So did April and late May. Something changed about Utah in 2025, and no published account explains what.
  2. The 5 September SU-BND sortie. A 68-minute closed-loop flight by an aircraft dormant for three months, five days before the event, has been characterised by one analyst as consistent with a corridor mapping run or an electronic sweep. It is also consistent with a check flight. Nobody has published the raw track that would distinguish them.
  3. The 07:14 departure on the morning of the shooting. The maintenance explanation covers why the aircraft was at Provo. It does not address the timing of its departure, which is the fact that started all of this.

What we do not know​

Named, so the holes are visible:

  1. No manifest exists in public for any of these seven arrivals. Not one.
  2. The customs records are in North Dakota. Every 2025 Provo arrival came in on a domestic leg from Minot (MOT). Anyone seeking entry records, passport data or a passenger list is looking in the wrong state if they are looking in Utah.
  3. SU-BGM's arrival date is unknown. The export begins with the aircraft already at Provo on 10 April 2025. When it arrived, and via where, is not in the published record.
  4. SU-BND's July 2024 departure is reported, not exported. The "sat there until 12 July" note comes from the audit's commentary rather than from a leg-by-leg export.
  5. The 10 June 2025 Provo→Provo flight has no duration logged, meaning the tracker captured a departure and an arrival without a continuous track. What happened in between is not in the data.
  6. The Kirk-side event dates are uncited. They come from a researcher timeline on X. Every one of them needs a primary source before it should be relied on.
  7. The Duncan Aviation work orders would settle most of this, and are not public.