Provo Airport Badge Access List Modified 9/11/25 (Claims)
:::caution Attributed claims only Airport badge lists are living compliance records that change constantly and lawfully. This item has no document, no custodian, and no allegation against any person. It is listed so it can be checked or retired, not because it currently shows anything. :::
Claim snapshot
| Field | Value |
|---|---|
| The claim | The Provo Airport badge access list was reportedly updated or modified on Sept 11, 2025 — the day after the assassination |
| Raised by | Anonymous citizen investigators; item 8 of the "Strange events" list |
| First surfaced | Undated in source |
| Rests on | A single unsourced line in a working list |
| Evidence rating | THIN |
What is alleged
The claim is one sentence long, and this page will not inflate it. Item 8 of the investigation file's "Strange events" list reads, in full: "Provo Airport: The Provo airport badge access list was updated 9/11/25. Modified the day after?" That is the entirety of it. The question mark is the original author's.
The suspicion being gestured at is straightforward. Provo Municipal Airport is the nearest airfield to Utah Valley University — roughly a ten-minute drive — and it sits at the centre of several other threads in this section: the Egyptian jet and alleged counter-UAS testing during September 4–10, the N560TW turnaround on the morning of the shooting, and the N888KG departure afterward. If credentialed-access records at that airfield were touched in the twenty-four hours after a national-headline assassination ten minutes away, an investigator would want to know why, because badge records are precisely the kind of record that establishes who had lawful airside privileges — and precisely the kind that could, in theory, be altered to obscure it.
What the item does not contain is worth stating plainly: there is no document, no screenshot, no named custodian, no before-and-after comparison, and no allegation that any specific person changed any specific entry. It is an observation someone wrote down to check later, and nobody appears to have checked it.
The ordinary explanation
Airport SIDA and badge access lists are living compliance records that are updated continuously as a matter of federal requirement. New hires, terminations, badge expirations and renewals, annual recurring-training reconciliations, and TSA-driven audits all generate modification timestamps as a routine byproduct of operating an airport. Many badging systems additionally stamp a "modified" date on any read-write touch of a record, meaning a modification date can be produced by an administrator simply opening the file.
More to the point, September 11, 2025 is exactly when one would expect that record to be touched for entirely innocent reasons. A national-headline assassination had occurred the previous day at a campus ten minutes from the field. A precautionary security review, a law-enforcement records request, a heightened-posture access audit, or a routine inquiry from any of the federal agencies then swarming Utah County would each produce the same metadata as anything sinister. The observation and the innocent explanation are indistinguishable on the evidence presented.
And without a before-and-after snapshot, a "modified" date says nothing whatsoever about what changed or why. No one has produced one. A modification timestamp is not a diff.
What would settle it
- A public-records request to the Provo Municipal Airport authority for the badge system's audit log covering September 1–30, 2025 — which would show what changed, not merely that something did.
- The identity of the administrator account that made the September 11 change, and the reason logged for it.
- Whether any federal agency requested badge records from PVU in that window, and on what date.
- The airport's ordinary modification cadence for the preceding twelve months, which would establish whether a September 11 change is unusual at all.
- Any evidence that a badge holder was removed rather than added — the only version of this claim that would matter.
Interesting In This Area
- An Egypt-registered jet had reportedly sat at that airfield since September 4.
- SAM-702 and the HADES aircraft are the other flight-record items here.
- Fort Huachuca image results were reportedly wiped, another records claim with no document.
- The US Intel list ranks items honestly, including the ones published to be retired.
Interesting In Other Areas
- Provo Municipal sits ten minutes from the courtyard where Charlie Kirk died.
- A booking-side tip reportedly places the Egyptian crews in one Orem hotel.
- Manifests, visas and waivers are where every foreign-nexus lead stops.
- Those Egyptian Air Force aircraft left the morning of September 10.
Images
Other Pages In This Section
SAM-702 to Fort Huachuca — the Hansell Passenger Claim
A USAF C-37A reportedly sat at the Army's intelligence home and left the morning of September 9. The claim that the Pentagon's top intelligence official was aboard rests on one broadcaster's allegation; no manifest or visitor log has been released.
Read this
The Claim a Group Blocked University Security (Claims)
One numbered bullet, with the file's own author writing "Is that true" into the record as he wrote the claim down. No name, no footage, no date, and no description of what blocking would have meant.
Read this
The Executive Who Removed the Camera SD Card (Claims)
The file carries this claim twice and never reconciles the two versions: an unnamed executive in a bare numbered item, and a named allegation by Candace Owens. TPUSA has reportedly said police instructed the removal.
Read this
The Burnt Object as a RODE Transmitter (Claims)
Proponents zoom into a charred mass photographed in the SUV and read a melted audio jack and a warning symbol into it. The imagery cannot carry that weight, and the theory's own advocates cannot agree which RØDE model it was.
Read thisElsewhere In The Investigation
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
A tip reportedly from inside the booking process places the occupants of the Egyptian jets in one named Orem hotel from September 4. Folios and camera servers could settle it in a week.
Read thisForeign-Nexus Flight Records Withheld (Claims)
Tail numbers, routes and times are all citizen trackers can see; manifests, cargo logs, visas and security waivers are where the foreign-nexus leads stop. A lead testable only with records nobody will release stays permanently open — which is itself the complaint.
Read thisEgyptian Jets — Provo Sept 4–10
Egyptian Air Force aircraft sat at Provo Municipal from September 4 and left the morning of September 10. The flight record is public; the reason is not.
Read thisSources
- No primary source is cited in the investigation file for this claim. It appears as item 8 of an anonymous "Strange events" working list with no document, screenshot, or named custodian attached.
This website's author is @HolonCitizen on X and YouTube/@HolonCitizen. Follow me there.
Interesting
- Researchers claim a life-insurance policy followed his October 7 questions.
- No cell-tower ping timeline has been released, despite the technique being routine.
- The state's rifle-to-wound chain reportedly fails at every separate link.