PHMSA Pipeline Enforcement Cases
Pricing
from $3.00 / 1,000 phmsa enforcement case rows
PHMSA Pipeline Enforcement Cases
Monitor official PHMSA pipeline enforcement cases and export structured rows for NOPV, warning letters, notices, orders, penalties, operators, and dates. Unofficial public-record scraper.
Pricing
from $3.00 / 1,000 phmsa enforcement case rows
Rating
0.0
(0)
Developer
Defenestrator
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
0
Monthly active users
6 hours ago
Last modified
Share
Export official PHMSA pipeline-safety enforcement case rows into a structured, source-linked Apify dataset for regulatory monitoring, compliance research, infrastructure risk review, insurance research, and legal/regulatory triage.
This Actor reads PHMSA public enforcement-data page JSON and defaults to Notices of Probable Violation (NOPV). It can also include Warning Letters (WL), Notices of Amendment (NOA), Corrective Action Orders (CAO), and Safety Orders (PSO).
Unofficial / not affiliated: this Actor is not operated by, endorsed by, or affiliated with PHMSA, the U.S. Department of Transportation, or any government agency.
Common use cases
| Use case | Why it helps |
|---|---|
| Pipeline-safety monitoring | Track new or open enforcement cases from the public PHMSA source. |
| Compliance triage | Filter by case type, status, year, region, operator, or proposed penalty. |
| Infrastructure risk research | Export normalized rows for repeatable review and downstream analysis. |
| Insurance / legal research | Create source-linked datasets before manual document review. |
| Regulatory watchlists | Run bounded scheduled checks for specific operators or regions. |
Example input
{"maxItems": 25,"caseTypes": ["NOPV"],"statuses": ["OPEN"],"openedYearFrom": 2025,"minProposedPenaltyUsd": 1}
Input fields
| Field | Notes |
|---|---|
maxItems | Maximum rows to save, 1–1000. |
caseTypes | One or more of NOPV, WL, NOA, CAO, PSO; defaults to NOPV. |
statuses | Optional OPEN / CLOSED filter. |
openedFrom, openedTo | Optional YYYY-MM-DD opened-date bounds. |
openedYearFrom, openedYearTo | Optional opened-year bounds. |
region | Optional case-insensitive PHMSA region filter. |
operatorSearch | Optional case-insensitive filter on operator name or CPF number. |
minProposedPenaltyUsd | Optional minimum proposed civil penalty. |
includeRawFields | Optional sanitized source-field debugging output when enabled. |
Output
Each dataset row includes:
- PHMSA CPF number / record key
- case type and status
- opened and closed dates
- operator name and operator ID
- PHMSA region
- proposed, assessed, and collected penalty amounts
- final-order / consent-order dates when present
- source URL and collection timestamp
Source
Official source: https://primis.phmsa.dot.gov/enforcement-data
PHMSA notes that enforcement data is intended to enhance public understanding, is updated as cases are initiated or resolved, and historical totals may change over time. The source search may not retrieve every document associated with every enforcement action. Use this Actor for monitoring and triage, then verify important decisions against official PHMSA records.
Pricing
from $3.00 / 1,000 PHMSA pipeline enforcement case rows
This Actor uses Apify Pay per Event pricing with platform usage included. The row event is charged only for useful rows written to the default dataset.
| Event | Price | Unit |
|---|---|---|
Actor start (apify-actor-start) | $0.00005 | Once when the run starts. |
PHMSA Enforcement Case Row (apify-default-dataset-item) | $0.003 | Per PHMSA pipeline enforcement case row. |
A row is one PHMSA pipeline enforcement case row. Apify plan discounts, user-configured max-charge limits, and any future Apify pricing UI changes may affect final charges.
Limitations and responsible use
- This output is not legal, regulatory, investment, safety, or compliance advice.
- Do not rely on the dataset as the sole basis for legal/regulatory decisions, public accusations, unsolicited mass outreach, or automated adverse actions.
- PHMSA records can change as cases progress; verify high-stakes findings against the official source.
- No browser, proxy, login, private API, external paid API, or LLM is used. The Actor performs bounded HTTPS requests to official public PHMSA data and writes normalized rows.
Related Actors in this portfolio
This Actor is part of the Public risk and enforcement monitors group. These are narrow, source-specific Apify Actors intended for scheduled checks and repeatable dataset exports — not broad scraped-content feeds.
- Texas Data Breach Reports Scraper — Official Texas data-breach notice rows for cybersecurity/compliance monitoring.
- OSHA Severe Injury Reports Scraper — Official OSHA severe-injury report rows for workplace-safety research.
- CFPB Enforcement Actions Monitor — Official CFPB enforcement-action rows for financial regulatory monitoring.
- PHMSA Pipeline Enforcement Cases — Official PHMSA pipeline enforcement case rows for safety/compliance monitoring.
Each listing includes its own source notes, limits, pricing, and responsible-use caveats. Use the official source links in each Actor when decisions require verification.