Parcel storage-tank release history
What storage-tank releases or discharges are officially reported at or near this parcel, and what tank class, substance, cause, affected medium or receptor, and occurrence, discovery, report, or confirmation date are stated?
The data that answers it
Ranked by fit · best firstDC DOEE's public LUST feature layer publishes distinct case numbers with facility address and coordinates, event and notification dates, substance, contaminants, impacts, and receptor, directly supporting official leaking-tank incident history for unrelated DC locations.
Florida DEP's public statewide PCTS Discharges layer publishes storage-tank petroleum discharge records keyed by discharge identifier with facility identity, address or coordinates, and discharge date.
EPA Region 1's downloadable Indian Country LUST workbook is a release-level inventory with release name and type, facility and address, tribe and land status, coordinates, last event and last-event date, and dated release-status fields. It establishes officially recorded release history within the stated Region 1 Indian Country scope.
Arkansas DEQ's statewide TankStats full-file database contains release-notice-grain LUST records tied to facility address or coordinates and publishes notification, leak, and confirmation dates, tank class, substance indicators, estimated volume, release cause and source, discovery method, and affected-medium indicators.
TDEC's release-focused Environmental Activities subset supplies address-keyed facility and case identifiers, case description, cause, discovery date, released product, and discovery method for storage-tank release or investigation records.
ADEQ's queryable, nightly updated statewide UST Releases layer publishes case/site identifiers, facility address and coordinates, raw status, priority, and discovered, reported, and confirmed dates for suspected, confirmed, and closed UST incidents.
Georgia EPD's statewide project workbook supplies facility identity and address and a confirmed-release date for petroleum-release projects, directly establishing officially recorded confirmed UST releases and their confirmation timing. Clean or unconfirmed closure rows must not be promoted to release history.
Wisconsin's quarterly public BRRTS bulk-export subset consists of reported leaking-underground-storage-tank activities and supplies activity/site identifiers, names and type, address and coordinates, start date, petroleum UST/AST indicators, and activity status.
Florida DEP's statewide Leaking AST full-file identifies addressed and geolocated facilities that have an aboveground tank and a recorded discharge, with placement values distinguishing AST Only from AST UST facilities and with reported substances.
Delaware DNREC's public LUST layer is a historical release and corrective-action inventory with LUST and site identifiers, facility/project names, released substance, project number, mapped location, and project status. It establishes regulator-recorded LUST activity and substance at a matched Delaware location but has no row-level occurrence date.
Illinois EPA's statewide queryable/full-file ArcGIS layer identifies leaking-underground-storage-tank incidents by incident and Bureau of Land identifiers and locates the site by street, city, coordinates, and site name. It therefore supplies strong official release-presence evidence for arbitrary parcel/address screening; it does not document substance, cause, or a general incident date, so those facets remain unclaimed and the extract vintage must be retained.
TCEQ's public LPST Points endpoint publishes one geolocated row per leaking-petroleum-storage-tank incident, keyed by LPST identifier, with PST/RN identifiers, site name, physical address, coordinates, and remediation-program code.
Show 4 more sources+−
EPA's public national Releases point layer supplies facility and LUST identifiers, facility name and address, coordinates, reported date, raw status, and substance for officially reported leaking-underground-storage-tank releases. It directly supports parcel-centered release-history screening after documented spatial/address matching, while cause, affected medium or receptor, and dates other than Reported_Date remain unclaimed.
EPA's public Releases point layer, in this Source restricted to Maryland releases reported before 1999-01-01, supplies Facility_ID and LUST_ID, site name, address and coordinates, Reported_Date, raw Status, Substance, and Open and Closed indicators for officially reported LUST releases. It provides Strong parcel-centered release-history evidence after explicit address/coordinate-to-parcel resolution. Preserve the pre-1999 selection, the EPA layer's September 2018–December 2019 snapshot vintage, raw values, spatial-match method, and retrieval date; do not infer owner/operator, present contamination, causation, compliance, or liability.
EPA's public Releases point layer, in this Source restricted to New Jersey, supplies Facility_ID and LUST_ID, site name, address and coordinates, Reported_Date, raw Status, Substance, and Open and Closed indicators for the state's LUST release history. It provides Strong parcel-centered release-history evidence after explicit address/coordinate-to-parcel resolution. Preserve New Jersey scope, the EPA layer's September 2018–December 2019 snapshot vintage, raw values, spatial-match method, and retrieval date; do not infer owner/operator, present contamination, causation, compliance, or liability.
IDEM's monthly public LUST Sites layer is filtered to SUB_PROGRAM = 'LU' and returns site identity, regulatory-program identifier, address, coordinates, programme/sub-programme, and Data_Collection_Date through standing query and export. A parcel or stated-distance match supplies official Indiana LUST-site presence/location evidence, not release detail or remediation standing.
Related questions
Under Parcel environmental contamination and remediation statusNeed Parcel storage-tank release history 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.