Environmental release occurrence and characteristics
What environmental release or potential release was officially reported for this event, and what material, quantity, cause, affected medium or receptor, location, and occurrence, discovery, or report dates were stated?
The data that answers it
Ranked by fit · best firstTCEQ's standing Socrata spill-notification endpoint publishes one row per incident tracking number with start and received dates, physical location and coordinates, potential source, material, amount and unit, classification, effect, nature, receiving water, responsible-party description, and incident narrative.
Illinois EPA's public incident tracker supplies incident number, name and type; incident start values; material and amount released; location and coordinates; responsible party; and comments.
The public statewide queryable and extractable layer identifies each oil-and-gas incident by incident number and publishes incident type, complaint and confirmation status, initial and investigation dates, coordinates, oil released and recovered, affected water body, and reported versus confirmed wildlife effects.
The public NC DEQ layer identifies each reported overflow or bypass by incident number and supplies report, start, and end dates; incident location and coordinates; released and waterbody-reaching volumes; affected waterbody; fish-kill indicator; cause; and facility context.
New York's published statewide archive explicitly contains reported petroleum and hazardous-material spills with unique Spill Number, facility and address, spill and received dates, source and contributing factor, affected waterbody, material name and family, quantity and units, and recovered amount. Preserve Spill Number grouping, material-row repetition, date meanings, zero-as-unknown quantity convention, missing coordinates, and archive coverage limits.
CT DEEP's public incident data supplies case identity, reported and release times, reported release location, substance and quantities in stated units, release type, affected waterbody and media, cause, and implicated party.
Ohio EPA's standing dataset identifies reported incidents by case number and publishes reported product, amount and unit, reported date, incident-site coordinates and locality, and associated waterway. Reports are not necessarily confirmed spills.
DNREC's standing public DERNS listing exposes event-level Release ID, release time, reported location or facility, released substance, extremely-hazardous indicator, and whether notification was issued.
Hawaii DOH's public iHEER API exposes hazardous-substance incident identity, case and release details, release and report dates, addresses, impact, and nested public location geometry. The public view may omit ongoing or coordinate-less incidents.
The combined public Active and Closed LAST reports key leaking-aboveground-storage-tank events by Leak # and publish tank, substance, capacity, county, affected-stream context, and suspected and confirmed release dates. RP Address is mailing, not leak-site, data.
Florida's queryable and exportable SWO hazardous-material and petroleum incident archive publishes incident ID/number/type/name, report and release dates, county, coordinates, address, chemical and CAS identifier, released amount, narrative, and report URL.
MassDEP describes more than 40,000 reported oil or hazardous-material releases and publishes RTN-keyed primary release information with linked chemical, location-type, and release-source files. Harvested primary fields also identify notification, category or classification, and the oil-or-hazardous-material indication. This is reported-release evidence; preserve notification basis and do not infer confirmed causation, exact quantity, or response outcome where absent.
Show 17 more sources+−
The standing NJDEP public-records archive identifies AFFF/firefighting-foam incident notifications by incident date, municipality, reported street or route, linked incident ID, and an aqueous-foam indicator.
The us_uscg_nrc/ga_incident_reports NRC full-file view supplies sequence key, potential-release flag, type, reported cause/narrative, incident date/time basis, and reported location. It is an overlapping initial, unvalidated notification view and supplies no response, closure, or tank-origin finding.
The us_uscg_nrc/incident_reports_al NRC full-file view supplies sequence key, potential-release flag, type, reported cause/narrative, incident date/time basis, and reported location. It is an overlapping initial, unvalidated notification view and supplies no response, closure, or tank-origin finding.
The us_uscg_nrc/incident_reports_az NRC full-file view supplies sequence key, potential-release flag, type, reported cause/narrative, incident date/time basis, and reported location. It is an overlapping initial, unvalidated notification view and supplies no response, closure, or tank-origin finding.
The us_uscg_nrc/incident_reports_ky NRC full-file view supplies sequence key, potential-release flag, type, reported cause/narrative, incident date/time basis, and reported location. It is an overlapping initial, unvalidated notification view and supplies no response, closure, or tank-origin finding.
The us_uscg_nrc/incident_reports_la NRC full-file view supplies sequence key, potential-release flag, type, reported cause/narrative, incident date/time basis, and reported location. It is an overlapping initial, unvalidated notification view and supplies no response, closure, or tank-origin finding.
The us_uscg_nrc/incident_reports_mn NRC full-file view supplies sequence key, potential-release flag, type, reported cause/narrative, incident date/time basis, and reported location. It is an overlapping initial, unvalidated notification view and supplies no response, closure, or tank-origin finding.
The us_uscg_nrc/incident_reports_mo NRC full-file view supplies sequence key, potential-release flag, type, reported cause/narrative, incident date/time basis, and reported location. It is an overlapping initial, unvalidated notification view and supplies no response, closure, or tank-origin finding.
The us_uscg_nrc/incident_reports_nj NRC full-file view supplies sequence key, potential-release flag, type, reported cause/narrative, incident date/time basis, and reported location. It is an overlapping initial, unvalidated notification view and supplies no response, closure, or tank-origin finding.
The us_uscg_nrc/incident_reports_pa NRC full-file view supplies sequence key, potential-release flag, type, reported cause/narrative, incident date/time basis, and reported location. It is an overlapping initial, unvalidated notification view and supplies no response, closure, or tank-origin finding.
The us_uscg_nrc/incident_reports_sc NRC full-file view supplies sequence key, potential-release flag, type, reported cause/narrative, incident date/time basis, and reported location. It is an overlapping initial, unvalidated notification view and supplies no response, closure, or tank-origin finding.
The us_uscg_nrc/incident_reports_wi NRC full-file view supplies sequence key, potential-release flag, type, reported cause/narrative, incident date/time basis, and reported location. It is an overlapping initial, unvalidated notification view and supplies no response, closure, or tank-origin finding.
The us_uscg_nrc/incident_reports NRC full-file view supplies sequence key, potential-release flag, type, reported cause/narrative, incident date/time basis, and reported location. It is an overlapping initial, unvalidated notification view and supplies no response, closure, or tank-origin finding.
The public case-level ArcGIS layer identifies petroleum-release events by composite RST_ID and PCNUM and publishes release-reported date, suspect-versus-confirm indicator, federal-regulated-tank indicator, release name, facility identifier, and agency classification fields. Unpublished material, quantity, cause, and receptor facets remain unclaimed.
The public statewide pollution-event layer identifies each report by PRP_REPORT_ID and publishes report-received and incident date-times, site name, address, and point geometry. Unpublished material, quantity, cause, and receptor facets remain unclaimed.
The us_uscg_nrc/wv_incident_reports NRC full-file view supplies sequence key, potential-release flag, type, reported cause/narrative, incident date/time basis, and reported location. It is an overlapping initial, unvalidated notification view and supplies no response, closure, or tank-origin finding.
Indiana's official queryable Spills layer returns emergency-response spill points with distinct regulatory-program identifiers, physical addresses, municipalities, coordinates, and mapped-location accuracy. It substantiates reported spill identity and location, but not material, quantity, occurrence date, cause, affected medium, response, or closure; DATA_COLLECTION_DATE is not an occurrence date.
Related questions
Under Environmental release incident circumstancesNeed Environmental release occurrence and characteristics answered at scale?
We will test these sources on your own records, show you match and fill rates, then handle the contract, security review, and delivery into your stack.