AFFINITY MINE
MSHA mine ID 4608878 · Raleigh County, WV
- Operator
- Pocahontas Coal Company LLC
- Controller
- Metinvest B V
- Mine status
- Active since Feb 1, 2016
- Mine type
- Underground
- Primary commodity
- Coal (Bituminous)
- Citations issued
- Oct 22, 2024 to Oct 6, 2026
Past 24 months at a glance
- Inspections
- 130
- Citations and orders
- 480
- Marked S&S by MSHA
- 58
- Assessed penalties
- $183,445
450 of 480 citations have an MSHA assessment so far, first proposed at $197,322. 0 are marked contested.
Citations by standard
The 30 CFR section MSHA cited, most cited first.
| Standard | Citations | Assessed |
|---|---|---|
| 75.370(a)(1) | 62 | $39,810 |
| 75.400 | 61 | $14,695 |
| 75.403 | 47 | $37,036 |
| 75.202(a) | 33 | $17,891 |
| 75.220(a)(1) | 32 | $12,561 |
| 75.503 | 26 | $5,069 |
| 75.512 | 20 | $3,617 |
| 75.1403 | 15 | $4,171 |
| 72.630(b) | 13 | $2,482 |
| 75.604(b) | 11 | $4,109 |
| 75.1731(a) | 8 | $1,208 |
| 75.1725(a) | 6 | $1,643 |
| 75.1731(b) | 6 | $604 |
| 75.342(a)(4) | 6 | $906 |
| 75.380(d)(7)(vi) | 6 | $1,080 |
| 75.517 | 5 | $5,792 |
| 75.1100-2(b) | 4 | $604 |
| 75.1100-3 | 4 | $662 |
| 75.1600-2(e) | 4 | $885 |
| 75.350(a)(2) | 4 | $604 |
| 75.363(b) | 4 | $2,413 |
| 75.701 | 4 | $1,258 |
| Not listed | 4 | $403 |
| 75.1101-10 | 3 | $418 |
| 75.1722(a) | 3 | $386 |
Latest citations
| Issued | Assessed |
|---|---|
| Oct 6, 2026 No. 5027040 75.370(a)(1) | Not yet assessed |
| Sep 29, 2026 No. 5029467 75.360(g) | Not yet assessed |
| Sep 22, 2026 No. 5029466 75.400 | Not yet assessed |
| Sep 21, 2026 No. 5029465 75.220(a)(1) | Not yet assessed |
| Sep 21, 2026 No. 5029464 75.370(a)(1) | Not yet assessed |
| Sep 21, 2026 No. 5029463 75.1403 | Not yet assessed |
| Sep 15, 2026 No. 5029462 75.503 | Not yet assessed |
| Sep 15, 2026 No. 5029461 75.400 | Not yet assessed |
| Sep 15, 2026 No. 5029460 75.523-3(b)(5) | Not yet assessed |
| Sep 14, 2026 No. 5029459 75.220(a)(1) | Not yet assessed |
| Sep 9, 2026 No. 5029458 75.220(a)(1) | Not yet assessed |
| Sep 9, 2026 No. 5029457 75.202(a) | Not yet assessed |
| Sep 8, 2026 No. 5183644 75.370(a)(1) | Not yet assessed |
| Sep 8, 2026 No. 5029456 75.1722(a) | Not yet assessed |
| Sep 8, 2026 No. 5029455 75.370(a)(1) | Not yet assessed |
| Sep 8, 2026 No. 5029454 75.351(k) | Not yet assessed |
| Sep 8, 2026 No. 5029453 75.1731(b) | Not yet assessed |
| Sep 4, 2026 No. 5027023 75.370(a)(1) | Not yet assessed |
| Sep 2, 2026 No. 5180094 75.400 | Not yet assessed |
| Sep 2, 2026 No. 5180093 75.400 | Not yet assessed |
| Sep 2, 2026 No. 5180092 75.400 | Not yet assessed |
| Sep 2, 2026 No. 5180091 75.400 | Not yet assessed |
| Sep 2, 2026 No. 5180090 75.1101-10 | Not yet assessed |
| Sep 2, 2026 No. 5028368 75.1400-3(b)(3) | Not yet assessed |
| Sep 1, 2026 No. 5029452 75.220(a)(1) | Not yet assessed |
Latest inspections
103(i) Spot Inspections
Event F03FD97
Oct 6, 2026
Verbal Hazard Complaint Inspections
Event F034305
Oct 3, 2026
Regular Safety and Health Inspection
Event F011303
Oct 1, 2026
103(i) Spot Inspections
Event 6322042
Sep 29, 2026
Spot Inspection
Event F020DCA
Sep 23, 2026
103(i) Spot Inspections
Event 6322041
Sep 16, 2026
103(i) Spot Inspections
Event F03FD92
Sep 8, 2026
103(i) Spot Inspections
Event F00C0C3
Aug 25, 2026
103(i) Spot Inspections
Event F00C0C1
Aug 18, 2026
103(i) Spot Inspections
Event F00C0BF
Aug 13, 2026
Get an alert when MSHA cites AFFINITY MINE 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.