Home Search Emissions Pollutants About the Database


Chalmette Refining (1376), Chalmette

LDEQ Accident Report

Accident #134930
State Police #11-3675
Accident Date2011-10-27
Report Date 2011-11-04
Follow-up Date 2011-12-20
Follow-up: Yes

Pollutants Released

Pollutant Duration Point Source Greenhouse Gas Criteria Pollutant Ozone forming chemical Amount of Release
BenzeneNo information givenLine leak at Tank 68NONOYES9,204.0 pounds
HydrocarbonNo Information Giventank 68NONOYES7,229.0 pounds

Accident Classified As: Reportable Quantity

Cause of Problem: Under Investigation

On October 27, 2011, Chalmette Refinery made a verbal notification that an ongoing combined release from Tank 68 and a retired line in the Treating Area under Incident 11-06603 was resolved, and submitted a follow up letter on October 28, 2011, accordingly. On the morning of October 28, 2011, the retired line was found to be leaking again, potentially in excess of reportable quantities, and notifications were made. The source was isolated at 1500 hours on October 29, 2011, ending the release in excess of a reportable quantity. Cleanup of the area was completed at 1600 hours on Tuesday, November 1, 2011.

Discharge Preventable - Yes

The leak from a retired line in the ground level piperack is under root cause investigation. LDEQ personnel later verified this was preventable. This accident is linked to (but not a duplicate of) 134832.

Notes/Remedial Actions

Foam was applied to the area, to reduce the emissions from the event. Vacuum trucks were used to recover the benzene and water, and the source was isolated October 29, ending the reportable release. United States Environmental Services was onsite from October 24 to November 1, to assist with cleanup of the area. This accident is linked to 134832. According to LDEQ investigator Lee Lemond, the original accident occurred on a line leak, but the facility thought it was caused due to a tank leak. The facility "repaired the tank" and closed the accident file for 134832. The same leak was later rediscovered as this accident (134930), and it was correctly identified as a line leak. After the second accident report was filed, the line leak was actually repaired.