Dataset Factory★ EST. 2026 · BEST AT 800×600 ★
★ WELCOME TO THE DATASET FACTORY ★ PUBLIC DATA → CHECKED BUILDS → HONEST BASELINES ★ NO POP-UPS ★ NO COOKIES ★ NO TRACKERS ★ HAND-MADE HTML ★ UNDER CONSTRUCTION SINCE THE NINETIES ★
Release notes · 2026-11-13 · announcement

Phmsa Pipeline Penalty Reduction

Suitability and evaluation

Evaluation setting: retrospective research. Read the prediction setting and limitations below. Public validation is development data; downloadable holdout labels must stay outside the evaluated agent workspace.

Will a PHMSA Notice of Probable Violation with a proposed civil penalty be closed within 36 months with a lower assessed penalty than proposed?

Population: NOPV cases with positive Proposed_Penalties and nonmissing Notice_Sent_Date from 2002-01-01 through 2023-06-30; deduplicated to earliest NOPV per WMS_Activity_Seq. Eligibility uses only decision-time information.

Target: y=1 iff the case has a nonmissing Closed_Date no later than 36 months after Notice_Sent_Date and Assessed_Penalties is nonmissing and strictly less than Proposed_Penalties (zero counts as elimination); otherwise y=0, including cases not closed with a reduction by 36 months. Closed cases with missing Assessed_Penalties are coded 0, not imputed.

Prediction time: Notice_Sent_Date, before the operator response, hearing or any order.

Splits: Fixed chronological boundaries by Notice_Sent_Date: train 2002-01-01 to 2016-12-31; evaluation 2017-01-01 to 2019-12-31; holdout 2020-01-01 to 2023-06-30. No embargo is needed because no lagged outcomes, rolling histories, operator histories, or future case records are used; related cases are deduplicated by WMS_Activity_Seq before splitting.

Outcome horizon: 36 months after Notice_Sent_Date; holdout notices end 2023-06-30, so all outcomes are observable by 2026-06-30 against the 2026-11-03 extract

Inputs: proposed_penalty_usd: Proposed civil penalty in dollars stated in the Notice of Probable Violation.; violation_category_count: Number of nonempty comma-separated violation categories in Violation_Category.; cited_regulation_count: Number of distinct nonempty regulation codes in Cited_Regulations.; integrity_management_flag: Whether Violation_Category includes Integrity Management.; pipeline_type: Pipeline segment type associated with the enforcement case, such as INTERSTATE LIQUID or INTERSTATE GAS TRANSMISSION.; region: PHMSA region that initiated the enforcement case.; discovery_route: How the case was discovered, such as Integrated, Specialized, Failure Investigation, Construction, SRCR or PA Program.; notice_actions: Notice action codes such as CO, CP, CO/CP, WI or NOA.; proposed_compliance_order: Whether a compliance order was proposed with the case.

→ Open the dataset page for numbers, files and checksums

★ THANKS FOR VISITING · BOOKMARK THIS PAGE · TELL A FRIEND ABOUT THE DATASET FACTORY · SIGN THE GUESTBOOK BEFORE YOU LEAVE ★