Every Plane Video In One Place
30 videos, every clip this site holds on aircraft, flight records and the drones reported over Utah Valley University, on one page and playable where they sit. Nothing downloads until you press play, each player keeps the clip's real shape rather than being stretched to the column, and the title under each one opens that video's own page, where the full transcript, the source post and the argument about what it actually establishes all live.
These are other people's videos, and a video is a record of what someone said, not a finding. Several of them contradict each other and at least one contradicts itself between its first half and its second. After every fourth clip the page stops for three sentences on what the flight data itself shows — each of those blocks points somewhere new in the Planes section, so reading straight down gets you the whole aircraft argument as well as the whole video corpus.
Two Egyptian-registered government jets are put on the ground at Provo on the day of the assassination by primary ADS-B position data rather than by a reading of a tracking website: SU-BTT at a closest fix of 1.23 km from the field, and SU-BND at 1.29 km. SU-BTT had been parked on that ramp since 4 September, six days before, and SU-BND did not move at all that day — its first and last fixes of 10 September are the same Provo position. Of the 85 claimed overlap rows reconstructed on this site, 29 are ones primary position data can decide either way, 25 of those put the aircraft at the field the claim names and three are refuted outright; the count and the case against reading it as shadowing are both on Following Charlie or Erika.
N1098L is a US Army-contracted Bombardier Global 6500, and researchers time low, slow passes near the campus in the half hour after the shot. It launched that morning from Biggs Army Airfield at Fort Bliss, a military origin rather than a civilian one, and it is not the only airframe of its type in this case — N2100L is a sister ship in the same contractor fleet. What that class of aircraft is actually built to collect, and why a purpose-built collection platform is not a passing business jet, is set out on ISR Program Context.
N102DZ, the aircraft reported as Charlie Kirk's, had its FAA registration certificate re-issued 36 days after the assassination to a Cheyenne, Wyoming holding company — an ordinary kind of event that is not evidence of anything by itself, but the only registration action among the case-central tails to fall after 10 September 2025. Erika Kirk publicly invited people to check that tail's flight logs, and researchers say the public history was afterwards removed; the dispute, with both sides and the copies taken beforehand, is on Erika Flight Logs Erased. Separating a genuine removal from an archive retention boundary and from an ordinary gap in volunteer receiver coverage is the whole job of Which Flight Records Were Deleted and What A 403 Actually Means, which is where this site retracted one of its own claims.
The Egyptian tails are not one stray jet: SU-BTU, SU-BTV and SU-BGM fill out the group trackers call an armada, five foreign state aircraft cycling through one small Utah municipal field in the year of the assassination. The innocent reading has to be put at the same size: Provo and Lincoln are Duncan Aviation fields and Wichita is a Falcon service centre, Duncan has held the Egyptian Air Force's maintenance account since 1999, and a jet sitting on a maintenance ramp is exactly what a maintenance visit looks like. The competing claim — that some of these legs logged as Cairo-to-Cairo actually ended in Israel with the transponder off — is collected, unverified and labelled as such, on Israel Planes.
N888KG left Provo about an hour after the shooting and is reported to have lost ADS-B near the Arizona border for the better part of an hour before reappearing and flying back. A transponder gap is not proof of anything on its own — coverage over that terrain is thin and receivers are volunteer-run — which is why the same morning's ordinary private traffic into the same small field, N560TW out of Scottsdale and N872RA out of Santa Barbara, is logged beside it rather than left out. Laid end to end against the hospital and campus timings, those windows are what produce the conflicts set out on the September 10 Flight Timeline.
Government aircraft sit on both ends of this week. SAM 99-0404 is tracked into Fort Huachuca, the Army's intelligence centre in Arizona, on 8–9 September 2025 under the SAM702 callsign, two days before the assassination. The day after it, Air Force Two carried the casket from Salt Lake City to Phoenix, landing at a military installation rather than a civilian terminal — the Casket Flight page has the route and the aircraft. Both VIP movements trace back to the same single base, Joint Base Andrews, and the same physical airframe appears in public tracking under several rotating callsigns, which is how one jet can look like several flights.
Not every aircraft in this case is a mystery, and saying so is part of the record. N59906 is a Piper Navajo Chieftain reported making four aerial-mapping passes over the campus that morning, the last ending around 11:35 — and what that class of aircraft routinely does, including its April 2026 re-registration, is laid out on Contract Survey Aircraft. N55906 differs from it by a single digit, has no confirmed route, operator or track anywhere in the public record, and is most likely a misreading that has been repeated. Which records would actually settle each remaining aircraft question — survey logs, raw ADS-B feeds, tasking orders — is the entire content of the Planes Investigation Index.
Everything above is checkable, which is the only reason to publish it. Flight Data Recovery records what came back out of four independent free archives — 1,831 aircraft-days across 3,619 trace files — and Per-Aircraft Recovery Status gives one row per tail naming every source that answered and every one that did not. Provo (KPVU) has its own page listing all 135 recorded ground visits at that field, and the follow log runs location by location rather than as one narrative. None of it places any person aboard any aircraft: no manifest for any leg has been published by anyone, and a trace proves presence, never purpose and never occupancy.
Where these came from
Every clip above is filed in the site's aircraft and flight-record video cluster or its drone video cluster, which keep them grouped by subject. This page is a second route into that same set of files, not a second copy: nothing was re-encoded and no new video bytes were written to build it, and each player streams from the same IPFS sources the clip's own page uses.
The still-image equivalent is Every Plane Photo In One Place, and both are introduced together on Plane Photos and Videos.