@proseid v2026.07.26 US

PHMSA hazardous-material incident reporting determination

Determines whether a transportation incident requires a National Response Center call within 12 hours, DOT Form F 5800.1 within 30 days, an FAA copy, a one-year update, and two-year retention.

Compatible with

FormGuided assessmentDeterminationCompliance checklistAPI

Use Schema in a Flow

Publication

Protocol: Proseid_v1.0
Version: v2026.07.26
Applies in: United States
Fields: 32
Flow price: $0.20
Publisher fee: None

Legal history

Time periods

phmsa_20262026-01-01 → continues indefinitely

Current

Controlling sources

Legal references

Hazardous Materials Regulations 49 CFR §§ 171.15–171.16

Source ↗

PHMSA Incident Reporting guidance DOT Form F 5800.1

Source ↗

Schema fields

32 fields

Field

Type

Description

Req

Person or business in physical possession of the material

String

—

Req

Reason the National Response Center call was late

String

—

Opt

There was a discharge of any quantity of hazardous waste

Boolean

—

Req

A marine pollutant release exceeded 450 litres of liquid or 400 kilograms of solid material

Boolean

—

Req

The situation is serious enough that immediate reporting is appropriate

Boolean

—

Req

Reason DOT Form F 5800.1 was late

String

—

Opt

A specification cargo tank of at least 1,000 gallons suffered reportable structural damage

Boolean

—

Req

The event occurred during transportation, loading, unloading, or temporary storage

Boolean

—

Req

The National Response Center was called as soon as practical and within 12 hours

Boolean

—

Opt

A report copy will be retained for two years

Boolean

—

Opt

A battery or battery-powered device directly caused a fire, violent rupture, explosion, or dangerous heat

Boolean

—

Req

A one-year update trigger occurred

Boolean

—

Req

Documented written-report exception

Select

Choices: None, Authorized vent or routine equipment minimal release, Qualifying small package release, Undeclared passenger baggage at airport screening

Req

The event involved the specified radioactive or infectious-material fire, breakage, spill, or suspected contamination

Boolean

—

Req

There was an unintentional hazardous-material release

Boolean

—

Req

The general public was evacuated for one hour or more

Boolean

—

Req

A hazardous material regulated by the HMR was involved

Boolean

—

Req

A person died or was admitted to a hospital as a direct result of the hazardous material

Boolean

—

Req

The updated incident report was submitted within one year of the incident

Boolean

—

Opt

Reason the updated incident report was late

String

—

Opt

A major transportation route or facility was closed for one hour or more

Boolean

—

Req

Incident date

Date

—

Req

An undeclared hazardous material was discovered

Boolean

—

Req

The required updated incident report has been submitted

Boolean

—

Opt

The report is at the principal place of business or can be made available there within 24 hours

Boolean

—

Opt

The operational flight pattern or routine of an aircraft was altered

Boolean

—

Req

A copy was submitted to the appropriate FAA regional office

Boolean

—

Opt

Calculated reporting position

Select

Choices: Outside hmr incident scope, Call nrc within 12 hours, Document late nrc call, File form 5800 1 within 30 days, Document late form 5800 1, Send faa copy, File one year update, Document late one year update, Complete retention control, Incident reporting record current

Opt

DOT Form F 5800.1 has been submitted

Boolean

—

Opt

The National Response Center call has been completed

Boolean

—

Opt

DOT Form F 5800.1 was submitted within 30 days of discovery

Boolean

—

Opt

The incident involved transportation by aircraft

Boolean

—

Req

Example payload

JSON

{
  "responses": {
    "reporting_entity": "",
    "nrc_call_delay_reason": "",
    "hazardous_waste_discharge": false,
    "large_marine_pollutant_release": false,
    "other_serious_situation_should_be_reported": false,
    "form_5800_1_delay_reason": "",
    "large_cargo_tank_structural_damage": false,
    "during_transportation": false,
    "nrc_call_completed_within_12_hours": false,
    "two_year_retention_arranged": false,
    "battery_fire_rupture_explosion_or_dangerous_heat": false,
    "one_year_update_trigger": false,
    "written_report_exception_basis": "",
    "radioactive_or_infectious_material_event": false,
    "unintentional_hazardous_material_release": false,
    "public_evacuated_one_hour_or_more": false,
    "hazardous_material_involved": false,
    "death_or_hospital_admission": false,
    "updated_report_submitted_within_one_year": false,
    "updated_report_delay_reason": "",
    "major_route_or_facility_closed_one_hour_or_more": false,
    "incident_date": "",
    "undeclared_hazardous_material_found": false,
    "updated_report_submitted": false,
    "report_available_at_principal_place_within_24_hours": false,
    "aircraft_operation_altered": false,
    "faa_copy_submitted": false,
    "form_5800_1_submitted": false,
    "nrc_call_completed": false,
    "form_5800_1_submitted_within_30_days": false,
    "aircraft_incident": false
  },
  "effective_at": "2026-07-26"
}

The request body this schema expects. Fill in responses and keep the field IDs unchanged. Validation becomes callable after you use this release in a published Flow.

API usage

Create a Flow from this schema, then replace the route placeholders with that Flow's organization and address. Validation is free and runs against the exact release bound to the Flow. It returns the engine's resolved fields and legal time period when ready, or a structured error with field-level issues.

cURL

curl -X POST https://proseid.com/api/v1/validate/{your-org}/{flow-slug} \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d @payload.json

200 OK

{
  "valid": true,
  "status": "READY",
  "definitions": { ... },
  "issues": [],
  "effective_at": "2026-07-19",
  "temporal_context": {
    "logic_version": "current",
    "valid_range": ["2026-01-01", null]
  }
}

422 Invalid

{
  "error": {
    "code": "validation_failed",
    "message": "the document did not pass validation",
    "details": {
      "status": "INCOMPLETE",
      "issues": [{
        "field_id": "reporting_entity",
        "kind": "missing_required",
        "severity": "error",
        "trigger": "completion",
        "message": "Required field is missing"
      }]
    }
  }
}

A completed webhook also depends on the Flow's experience, signing, pricing, and delivery settings. Create a Flow with this schema, then use Send sample completion in its delivery settings to receive the full signed JSON without using your balance. Webhook guide

Published versions

Permanent, attributable versions

Loading published versions…

Trust ledger

Crowd → credentialed

Provenance

Community publisher (unverified)

@proseid · latest v2026.07.26

Community signal

0 votes

No votes yet.

Attestations · by version

0 total

No attestations yet. A verified professional can vouch for a specific version.

Discussion

0 comments

to join the discussion.

Time periods

Legal references

Schema fields

Example payload

API usage

Published versions

Trust ledger

Discussion

FDA food-facility registration determination

EU right-of-withdrawal record

EU whistleblowing internal-report deadlines

OSHA fatality or severe-injury reporting determination