N102DZ Kirk's Plane
Tail number N102DZ is reported in public flight records as the aircraft associated with Charlie Kirk's travel into Utah on the morning of September 10, 2025. Reporting describes it as a larger private aircraft (15–16 passenger capacity) that flew from Scottsdale, Arizona into the Salt Lake City area ahead of his Utah Valley University appearance. This is the Kirk family's own aircraft, and it appears in the investigation mainly because it anchors the timeline of where Kirk and his party were in the hours before the event. What X accounts alleged about Erika Kirk's use of this tail, her on-camera invitation to check it, and the reported May 2026 FlightRadar24 removal is collected on Erika Kirk's flights.
Aircraft identification
- Tail number: N102DZ
- Type: Gulfstream Aerospace G-V (Gulfstream V) — confirmed in the FAA Civil Aviation Registry. Commentary describing it as "a Gulfstream G5" was correct; commentary calling that characterization unconfirmed is now out of date.
- Year built: 1998 · Serial number: 555 · Seats: 20 in the FAA type record (commentary citing 15–16 passenger capacity was in the right range)
- Registered owner: Elderberry Chestnut LLC, Cheyenne, Wyoming — also listed on the registration: Sunny Blue Sky LLC and UST Enterprises LLC. Naming a registered owner is not naming a wrongdoer, and nothing here asserts anything improper by any of them.
- Registration dates: current certificate issued 16 October 2025, last registry action 23 December 2025 — both after the assassination. Certificate reissues are ordinary events (sale, transfer between owner LLCs, renewal, address change) and are not evidence of anything by themselves; the dates are recorded because they fall inside the window in which researchers separately allege the aircraft's public flight history was removed.
- Association: Reported as Charlie Kirk's plane for the September 10 travel into Utah, and tied in reporting to Charlie Kirk, Erika Kirk, and TPUSA travel logistics
Flight history relevant to the case
Public flight records and reporting describe the day's movements in two sets that cover different legs:
- Morning inbound (Sept 10): Kirk's plane (tail N102DZ) is reported to have landed at Salt Lake City International (SLC) around 9:30 a.m. MDT, after departing Scottsdale, Arizona, for a scheduled interview before the UVU event.
- Afternoon movements (Sept 10): A separate set of records circulated by investigators lists N102DZ arriving into Scottsdale at ~1:13 p.m. local, departing again immediately at ~1:13 p.m., and landing into Provo (PVU) at ~3:31 p.m. local — i.e., later movements on the same day after the shooting. The "departed immediately at 1:13" half of that reading has since been shown to be a misread column — see the correction below.
- Provo ground movements (Sept 10): According to investigators tracking the records, after the ~3:30 p.m. Provo landing the aircraft is described as having waited roughly 30 minutes at the gate and then taxied to Duncan Aviation, the FBO on the field. They note that an Egyptian-registered jet, SU-BND, is reported to have still been on the Duncan tarmac with its power on at that time. This account is reproduced as reported; it has not been independently confirmed here.
- Later California flights: Some reporting describes N102DZ making subsequent flights to Camarillo, California (CMA). Per user reports, portions of the day's flight data were later said to be harder to find on some public trackers.
The two record sets describe different legs of the day and are reproduced here as reported. They have now been reconciled against a recovered primary record, set out immediately below.
The recovered FlightRadar24 record
Researchers reported that this tail number's FlightRadar24 history was removed in May 2026, after which no member of the public could pull it. This site previously carried that reading and now retracts it. Opened in an ordinary browser on 24 August 2026 the FlightRadar24 page for N102DZ returns HTTP 200 and renders its full identity block — Gulfstream V, type code GLF5, Mode S A00C85. Nothing has been taken down. The HTTP 403 our scripted probe recorded is a robot block, not a removal: the identical script got the identical 403 for five unrelated control aircraft, among them a Ryanair 737, a Lufthansa A380 and Nike's corporate Gulfstream. The flight table is empty for a different and equally ordinary reason — FlightRadar24 shows a logged-out visitor the last seven days only and paywalls everything older, and a private jet that has not flown in a week therefore shows nothing. Nike's Gulfstream, a control with no connection to this case, printed the same empty table on the same day. See Flight Data Recovery and What A 403 Actually Means.
The table it used to carry has been recovered. The Internet Archive holds a copy of
flightradar24.com/data/aircraft/n102dz captured at 11 September 2025, 05:57 UTC — roughly
twenty hours after the assassination. It contains
FlightRadar24's flight-history table intact: eleven rows covering 4–10 September 2025, with
scheduled and actual times. The full recovery, the method, and the other aircraft it was run against
are on Flight Data Recovery.
The five September 10 legs, as FlightRadar24 published them. Times are UTC as the archived page gave them; local times are computed alongside (Scottsdale MST = UTC−7, Utah MDT = UTC−6, California PDT = UTC−7). For reference, the shooting occurred at approximately 12:20 MDT / 18:20 UTC.
| From | To | Duration | Actual off (UTC) | Actual on (UTC) | Local |
|---|---|---|---|---|---|
| Scottsdale (SCF) | Salt Lake City (SLC) | 1:11 | 14:12 | 15:23 | 07:12 MST → 09:23 MDT |
| Salt Lake City (SLC) | Scottsdale (SCF) | 1:13 | 19:00 | 20:13 | 13:00 MDT → 13:13 MST |
| Scottsdale (SCF) | Provo (PVU) | 0:59 | 20:31 | 21:31 | 13:31 MST → 15:31 MDT |
| Provo (PVU) | Camarillo (QTC) | 1:38 | 22:10 | 23:48 | 16:10 MDT → 16:48 PDT |
| Camarillo (QTC) | Provo (PVU) | 1:11 | 00:21 (11th) | 01:32 (11th) | 17:21 PDT → 19:32 MDT |
What this confirms. The ~9:30 a.m. MDT arrival into Salt Lake City is right — the recovered record puts it at 09:23. The ~3:30 p.m. Provo landing is right — 15:31. The Camarillo, California legs are real, and there were two of them, out and back, on the evening of the 10th.
What this corrects. The reported "arriving into Scottsdale at ~1:13 p.m., departing again
immediately at ~1:13 p.m." is a misreading of FlightRadar24's duration column. The Salt Lake
City → Scottsdale leg has a flight duration of 1:13 and it landed at 13:13 Scottsdale
local — the same figure by coincidence. The aircraft's actual next departure was 13:31 MST, an
eighteen-minute turn. A fast turnaround, and worth noting as one; not the zero-minute
turnaround that has been described.
What it does not show. It says where an airframe was. It says nothing about who was aboard any leg, who arranged it, or why. The free FlightRadar24 page displayed only seven days of history, so even this recovered copy never held the multi-year record the overlap spreadsheets were built from.
The archived page also carries FlightRadar24's own identity fields — Gulfstream V, type code
GLF5, Mode S A00C85, operator "Private owner", page title N102DZ - Gulfstream V [555].
That supports the "Gulfstream G5" characterization noted above, though it is a tracking-site
database entry rather than a registry record, and the FAA registry still outranks it.
Raw recovered payloads and the day-by-day source table are saved at
site/docs/Planes/N102DZ/data/recovered/.
Theories about the aircraft's role
These are presented as open questions and reported allegations raised by independent investigators, not as conclusions. N102DZ is the Kirk family's own aircraft, and nothing here asserts wrongdoing by any person aboard.
- The SLC-versus-Provo diversion. On her November 17, 2025 podcast episode ("Operation Mocking-Plane: The Charlie Kirk Plot Thickens"), Candace Owens flagged it as strange that Kirk landed at SLC — roughly 45 miles north of UVU — instead of the much closer Provo Municipal Airport (PVU), about 7 miles from the campus. By Owens's account, Provo was also the airport where the Egyptian-registered jet SU-BTT had been based. Owens frames this as a question about why Kirk's morning routing was longer than the obvious option, not as proof of anything.
- Timeline-and-logistics scrutiny. Independent investigators on podcasts and videos have built detailed timelines of the Kirk family's movements on and around September 10, raising questions about the aircraft's parking, runway exits, and how its movements may relate to Erika Kirk's reported activities after the event. They say their timelines are cross-referenced with public statements and flight-tracking data; some posted Flightradar24 screenshots that, per user reports, were later harder to find in some apps.
- The Duncan Aviation link-up question. Researcher @AnaEscobarShow has posed the Provo ground movements as an open question: "Why did Charlie's plane (N102DZ) land in Provo at 3:30pm, wait for 30 mins at the gate and THEN make its way to Duncan Aviation to link up with the Egyptian plane (SU-BND) which was still there on and running? Was this the wait for Andrew?" She credits the work of @baroncoleman, writing "Barons timeline has helped me sm. I am going to go John-Cullen-level autist on the flight records" — a reference to investigator John Cullen's detailed flight-record method. These are framed by the researchers as questions about parking choices (the main terminal versus Duncan Aviation) and the alignment of the aircraft's arrival with the official timeline, not as findings of coordination by any person.
In response to such claims, Erika Kirk has reportedly provided her own flight logs and accounts of her movements as alibis. No public evidence ties the routing choices to any plan, and ordinary scheduling, airport-handling, and crew availability are equally consistent with the records. These remain open lines of inquiry.
Flightradar24 screenshots and reported scrubbing
Much of the public timeline work on this aircraft rests on flight-tracking screenshots shared by X users. According to posts attributed to @hurtfeelingzday, extensive screenshots of N102DZ's flight data — captured from Flightradar24 — were shared on X, including the Scottsdale and Provo (PVU) movements described above. These screenshots are the basis for several of the timestamps that independent investigators have cited.
Per user reports, portions of that flight data were later said to have been scrubbed or made harder to find on some public trackers and apps. This claim is reproduced as reported by X users and has not been independently confirmed here. A common, non-suspicious explanation is that commercial trackers honor the FAA's LADD block list (see the tracking note at the bottom of this page), which can remove flights an owner or the government has asked to hide; investigators raise the disappearance of the data as an open question rather than as proof of anything.
That question has now been tested directly, and the answer went the other way: the FlightRadar24 page for N102DZ still loads, HTTP 200, and the archived copy of the table it used to carry has been recovered in full. See the recovered record above and the status block below.
Open questions
- What is the complete, reconciled itinerary for N102DZ on September 10, 2025?
- Why did the morning inbound route to SLC rather than the closer Provo (PVU)?
- Who was aboard on the inbound leg with Kirk, and who handled the afternoon legs?
- Who is the registered owner and operator of the aircraft?
- Where did the aircraft and its crew go after the Provo arrival, including the reported Camarillo, California legs?
- Why is the aircraft reported to have parked at the main terminal first and then taxied to Duncan Aviation, and how does that timing relate to the Israel/Egyptian jet SU-BND said to have been on the Duncan tarmac?
What this aircraft would cost to buy new today
- Type (FAA-confirmed): Gulfstream Aerospace G-V (Gulfstream V), built 1998, serial 555
- Registered owner: ELDERBERRY CHESTNUT LLC (Cheyenne WY)
- Still built today? No — GV built 1995-2002; successor G550 ended 2021
- Priced against: Gulfstream G600
- Cost to buy new today: ~$58.8 million
Gulfstream V is out of production. Nearest in-production Gulfstream by cabin size and range is the G600 at ~$58.8M list. Gulfstream's current large-cabin line brackets it: G500 ~$45M to G650ER ~$78M.
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
Nothing in this aircraft's public record was found to be missing. Every archive that could plausibly hold N102DZ still holds it, the FlightRadar24 page still loads, and the archived copy of the flight table set out above was recovered intact — 13 flight rows across three archived pages, which is more published history for this tail than was on this site before the sweep.
| Source | What it holds for N102DZ |
|---|---|
adsb.lol globe_history | 12 days of track, 1 September 2025 to 9 October 2025 |
| globe.airplanes.live | 50 days of track, 1 September 2025 to 5 June 2026 |
| ADS-B Exchange monthly sample | 18 days, 1 May 2022 to 1 June 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 | 3 page snapshots held; 13 flight rows recovered off them |
A fourth route, adsb.lol's own public backup files on GitHub, supplied 13 October 2025 — a date the live adsb.lol API refuses to everyone.
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 N102DZ.
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/N102DZ/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
- Erika Kirk invited the public to check this tail logs.
- The September 10 timeline puts this arrival at 3:31 that afternoon.
- SU-BND is alleged to have shared a ramp with it that day.
- The section index lists which records would close the question.
Interesting In Other Areas
- The day-of timeline is the master version of the same afternoon.
- Pre-event timeline tracks where he was before he flew.
- Provo Municipal is the other field in play that morning.
- The hospital trip closes the same afternoon from the other end.
Other Pages In This Section
A Bombardier Global 6500 flown by an Army ISR contractor, callsign AXLE10, ran an unusual low and slow profile near Orem on September 10. No track, tasking order, or sensor product from it has appeared in the prosecution.
Read this
A Piper Navajo configured for high-resolution camera and LiDAR mapping reportedly flew four survey passes over campus hours before the shooting. What it photographed, and who tasked it, has never been established.
Read this
Elsewhere In The Investigation
September 10, 2025 – Day-of Timeline
Midnight to midnight on Utah's clock: the pre-dawn aircraft picture, the camera sightings from 8:07 AM, the 12:23:30 shot, the hospital run, and the evening flights. Every line labelled reported or claimed.
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
No ambulance, no sirens — carried into a private vehicle by his own detail. Using the car already on hand in a chaotic scene is not evidence of wrongdoing, which is why the page is about who controlled the evidence, not about rescue.
Read thisSources
- Public flight records and reporting on Charlie Kirk's September 10 arrival into SLC (~9:30 a.m. MDT from Scottsdale).
- Candace Owens podcast, November 17, 2025 episode "Operation Mocking-Plane: The Charlie Kirk Plot Thickens" (SLC-versus-Provo diversion point).
- Flight-record screenshots of Scottsdale and Provo (PVU) movements circulated by independent investigators (e.g., @hurtfeelingzday).
- @AnaEscobarShow posts raising the Provo wait, Duncan Aviation taxi, and SU-BND link-up questions, crediting @baroncoleman's timeline and citing John Cullen's flight-record method.
- Reported responses from Erika Kirk providing flight logs and alibis to such claims.
- Public ADS-B flight-tracking history for tail N102DZ.
Laws (Charlie Kirk)
- The full passenger manifest and reconciled itinerary for N102DZ on September 10 are things that the Charlie Kirk Investigation Laws may result in powerful truths coming out that aren't out yet.
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 (N102DZ Kirk's Plane) 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 same C-32A airframe type reappears the day after the killing on the Vance flight.
- Bodycam reportedly shows a Miranda warning hours before the call that named him.
- A citizen investigator matches a construction-site mast to a military special-operations antenna.
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 — N102DZ — 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 — N102DZ — volunteer-fed, unfiltered tracker that does not honor LADD, so it often shows blocked aircraft and tracks the filtered sites leave out.
Images
