MSHA public records

Stone Splitters #3

MSHA mine ID 3402084 · Haskell County, OK

Operator
Stone Splitters #3
Controller
Jamie Fargo
Mine status
Active since Apr 16, 2013
Mine type
Surface
Primary commodity
Dimension Sandstone
Citations issued
Dec 18, 2025 to Oct 1, 2026

Past 24 months at a glance

Inspections
6
Citations and orders
2
Marked S&S by MSHA
0
Assessed penalties
$151

1 of 2 citations have an MSHA assessment so far, first proposed at $151. 0 are marked contested.

Citations by standard

The 30 CFR section MSHA cited, most cited first.

StandardCitationsAssessed
47.41(a)1$0
56.23003(b)1$151

Latest citations

IssuedAssessed
Oct 1, 2026

No. 5041816

47.41(a)

Not yet assessed
Dec 18, 2025

No. 5041424

56.23003(b)

$151

Closed

Latest inspections

  • Regular Safety and Health Inspection

    Event F031ACE

    Oct 1, 2026 to Oct 7, 2026

  • Regular Safety and Health Inspection

    Event F025970

    Apr 8, 2026

  • Regular Safety and Health Inspection

    Event F025955

    Dec 18, 2025 to Dec 19, 2025

  • Special Emphasis Programs

    Event F018AE9

    Jul 10, 2025 to Jul 11, 2025

  • Regular Safety and Health Inspection

    Event F018ADA

    May 7, 2025 to May 8, 2025

  • Regular Safety and Health Inspection

    Event F016010

    Dec 19, 2024 to Dec 20, 2024

Get an alert when MSHA cites Stone Splitters #3 again

MineCitation checks MSHA data every day and emails new citations, S&S violations, penalties and ownership changes in the states and mine types you choose.

About this record

These figures come from public Mine Safety and Health Administration (MSHA) open government data on mines, inspections, violations and assessed violations. MineCitation copies them as published and does not add findings of its own.

A citation records a condition an MSHA inspector found. Operators can contest citations and penalties, and amounts can change after review. MineCitation is not legal advice.

See something that does not match MSHA's records? Email support@minecitation.com with the mine ID and we will check it against the source data.