@pipeworx/fra-rail-safety

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/fra-rail-safety’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 3

US railroad accidents, derailments and highway-rail grade crossing collisions reported to the Federal Railroad Administration, 1975 to the present: railroad, FRA cause code, location, casualties and damage per report, plus grouped counts.

Tools

• rail_accidents(year?, state?, railroad?, cause_code?, accident_type?, min_damage_usd?, limit?) — individual rail equipment accident reports (derailments, collisions, obstructions, fires), newest first, with the reporting railroad, accident type, FRA primary and contributing cause code and text, state/county, train speed, hazmat cars released, people evacuated, killed, injured, damage cost and a link to FRA’s own report page.
• crossing_incidents(state?, county?, city?, year?, railroad?, crossing_id?, highway_user?, fatal_only?, limit?) — collisions between trains and road users at railroad crossings, newest first, with the USDOT crossing id, road name, road user type and action, vehicle and train speed, warning devices, weather, killed and injured.
• rail_accident_summary(group_by, dataset?, year?, from_year?, state?, railroad?, limit?) — counts and casualty/damage totals grouped by railroad, cause, accident type, state, year or road user, for either dataset.

Auth

Keyless.

Data sources

• Federal Railroad Administration, Office of Safety Analysis — Rail Equipment Accident/Incident Data (Form 54).
• Federal Railroad Administration, Office of Safety Analysis — Highway-Rail Grade Crossing Incident Data (Form 57).

Both are published by the US Department of Transportation and queried live on each call. US federal government work, public domain.

Things worth knowing:

• One row per railroad report, not per accident. An accident involving two railroads (joint operations, trackage rights) is filed once by each. FRA’s unique-accident count keys on the incident key; rail_accident_summary reports both accidents (distinct) and railroad_reports.
• Railroad filter: 1-4 character input is matched against the reporting mark exactly (NS, UP, BNSF, CSX, ATK); longer input is a name substring (Norfolk Southern). A substring match on a reporting mark is wrong — NS occurs inside “CSX TRANSPORTATION”.
• State fields differ between the datasets: accidents carry a two-letter code, crossings only the upper-case full name. The pack accepts either form and translates.
• Lag: railroads file monthly and FRA publishes a few months behind, so the current year is partial.
• Cause codes are FRA’s: the first letter is the family (T track, S signal, H human factors, E equipment, M miscellaneous); cause_code matches a prefix.

Tools

• rail_accidents — US train accidents and derailments reported to the Federal Railroad Administration (FRA Form 54, 1975–present).
• crossing_incidents — Highway-rail grade crossing collisions in the US — trains striking cars, trucks, pedestrians and cyclists at railroad crossings
• rail_accident_summary — Counts and totals of FRA-reported US railroad accidents or grade crossing incidents, grouped by railroad, cause, accident type,