MSHA Mines Data Set

For mines associated through current operator or controller identifiers, the nationwide MSHA full file reports Mine ID, name, type, and location; current status and status date; days per week, hours per shift, and production and maintenance shifts; average mine height; mine-gas category and methane liberation; producing and nonproducing pit counts, multiple-pit and tailing-pond indicators; pillar-recovery and highwall-miner use; portable-operation status; and miners’ representative and safety-committee indicators. It is primary governmental evidence for the mine-specific operating and physical-hazard profile, subject to field applicability, commodity-specific definitions, null values, retrieval-date pinning, and the rule that controller attribution does not prove ownership.

For each mine associated through CURRENT_OPERATOR_ID and CURRENT_OPERATOR_NAME, MSHA reports coal-versus-metal/non-metal classification, primary and secondary SIC codes and descriptions, canvass industry groups, and primary and secondary commodities. This directly supports regulator-attributed mining activity and classification, bounded to the organisation’s MSHA-covered mine operations. It does not prove that every classified activity is current; retain raw codes, descriptions, mine-status context, and retrieval date.

CURRENT_OPERATOR_ID and CURRENT_OPERATOR_NAME, CURRENT_MINE_STATUS, CURRENT_STATUS_DT, and the reported operating-schedule fields provide a regulator-held, dated external signal that the resolved organisation operates an active, intermittent, nonproducing, idled, new, or abandoned mine. This mining-operation signal does not establish the organisation’s complete legal or commercial operating status or activity outside MSHA-covered mines; retain the status date, retrieval date, and missing values.

The nationwide MSHA full file pairs CURRENT_OPERATOR_ID and CURRENT_OPERATOR_NAME with Mine ID, current mine name and type, state and county, coordinates, current mine status, and CURRENT_STATUS_DT. It therefore strongly supports a dated regulator-observed mine-location footprint for a resolved operator, but not a complete organisation footprint, mine ownership, or brand affiliation. Retain the retrieval date and status date, and preserve null location values.

The schema pairs CURRENT_CONTROLLER_ID and CURRENT_CONTROLLER_NAME with CURRENT_OPERATOR_ID and CURRENT_OPERATOR_NAME and defines the controller as a legal entity acting as controller of the operator; CURRENT_CONTROLLER_BEGIN_DT records the associated operating-period start. This supports only a regulator-recorded controller-to-operator affiliation when both resolved parties are organisations. It does not establish parent/subsidiary status, equity, beneficial ownership, or an exhaustive affiliation graph. Preserve direction, both IDs and names, the operating-period date where present, current-record and retrieval dates, and exclude rows where the controller resolves to a natural person.

For a mine associated with the resolved operator, CURRENT_103I supplies MSHA’s regulator-defined hazard or heightened-inspection classification, including 5-, 10-, or 15-day inspection-frequency statuses, and CURRENT_103I_DT dates entry into that status. This answers only the intervention-threshold-indicator slice of the leaf, not peer comparisons, rates, inspection results, incident history, or an organisation-wide aggregate; retain the regulator, raw classification, status date, retrieval date, and null values.