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 / PATROL

Case Journey

PATROL

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

County

Gallatin County

Started

2026-02-18

Latest Update

02/18/26 17:11:19

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

Meadow Village

Timeline

dispatch record

PATROL

exact · 94/100

2026-02-18

SAYS SHE LOVES TO SHARE FOOD WITH THE GAL AT THE DELI BELIEVES THE "FAT GUY" THAT GOT OUT OF THE RV IS SELLING DRUGS HER SMOKE DETECTOR AND FIRE ALARM HAVE BEEN TAMPERED WITH THE RV IS GONE BECAUSE HER PHONE IS TAMPERED WITH AND WHEN SHE MADE THE CALL THE RV LEFT INCLUDING THE WOMAN THAT USED TO SHOWER AT THE GYM AND USED TO COME OUT CRAZY INFORMED HER OF THE PENDING EVICTION NOTICE AND SHE IMMEDIATELY REFERRED TO HER DESIRE TO MAKE A REPORT TO MONTANA POST SAYS SHE ALREADY HAS THE PAPERWORK TO FILE THE POST COMPLAINT THE BIGGEST ISSUE IS 627 BECAUSE HE WANTS TO SERVE THE PAPERWORK QUICKLY BELIEVES 627 CALLED BECAUSE SPEAKING WITH HER WOULD BE AIDING AND ABETTING

Why this is linked: Primary Montana Blotter incident record.

command log

Hennessey, James

exact · 100/100

02/18/26 16:17:16

SKETCHY BC NO LIC

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

command log

Hennessey, James

exact · 100/100

02/18/26 16:17:46

EYEBALLS ARE OVERLY STIMULATED

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

command log

Hennessey, James

exact · 100/100

02/18/26 16:19:14

UNK WHERE THE M IS RIGHT NOW

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

command log

Hennessey, James

exact · 100/100

02/18/26 16:19:19

RV IS STILL PARKED IN FRONT OF HOUSE

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

command log

Hennessey, James

exact · 100/100

02/18/26 16:19:27

DK BRO HAIR

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

command log

Hennessey, James

exact · 100/100

02/18/26 16:19:28

GREEN COAT

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

command log

Hennessey, James

exact · 100/100

02/18/26 16:19:41

5' 7''

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

command log

Hennessey, James

exact · 100/100

02/18/26 16:19:52

30'S YO

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

command log

Hennessey, James

exact · 100/100

02/18/26 16:19:59

WHI M

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:00:09

SAYS SHE LOVES TO SHARE FOOD WITH THE GAL AT THE DELI

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:00:37

BELIEVES THE "FAT GUY" THAT GOT OUT OF THE RV IS SELLING DRUGS

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:00:54

SAYS SHE GOT THE SHIVERS WHEN HE LOOKED AT HER

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:01:16

SAYS THE "FAT GUY'S" EYES WERE BULGING OUT

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:01:53

HER SMOKE DETECTOR AND FIRE ALARM HAVE BEEN TAMPERED WITH

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:02:14

SAID SHE CALLED AND NOTIFIED THE FD

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:02:28

THE SMOKE ALARM IS CHIRPING

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:03:10

THE RV IS GONE BECAUSE HER PHONE IS TAMPERED WITH AND WHEN SHE MADE THE CALL THE RV LEFT

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:04:03

EVERYONE IS ASSOCIATED WITH THE RV

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:04:26

INCLUDING THE WOMAN THAT USED TO SHOWER AT THE GYM AND USED TO COME OUT CRAZY

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:07:38

INFORMED HER OF THE PENDING EVICTION NOTICE AND SHE IMMEDIATELY REFERRED TO HER DESIRE TO MAKE A REPORT TO MONTANA POST

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:07:55

SHE WOULD RATHER GO THE "SHERLOCK HOLMES ROUTE"

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:09:10

SAYS SHE ALREADY HAS THE PAPERWORK TO FILE THE POST COMPLAINT

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:10:11

THE BIGGEST ISSUE IS 627 BECAUSE HE WANTS TO SERVE THE PAPERWORK QUICKLY

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

command log

Stubblefield, Matthew

exact · 100/100

02/18/26 17:11:19

BELIEVES 627 CALLED BECAUSE SPEAKING WITH HER WOULD BE AIDING AND ABETTING

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