The Diverted Pursuit — Where The First Hours Of The Investigation Went
:::caution Legal Disclaimer Tyler Robinson is charged, not convicted, and is presumed innocent. Nothing on this page states as fact that any living person committed a crime, destroyed evidence, or acted improperly. Court filings in this case are subject to a gag order and sealing, so the public record is incomplete by design. :::
:::note This page names nobody, and it is about decisions rather than people Archived radio traffic from the afternoon of September 10, 2025 carries look-outs for two private individuals. Neither has been charged with anything in this case. They are not named here. They are not described here. Nothing about their conduct, their knowledge or their state of mind is asserted or implied anywhere on this page. Every demand below is addressed to a records custodian and asks for documents about decisions and timing — who directed effort, at what minute, on whose authority. It never asks about a person. :::
What We Contend
This is a contention this exercise would attempt to prove. It is not a finding this site asserts. Appendix A thesis T5: the direction of local police effort toward two individuals in vehicles absorbed the first hours of the investigation into Charlie Kirk's death, and federal personnel were already present at an address when local units arrived there.
Two claims sit inside that sentence and they are different in kind. The first is about where effort went — a question of hours and unit assignments. The second is about arrival order — a question of which agency's personnel reached an address first, and when. Both are questions of fact, and both are answerable from records that already exist or existed.
Nothing here says the direction was wrong, deliberate, or improper. Multi-agency responses to a mass-casualty event chase bad tips as a matter of routine, and chasing a bad tip is not misconduct. What the contention says is narrower and harder: that the State has never accounted, on any document the defense can inspect, for what its own investigation was doing during the hours it says it was building the case now before the court.
The strength of this thesis is what it rests on. Computer-aided dispatch records, radio logs, licence-plate-reader query logs, automatic-vehicle-location telemetry and body-worn camera activation metadata are all machine-generated and contemporaneous. Nobody wrote them for a courtroom. Nobody can shade them from memory eleven months later. They cannot be argued with, only produced or not produced. This page does not know what they show, and says so. It contends only that a capital jury is entitled to see them before it is asked to be sure.
The arrival-order half of the contention deserves one more sentence, because it is the load-bearing one and it is the easiest to write badly. Whether federal personnel were at an address before local units is not a matter of anyone's impression. It is fixed by the intersection of four independent machine-generated sources — the CAD unit-status log, vehicle automatic-vehicle-location telemetry, body-worn camera activation metadata, and the scene entry log — and where those four agree, the order is a fact established four ways with no witness's memory involved. Where they disagree, the disagreement is itself discoverable and itself a cross-examination. Either result is useful to a defense. Neither requires an accusation against anybody, and this page makes none.
The Chain Of Reasoning
Each link is a fact this site already carries, in the order the links build. Where the site holds no page for a link, that is said plainly and the link is marked as research still to do rather than dressed up with a citation.
- The shot is fixed at 12:23:30 p.m. MDT, and the first archived police-radio report of a shooting is placed at 12:26 p.m. — about two and a half minutes later. This site's own page on that interval argues it is fast rather than slow, and that even the 12:26 figure is secondhand because no audio, log, agency or channel is identified behind it. That concession belongs at the top of the chain, not buried at the bottom.
- The description broadcast in the first minutes was a male in all black with a mask, described in some transmissions with a tactical helmet, carrying a long gun — a description that does not match the figure in the imagery released the following evening (black-clad rooftop suspect dropped from the narrative, dispatch and scanner timeline).
- Multiple 911 callers reported an armed man near the Fulton Library, on the north-side route away from the Losee Center — the same area where a backpack, jacket and gloves were later recovered (dispatch and scanner timeline).
- Within minutes of the shot a man at the scene was detained after a false claim of responsibility, and the radio carried "suspect in custody" almost immediately — a channel echo, not a capture. He was publicly cleared the same day of any role in the killing (distraction timeline, Utah DPS).
- A second person was taken into custody that afternoon, a federal announcement signalled a suspect was in hand, and the person was released roughly ninety minutes later with no public explanation. Researchers argue the announcement may have paused the field search. This site records plainly that no public CAD log has confirmed a stand-down (Kash Patel briefings, manhunt timeline).
- Through the afternoon the archived radio carries a running vehicle hunt built on a report that an armed man was going hospital to hospital — and officers relayed on air that a hospital, asked directly, said none of it had happened. The hunt continued (dispatch and scanner timeline).
- The described vehicle changed colour, make and model repeatedly across the same afternoon, and one plate, when run, returned no record of any kind (dispatch and scanner timeline, rental cars and vehicle movements).
- Local units surveilling a residential address reported a vehicle arriving that turned out to be federal, after which dispatch stated on air that the individual would not be pursued. A separate vehicle at the same address departed as an officer moved to read its plate, and no plate was ever read out (dispatch and scanner timeline).
- The rifle was recovered only after an arm-to-arm sweep and a K-9 pass had found nothing, and — on the reported sequence this site carries — after federal agents directed a further search (gun discovery sequence, rifle found after federal redirect).
- On the certified record, the SBI sergeant who agreed she was "the traffic manager of the whole operation" arrived near the south end of campus at about 1:30 p.m., saw "multiple police cars as well as multiple officers from various agencies," and was directed to a command post in the Fugal Building. She testified that the courtyard was assigned to the FBI. Certified preliminary hearing Day 4, searched in full.
- On the same certified record, the items recovered near the library went to the FBI laboratory and further analysis was stopped. Asked whether she had communicated that those items were not connected to the case, the witness answered that she did not remember communicating it, and agreed that if lab notes said so it would not be inconsistent with what she knew (forensic tests reportedly skipped).
- Not one of the machine-generated records that would fix the sequence is public. No CAD export, radio log, look-out issuance record, plate-reader query log, vehicle telemetry or camera activation trail appears among the State's 34 preliminary-hearing exhibits, and no communications-centre witness appears on the State's May 6, 2026 witness list (dispatch and CAD records, detention and release records).
- No federal case agent has been cross-examined in this case at all. Exactly one FBI witness has testified live across five hearing days, she was a laboratory examiner, and the defense called her (FBI agents on the stand).
- Local officers were reportedly told not to run down witness interviews while descriptions were still fresh, and the counterterrorism review of foreign leads was reportedly ordered to stop once a suspect was in custody, before its leads were exhausted (witness interviews reportedly blocked, locals reportedly told not to investigate, Joe Kent). These are reported allegations, not findings, and they belong in the chain as the reason a defense would want the tasking records rather than as proof of anything.
- The defense reported, on August 28, 2026, that it has identified 40 law-enforcement or other government agencies in this case, and that some forensic material sits with the FBI and ATF and may not be produced absent an order of the Court. Forty agencies generate forty activation records, and not one of them is public (court document archive, FBI discovery delays).
- Therefore: the hours in which a capital investigation was formed are documented only in records nobody outside the case has seen, and the parts of those hours that are visible show effort directed away from the courtyard on the strength of a report a hospital denied.
Research still to do, and no page on this site yet carries it. Three links in the chain above are asserted from archived radio narration alone and have no documentary anchor here: who authorised each vehicle look-out and at what minute; the arrival order of agencies at each address units were sent to; and the initiation and release times of every field contact that afternoon. Those three are exactly what the two instruments below demand, and until a custodian produces them they stay marked as gaps rather than written up as findings.
The Day-One Track
Our attorney was retained on September 12, 2025. Everything in this thesis is perishable, and most of it is perishable on a schedule measured in weeks rather than years.
That is the difference this thesis turns on. A dispatch recording, a plate-reader query row and a fleet telemetry track are not evidence anybody decided to destroy — they are database rows on an automatic clock, and they reach their ordinary deletion date whether or not a homicide is under investigation, unless somebody writes a letter saying otherwise. Between September 12 and October 20, 2025 there was no preservation order of any kind in this case, which means that for thirty-eight days every one of these artefacts was governed by nothing but ordinary agency practice. A letter needs no court, no filing fee and no opponent's consent, and it is the single highest-value-per-minute act available in the first week.
| When | What our attorney serves | What was still recoverable then | When the window closed |
|---|---|---|---|
| Sept 12, 2025 | Preservation letters, same day, to the dispatch authority of record for Utah County and to every responding agency, naming by artefact: the CAD incident record and its audit history, all radio recordings and the talkgroup patch log, the look-out issuance record, and the licence-plate-reader query log | All of it. Nothing had reached an ordinary purge date. A letter needs no court, no filing fee and no opponent's consent | Rolling, per agency schedule |
| Sept 13, 2025 | Litigation-hold letter to the licence-plate-reader system operator, demanding the September 10 query log, the hit and non-hit returns, and the purge setting in force that day | Plate-reader reads and the queries run against them. Vendor default automatic purge for reads was commonly 30 days at the time | Roughly mid-October 2025 absent a hold — before the first preservation order of any kind was entered on October 20 |
| Sept 15, 2025 | Rule 16 request naming dispatch, 911 audio, field-contact documentation and communications records | The full production clock starts fifteen days earlier than it did | Does not close — but the earlier it starts, the earlier the gaps surface |
| Sept 16, 2025 | Preservation demand for body-worn camera device audit trails, for every device assigned to every officer at every address, including devices that produced no recording | The audit row survives even where footage does not, because it is a database entry rather than a video file | Same platform retention as the footage, and it is not requested by default |
| Sept 19, 2025 | Rule 14 subpoena to each agency's fleet system for automatic-vehicle-location telemetry for the operational period | Position tracks for every marked unit, independent of any officer's account | The most perishable record in this thesis. Commercial fleet telematics retention is commonly weeks to months. Closed |
| Sept 22, 2025 | Demand for the detention paperwork for every field contact — initiation time and release time as separate entries, the booking or non-booking determination, and the name and rank of whoever made it | Paper and forms still in the originating file, with the two times on them | Open in principle; the specific forms are not public and never have been |
| Sept 26, 2025 | Demand for the arrival-order record at each address: unit arrival stamps, any scene entry or sign-in sheet, and any entry noting personnel already present | A sign-in sheet was still a physical page on somebody's clipboard | Unknown, which is itself the reason to have asked in September |
| Oct 1, 2025 | Motion to compel a filed written response identifying, item by item, what is produced and what is withheld and why — the formula the September 30, 2025 request itself invokes | Converts every silence into a document a jury can be told about | Still open. This one has not closed |
Three of those eight rows are gone and cannot be brought back at any price: the plate-reader query log if no hold was applied, the fleet telemetry, and whatever a scene sign-in sheet recorded before it went into somebody's file. Four are still open today — the CAD record, the detention paperwork, the arrival-order artefacts and the retention schedules — and the eighth, the demand for a filed written response, was never time-limited at all. This thesis is therefore not a lament about a lost year. Most of what it asks for is still obtainable on a subpoena that a judge would sign this week.
The Gap Analysis
How this was checked matters as much as what it found, so here it is plainly. We hold certified Moorhead transcripts for two hearing days only — preliminary hearing Day 4 (July 9, 2026) at 278 pages and Day 5 (July 10, 2026) at 97 pages. Both were searched in full, term by term, together with the word index printed at the back of each volume. The index is the control: it counts every occurrence of every word, so a term that returns nothing in the body and nothing in the index is genuinely absent from that day rather than missed by a bad search string. Days 1, 2 and 3 exist here only as machine transcriptions of the pool feed and are not the record. On the filings side, the archive holds 374 PDFs against 867 known docket entries, of which only 258 ever had a public PDF at all, and 62 entries are private or sealed.
| # | What we would do, and of whom | Stage and date | Witness took the stand? | Asked on the record we hold? | How we checked |
|---|---|---|---|---|---|
| 1 | "Sergeant, at each address local units were sent to that afternoon, which agency's personnel were already there when the first local unit arrived?" — to Sgt. Jennifer Faumuina | Preliminary hearing cross, July 9, 2026 | Yes — July 7 and July 9, 2026 | Partly — her own arrival at about 1:30 p.m. and "multiple officers from various agencies" are on the record; the arrival order at any other address is not | T1 — certified Day 4, searched in full including the back word index |
| 2 | "What is the computer-aided dispatch incident number for this operation, does that record still exist, and has anyone placed a hold on it?" — to the same witness | Preliminary hearing cross, July 9, 2026 | Yes | Not found — the words dispatch and CAD appear nowhere in either certified transcript as a question or an answer | T1 — certified Days 4 and 5, searched; the five "cad" string hits are Academy and decades |
| 3 | Rule 14 subpoena duces tecum to the dispatch authority of record and to each responding agency for the complete CAD incident record in native format with its audit or edit history, plus a Utah R. Evid. 902(11) and 902(13) custodian certification | Third-party records subpoena — available from arraignment onward | n/a | Not found — no such subpoena is visible for any dispatch authority | T2 — dockets 468 and 495 show a Notice of Subpoena Duces Tecum to the Utah County Sheriff's Department; neither the notice nor any return is held, so its scope is unknown to us |
| 4 | Rule 16 request item 10: "copies of all recordings and/or transcripts of any communications, including dispatch calls from law enforcement, fire department or any other civilian agency" | Formal Request for Discovery, September 30, 2025, Dkt. 61 | n/a | Asked — expressly requested, twenty days after the killing | T2 — filing held in the archive, read in full |
| 5 | Rule 16 request item 8: "all field interview cards used to identify any individual(s) involved" | Formal Request for Discovery, September 30, 2025, Dkt. 61 | n/a | Asked — the closest thing on the public record to a demand for the field-contact paperwork | T2 — filing held |
| 6 | Rule 16 request item 11: "specify the date, time and substance of any and all further contact between any investigating officer and any defendant, co-defendant, or witness" | Formal Request for Discovery, September 30, 2025, Dkt. 61 | n/a | Asked — and it is the request that would surface the contact times if answered item by item | T2 — filing held |
| 7 | Rule 16 request item 21: information material to "the participation of any other individual in any charged crime" | Formal Request for Discovery, September 30, 2025, Dkt. 61 | n/a | Asked — framed as a mitigation and equal-culpability request rather than a first-hours request | T2 — filing held |
| 8 | "Of the 229 pages your agency produced, is there a section that reconstructs where units were between 12:26 p.m. and midnight on September 10?" — to Sgt. Faumuina | Preliminary hearing cross, July 9, 2026 | Yes | Partly — the 229-page compiled report, its multiple authors and the nine sections she wrote are all established on the certified record; no section reconstructing unit movements was identified | T1 — certified Day 4, cross by Mr. Burt, searched |
| 9 | "You requested DNA and other analysis on the items recovered near the library. At some point did you decide to pull the plug on that?" — to Sgt. Faumuina | Preliminary hearing cross, July 9, 2026 | Yes | Asked — and answered: at the time it was sent "we didn't have more information as far as whether or not the evidence that were collected there were probative." Asked whether she communicated to the lab that the items were unconnected, she answered "I don't remember communicating that" | T1 — certified Day 4, searched. This is the strongest single exchange on the certified record for this thesis |
| 10 | "Who has authority to put a vehicle look-out on the air, and is the authorising officer recorded in the system when they do?" — to any Utah officer witness | Preliminary hearing cross, July 6-10, 2026 | Yes for four Utah officers | Not found — BOLO, lookout and look-out appear nowhere in either certified transcript | T1 — certified Days 4 and 5, searched |
| 11 | Rule 14 subpoena to the licence-plate-reader system operator for the September 10, 2025 query log, every hit and non-hit, the purge setting in force that day, and any litigation hold and its date | Third-party records subpoena — available now | n/a | Not found — Flock, plate reader and licence plate appear nowhere in either certified transcript, and no such demand is visible in the archive | T1 for the transcripts; T2 for the filings, 374 PDFs held against 867 known docket entries |
| 12 | Demand for body-worn camera device audit trails — power-on, record start, record stop, upload, category, retention, access and deletion events — for every device at every address, including devices that produced no file | Rule 16 supplement and Rule 14 subpoena | Yes — the subject arose | Partly — on the certified record the witness placed a body camera at the rifle recovery: "I believe one of the officers on scene actually had his body camera on," and confirmed "I have not" seen it. The activation log itself was not sought on that record | T1 — certified Day 4, searched |
| 13 | Demand for detention paperwork with initiation and release times as separate entries, the booking or non-booking determination, and the name and rank of the officer who made it | Rule 16 supplement; Rule 14 subpoena to each responding agency | n/a | Not found — detain and detention appear nowhere in either certified transcript | T1 for the transcripts. Detentions were raised on Day 2, which we hold only as an uncertified machine transcription of the pool feed — T3, and not citable as the record |
| 14 | Cross-examination of a federal case agent on which decisions that afternoon were federal, who directed effort toward each described vehicle, and who ended it | Preliminary hearing, July 6-10, 2026 | No — exactly one FBI witness testified live in five days, a laboratory examiner, and the defense called her | Not found — no federal case agent has been examined at any stage | T1 for Days 4 and 5; T2 for the State's May 6, 2026 witness list, which names no communications-centre or federal case-agent witness |
| 15 | Rule 14 subpoena for the interoperability and patch log — which outside agencies, including federal personnel, were placed onto a local talkgroup, at what time, and on whose authorisation | Third-party records subpoena — available now | n/a | Not found in the material we hold | T2 — filings archive searched; T4 for anything inside the sealed set |
| 16 | Motion to compel a filed written response identifying with specificity what will not be produced, per State v. Knight and Utah R. Crim. P. 16 — the formula the September 30, 2025 request itself demands | Rule 16 enforcement — available from October 2025 onward | n/a | Not found — the request asks for a written response; no filed production response identifying what was produced or withheld is held | T2 — archive holds 374 PDFs against 867 docket rows, 258 of which ever had a public PDF |
| 17 | Fold the CAD, radio, look-out, plate-reader, telemetry and camera-metadata demands into the motion to compel forensic discovery the FBI and ATF have not produced, and ask the Court to set a briefing schedule | Discovery Status Report, August 28, 2026, Dkt. 257 — schedule to be requested September 1, 2026 | n/a | Not yet due — and a step not yet due has not been missed. The vehicle for this demand is opening, not closed | T2 — Dkt. 257 held and read in full |
| 18 | "Was there an entry log or a sign-in sheet for the cordoned area, and was any log kept of who was present at the command post and at what times?" — to Sgt. Jennifer Faumuina | Preliminary hearing cross, July 9, 2026 | Yes — July 7 and July 9, 2026 | Partly — the command post in the Fugal Building is on the certified record, along with evidence being compiled there and "the discussion that was had as to who would take custody." No entry log, sign-in sheet or attendance record was identified | T1 — certified Day 4, searched |
| 19 | Rule 16 request item 1: "all 911 audio recordings and unofficial transcripts," and — beyond it — the call-taker screen notes and the ANI/ALI records for every call relating to the incident | Formal Request for Discovery, September 30, 2025, Dkt. 61 | n/a | Asked as to the audio. Not found as to the call-taker notes and ANI/ALI, which are a different artefact and are not requested by default | T2 — filing held and read in full |
| 20 | Rule 14 subpoena for the mutual-aid and task-force activation record across every agency that self-deployed or was requested — the time of each request and the time each agency's first unit reported on scene | Third-party records subpoena — available now | n/a | Not found — the certified record establishes that "multiple agencies besides the SBI" were involved and that the courtyard was assigned to the FBI, but no activation record, arrival stamp or agency roster was put before the court | T1 for the certified admission of multi-agency involvement; T2 for the absence of any activation record in the archive |
Where this chain breaks the State's case
The link it attacks is not identity and not mechanism. It is the reliability of the process that produced the evidence the State will offer. Every item the State recovered on September 10 was recovered by units operating inside a command structure whose decisions that afternoon are documented only in records the defense cannot inspect. If the sequence of those hours cannot be reconstructed from the State's own machine-generated records, the jury is being asked to accept a chronology that nobody — not the defense, not the court, not the State's own witnesses reading from a 229-page compilation many hands wrote — can independently check.
It also attacks the State's witnesses at the joint a defense can actually reach. Almost everything offered about the first hours arrives through Utah officers summarising a 229-page compiled report that many hands wrote. A witness reading out another author's paragraph has no personal knowledge of the event described in it — a Rule 602 problem and a hearsay-conduit problem at the same time. The CAD export is the document underneath those paragraphs. Holding it turns every "as I recall" into a checkable claim, and it makes impeachment by omission available: a decision described from the stand that left no trace in a system which logs everything automatically is a fair question, and only counsel holding the export can ask it.
What would defeat this thesis
Produce the CAD incident record with its audit history and the radio log, and let them show that each vehicle look-out was originated by a local officer on a citizen 911 call, was cancelled within an ordinary interval, and that local units reached every address before any federal personnel did. That result ends this thesis, and this page will publish it with the same prominence as anything else. A busy, chaotic, tip-chasing afternoon that the records account for minute by minute is an ordinary investigation, not a diverted one.
The instruments that serve this thesis
- Subpoena The Dispatch And CAD Record — primary. The twelve-item Schedule A rider, the retention arithmetic, and the custodian certification that makes the timeline self-authenticating.
- Demand The Detention And Release Record — And The Arrival Order — primary. The six artefact families, and the four machine-generated sources that fix arrival order without needing anyone's memory.
- Put FBI Case Agents On The Stand — supporting. A document production can omit. A witness asked who directed effort has to answer.
How This Reaches A Juror
This is Route 2 in its purest form — the investigation itself — and it is worth saying plainly what that means. The jury does not need to know who the two individuals were. It does not need an alternative perpetrator, a foreign nexus, or any theory at all about the microphone. It needs one thing: to understand that the first hours of a capital investigation went somewhere the State has not accounted for on any record the defense has been permitted to inspect.
That is also why this thesis is cheap. It touches no classified holding, asks no agency to waive anything, and requests database exports that county agencies produce routinely in ordinary criminal cases. And a refusal is also an answer. A custodian who reports that the audit trail was purged has told the jury something no witness ever would.
"The State says it built this case in the hours after Charlie Kirk was killed. So ask where those hours went. Officers spent the afternoon chasing a report a hospital told them had never happened, after a vehicle that changed colour four times, behind a plate that came back to nothing. There is a record of every minute of it — a dispatch log, a radio tape, a query log, a camera that writes down when it was switched on. Not one of them is in this courtroom. You are not being asked to trust the evidence. You are being asked to trust a process you have not been allowed to look at."
One juror who cannot answer that is a hung jury, and this is the kind of doubt that does not need a rival story to survive deliberation. It survives because nobody in the room can close it — not the prosecutor, not the witnesses, and not the judge. The only thing that closes it is the record itself, and the State can close it any time it chooses to produce one.
What Would Have To Be Obtained
Reachable — a court can order these, and courts do, routinely.
- The complete CAD incident record in native format with its audit or edit history, from the dispatch authority of record and from each responding agency. Rule 14 subpoena duces tecum, with a Utah R. Evid. 902(11) and 902(13) custodian certification so it comes in without a live witness.
- All radio recordings, the radio log, the talkgroup map and the interoperability patch log for the operational period.
- The look-out issuance record: exact text broadcast, time, originating agency, authorising officer identifier, and every amendment and cancellation with its time.
- The licence-plate-reader query log, hits and non-hits, the retention and purge settings in force on September 10, 2025, and any litigation hold with the date it was applied.
- Detention paperwork for every field contact — initiation and release times as separate entries — plus the booking or non-booking determination and the name and rank of the person who made it.
- Body-worn camera device audit trails for every device at every address, including devices that produced no recording, and every written non-activation report Utah's body-worn camera provisions contemplate.
- Automatic-vehicle-location telemetry for every marked unit, in native export.
- Any scene entry, sign-in, perimeter or command-post attendance log, and the identity of the officer who kept it.
- The mutual-aid and task-force activation record across the 40 law-enforcement or other government agencies the defense reported identified as of August 28, 2026.
- The 911 and non-emergency call recordings, the call-taker screen notes, and the ANI/ALI records for every call relating to the incident — a different artefact from the audio, and not produced by default.
- The record of who directed effort toward each described vehicle: the transmission or entry that started it, the requesting agency or role, the basis stated at the time, and the transmission or entry that ended it.
- The CAD comment lines with the terminal and operator identifier of whoever typed each one, exported as a field rather than flattened into a printed narrative.
- The records-retention schedule for each of the above, and documentation of every hold applied to it — which is how the Court learns, on the agency's own paper, whether a demand made today is a demand made too late.
- A filed written response identifying, item by item, what is produced and what is withheld and on what legal basis. A refusal on the docket is worth more to a defense than a silence in a file room.
Unreachable, or reachable only through the State.
- Federal internal communications about who directed local effort toward which address and when. The defense has told the Court that FBI and ATF material may not come out absent an order, and the motion to compel it is being prepared.
- Any federal deconfliction, surveillance-notification or task-force-tasking record explaining why federal personnel were at an address ahead of local units. Nothing on this site establishes that such a record exists, and this page does not assume one does.
- Anything inside the sealed December 2025 to February 2026 material, the five sworn Rule 1102 written statements, or the 34 preliminary-hearing exhibits, of which we hold zero as documents.
- Any classified holding. This thesis deliberately asks for nothing from one, because a demand that cannot be granted produces no ruling and therefore no record of refusal.
- The unedited talkgroup audio in a form authenticated by anyone. What circulates publicly is clipped and narrated by third parties, and no page on this site should be read as treating that as the record.
The line between the two lists is the whole strategy. Everything in the reachable list is a database export from a county agency, granted routinely, cheap to ask for, and self-authenticating once certified. Everything in the unreachable list is the reason the motion the defense told the Court it is preparing — to compel forensic discovery the FBI and ATF have not produced — matters more to this thesis than any subpoena our attorney could draft. We would file the cheap demands first and use the answers to frame the hard one, because a court that has already seen four local custodians produce their logs asks a different question of the agency that will not.
The Honest Counterargument
The first answer is the strongest, and it is that a chaotic afternoon is the normal texture of a mass-casualty response. False tips, mistaken vehicle descriptions, a plate that does not return, a hospital that contradicts a report already on the air, and units surveilling an address that turns out to hold other law enforcement — every one of those happens in ordinary investigations that end in ordinary convictions. Federal personnel arriving first at an address in a case with FBI involvement is unremarkable; a federal officer who lives nearer the address than the responding patrol unit gets there first for reasons no more sinister than geography. A page that treats "federal personnel were already there" as inherently meaningful has assumed its conclusion. The correct posture is to establish the times from records, publish them, and let them mean whatever they mean.
The second is that the material may already be in the defense's hands. The Discovery Status Report of August 28, 2026 records 45 productions totalling 29,237 files through August 18, 2026, delivered through a platform the defense has told the Court is not a tenable review environment — thousands of duplicate filenames, no Bates in the original filenames, and PDFs that will not OCR. Detailed coding was complete on roughly 20 per cent of it. A CAD export and a radio archive could be sitting inside the eighty per cent not yet reached, under a filename that says nothing about what it is. Absence from the public docket here is close to meaningless, and this page's every "not found" means only what it says.
The third is about stage, and it has already bitten in this case. A preliminary hearing tests probable cause. It is not the forum for reconstructing an agency's afternoon, and a magistrate would properly cut off a dispatch-timeline cross as beyond scope. When the defense sought a certificate for an out-of-state witness at this same hearing, the court applied the Rule 14 reasonableness limitation and declined it, holding that a probable-cause proceeding is not the place for that litigation. A records subpoena aimed at arrival order would have met the same objection at the same stage. Reserving this for the post-bind-over discovery motion is a defensible sequencing choice and not a lapse — and that motion's briefing schedule is being requested on the day this page publishes.
The fourth cuts at the evidence rather than the argument. Everything in links 6 through 8 of the chain rests on archived scanner audio narrated by citizen researchers, not on any certified transcript, agency release or filed document. Clips are selected. Narration is characterisation. A three-hour talkgroup compressed into fifteen minutes will sound like a diverted afternoon whether or not it was one, because the routine traffic is what got cut. Until a custodian produces the unedited log, the honest description of links 6 through 8 is unverified public claims about a recording nobody outside the case has authenticated — which is exactly why this thesis is written as a demand for records rather than as a finding about hours.
The fifth is that "unaccounted for" is doing heavy lifting that the archive cannot support. The public docket is not the case. A broad gag order has been in force since December 16, 2025, sixty-two docket entries are marked private or sealed, and a subpoena duces tecum was noticed to the Utah County Sheriff's Department on April 1, 2026 whose scope is completely invisible to us — we hold neither the notice, nor the Sheriff's Response, nor the defense Reply's underlying attachments. That subpoena could already ask for every document on this page. Every "not found" in the table above is a statement about our archive, never about counsel, and a reader who converts one into the other has misread the page.
And the sixth is the concession this exercise owes the real team. The defense asked for the dispatch recordings in writing on September 30, 2025, twenty days after the killing, and asked for the field interview cards and the contact-by-contact times in the same document. That is early, correct work on exactly this ground, and nothing in this thesis is a criticism of it. What our attorney would do differently is narrower: serve the preservation letter on day one rather than the request on day twenty, name the audit trail and the query log and the telemetry as artefacts rather than asking for "recordings", and demand the arrival-order record as a distinct thing rather than hoping it falls out of the reports.
Sources On This Site
- Dispatch, Police Radio and Scanner Timeline — September 10
- Three Minutes to the First Police Report
- Ten Minutes After the Shot
- Shooting, Minute By Minute
- Black-Clad Rooftop Suspect Dropped From the Narrative
- Distraction Timeline — September 10-11
- Distraction Events Timeline
- Kash Patel Manhunt Timeline
- Rental Cars and Vehicle Movements Timeline
- Suspect Manhunt and Misidentification
- Orem Police and Local Response
- UVU Campus Police
- Utah County Sheriff
- Local Police Reportedly Told Not to Investigate
- Rifle Found After Federal Redirect
- Gun Discovery Sequence
- Standard Forensic Tests Reportedly Skipped
- Officer's Body Camera Stopped On The Roof (Claims)
- Cover-Up Indicators
- Alleged Patsies and Distraction Actors (Claims)
- Stairs Guy Identity Gap
- FBI Investigation
- Preliminary Hearing Day 4 — July 9, 2026
- Preliminary Hearing Day 5 — July 10, 2026
- Bind-Over Oral Argument — September 1, 2026
- Court Document Archive
- The Day-One Track
- Two Tracks Compared
- Cover Up (Possible)
- Proof Not Tyler
- FBI Discovery Delays
- Witness Interviews Reportedly Blocked
- Joe Kent And The Halted Foreign-Lead Review
- Miranda And Custody Timing Hub
- Preliminary Hearing
- Score Card
:::danger Theoretical Exercise Only This page is a theoretical exercise. It is a written simulation of how an idealised defense attorney might approach this case. We make no claim that there is any problem with the current defense attorney, with any member of the defense team, or with any decision they have made.
Real capital defense is conducted under a gag order, with sealed filings, and on the basis of full discovery that the public has never seen. Counsel of record know facts we do not. A step described here as "not on the public record" may already have been taken privately, may have been considered and rejected for good reason, or may not yet be due at this stage of the case. Silence in the public record is not evidence of a failure.
Nothing here is legal advice, a criticism of any licensed attorney, or an allegation of professional misconduct. :::
This website's author is @HolonCitizen on X and YouTube/@HolonCitizen. Follow me there.