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.
Sources
- 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.