Montana Public Records Initiative

An official website of the Montana Public Records Initiative

Support Coverage Get Alerts

Statewide Public Records Access

Montana County, City, Jail, Warrant, and Court Lookup

The Montana Blotter
Montana Public Records Directory
Montana Blotter / Case Journeys / ASSAULT

Case Journey

ASSAULT

Montana Blotter captured 24 follow-up log entries after the initial record.

County

Gallatin County

Started

2026-02-17

Latest Update

02/17/26 09:09:55

Active timeline 25 public steps exact link confidence CFS CFS26-023620

Colter Trl

Timeline

dispatch record

ASSAULT

exact · 94/100

2026-02-17

IS WANTING TO LEAVE BECAUSE PARENTS ARE MAKING HIM GO TO SCHOOOL SRO TRANSPORTED THE JUVENILE TO SCHOOL AND CONNECTED THE STUDENT WITH THE COUNSELOR FOR A PLAN MOVING FORWARD. PARENTS DIDN'T WANT ANY

Why this is linked: Primary Montana Blotter incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:16:08

15 YEAR OLD SON IS TRYING TO RUN AWAY

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:16:21

SON-

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:16:28

IS BEING PHYSICALLY AGGRESSIVE

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:16:32

PUSHING AND SHOVING RP

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:16:34

IS SCREAMING

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:16:47

MALE IS RIGHT IN FRONT OF RP

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:16:54

IS WANTING TO RUN AWAY

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:16:59

KNIVES AND GUNS IN THE HOUSE

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:17:12

PARTIES ARE ARGUING ABOUT MALE LEAVING

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:17:41

NO ONE ELSE IN THE HOUSE

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:18:13

MALE JUST LEFT

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:18:23

LEAVING IN A DODGE CHARGER BLACK

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:18:42

LIC- TEMP

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:19:35

IS WANTING TO LEAVE BECAUSE PARENTS ARE MAKING HIM GO TO SCHOOOL

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:19:49

MALE IS SITTING IN CAR WITH IT IN REVERSE

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:20:02

RP IS STANDING BEHIND VEH

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:20:17

DISPATCH ADV RP TO MOVE

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:20:27

RP DOESNT DOUBT HE WOULD TRY AND HIT RP WITH CAR

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:22:05

MALE IS SLOWLY BACK UP TRYING TO GET RP TO MOVE

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:22:24

JUST PUSHED RP OUT OF THE WAY

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:22:50

MALE JUST LEFT

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:23:06

IS ON COLTER TRL

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Hartman, Kate

exact · 100/100

02/17/26 08:23:12

WILL GET ONTO KIDD RD

Why this is linked: Direct command-log entry tied to the same incident record.

command log

Mayland, Dan

exact · 100/100

02/17/26 09:09:55

SRO TRANSPORTED THE JUVENILE TO SCHOOL AND CONNECTED THE STUDENT WITH THE COUNSELOR FOR A PLAN MOVING FORWARD. PARENTS DIDN'T WANT ANY

Why this is linked: Direct command-log entry tied to the same incident record.

Editorial Standards

Montana Blotter is designed to make public records and public meeting information easier to access. It is not a government office, and it does not replace official notice, clerk records, court files, or agency databases.

1. Primary Source Rule
We prefer direct links to official county, city, court, sheriff, police, and state judiciary pages. Where possible, each page should point readers back to the original public record, agenda, minutes page, or official document listing.

2. What We Standardize
Date and time formatting — location and body-name labeling — document labels such as agenda, packet, or minutes — searchable statewide filters and metadata.

3. What We Do Not Claim
We do not claim to be the official keeper of public records. We do not guarantee that a third-party government site is complete, current, or correctly maintained. We do not treat summaries or extracted text as a substitute for the official source file.

4. Update Cadence
Automated sources are checked on a recurring basis. If a source is stale, broken, or moved, the originating public body remains the authoritative reference until the source is repaired.

5. Provenance and Visibility
We aim to show where information came from, when it was last refreshed, and how users can verify it.

6. Redactions and Sensitive Material
We may review records for obvious sensitivity, legal restrictions, or redaction issues. The existence of a public record does not automatically mean every field or derivative presentation should be amplified without review.

7. Corrections
If a source link breaks, a meeting is mislabeled, a record is duplicated, or a page needs clarification, see the Corrections Policy for the reporting workflow.

8. Government and Clerk Communications
If you work for a Montana public body and need a source updated, corrected, or removed, contact us directly. We prefer exact URLs, dates, and a brief explanation of the change.

9. Contact
Montana Blotter — records@montanablotter.com

Read full standards →

Corrections Policy

We want corrections requests to be specific, easy to verify, and fast to act on. The more concrete the report, the faster it can be reviewed.

1. What To Report
Broken official source links — moved agenda or minutes pages — incorrect meeting date, body name, or location label — duplicate records or meetings — stale source pages — material factual errors in a summary or description.

2. What To Include
The exact Montana Blotter URL — the exact official source URL that should be used — a short description of what is wrong — if timing matters, the date and time the official source changed.

3. Where To Send It
Email records@montanablotter.com with subject line Correction Request or Source Update. If you represent a government office, say so in the message.

4. Review Standard
We review corrections against the official source when available. If a report cannot be verified, we may ask for a clarifying URL, screenshot, or exact document reference before changing the page.

5. Response Goal
Our goal is to review straightforward source and labeling issues within two business days. Complex disputes, legal issues, and record-sensitivity questions may take longer.

6. How Fixes Are Handled
Broken or moved source URLs are updated at the source-config level when possible. Mislabeled dates, titles, or locations are corrected in the public presentation. If a government source removes or replaces a document, the official source controls.

7. Limits
A correction request does not automatically guarantee removal. Montana Blotter may preserve accurate public-record references while updating labels, links, timestamps, or explanatory text.

Read full corrections policy →

Montana Laws Reference
More

Bail = Bail Bonds · Cases = Case Journeys · Missing = Missing Persons

Courts Meetings Jails Bail Cases Missing Subscribe Support Sign In Join