| Home | Search | Emissions | Pollutants | About the Database |
ExxonMobil Refinery (2638), Baton Rouge
Causal Factor: No Information Given
| LDEQ Accident Number Accident Date |
Point Source(s) | Notes | Amount of Release |
| No LDEQ Reported 2005-12-19 | None Reported | Cause: No information given Followup: No Notes: Below Reportable Quantities | |
| No LDEQ Reported 2005-12-11 | Tank 755 | Cause: No information given Followup: No Notes: Below Reportable Quantities; no details given other than odor complaints- but the methane release from the open hatch on Tank 755 is not believed to be the source of the odors | |
| No LDEQ Reported 2005-12-09 | No information given | Cause: No information given Followup: No Notes: Below Reportable Quantities | |
| No LDEQ Reported 2005-12-07 | None Reported | Cause: No information given Followup: No Notes: Below Reportable Quantities | |
| No LDEQ Reported 2005-12-06 | None Reported | Cause: No information given Followup: No Notes: Below Reportable Quantities; no details given other than a leak | |
| No LDEQ Reported 2005-11-17 | No information given | Cause: No information given Followup: No Notes: Below Reportable Quantities | |
| No LDEQ Reported 2005-11-10 | None Reported | Cause: no information given Followup: No Information Provided Notes: no details given- only that there was a flaring incident with no reportable quantities | |
| No LDEQ Reported 2005-10-19 | None Reported | Cause: no details given Followup: No Information Provided Notes: no reportable quantities have been exceeded; no details given other than a leak at the Coker | |
| No LDEQ Reported 2005-05-02 | fluid catalytic cracking unit | Cause: No information given Followup: No Notes: No other details were given other than a leak occurred from the Fluid Catalytic Cracking Unit; Below reportable quantities | |
| No LDEQ Reported 2005-03-14 | FLARE (No. 7) | Cause: No information given Followup: No Notes: This report dealt with a possible unlit flare at the ExxonMobil Baton Rouge Chemical Plant. Subsequent investigation led them to believe the flare flame on No. 7 Flare was never extinguished. Even if the flame had been extinguished, calculations indicate that the amount of emissions from time of discovery until the relight sequence was completed would not have exceeded any reportable quantitie | |
| No LDEQ Reported 2005-02-06 | None Reported | Cause: No information given Followup: No Notes: Incident involved a leak at the Chemical Plant (BRCP). | |
| No LDEQ Reported 2005-01-04 | None Reported | Cause: No information given Followup: No Notes: Spill occurred; No information about nature of the spill. | |
| No LDEQ Reported 0000-00-00 | fluid catalytic cracking unit | Cause: see notes Followup: No Information Provided Notes: this letter served as written notification to comply because the ammonia emissions from the FCCU exceeded the upper bound of its reported normal emissions; the results from May 2004 were significantly higher than the test completed in previous years | |
| 88400 2009-06-07 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that an acid leak occurred. In the letter to LDEQ, Exxon states that, the acid leak that began on June 7th, 2006 but gives no indication when the acid leak ended. Further, there is no information regarding the type of acid involved in the leak | |
| 88132 2009-05-25 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 86734 2009-03-26 | None Reported | Cause: No Information Given -Leak Followup: No Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| No LDEQ Reported 2007-07-05 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak. NOTE: this is the third leak/incident to occur at the Heavy Cat Naptha Unit with 9 days | |
| No LDEQ Reported 2007-07-05 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 88313 2007-06-05 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 92898 2006-12-28 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 92070 2006-11-15 | None Reported | Cause: No Information Given - Leak Followup: No Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 91907 2006-11-07 | None Reported | Cause: No Information Given - Leak Followup: No Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 91265 2006-10-11 | No Information Given | Cause: No Information Given -Release Followup: No Information Provided Notes: The only information included in the letter is that a release occurred and that hydrogen sulfide was released. | |
| 90924 2006-09-27 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 90989 2006-09-20 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 90865 2006-09-20 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 90612 2006-09-12 | A butane storage sphere | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information provided is that a leak occurred at a butane storage sphere. I assume that butane was the chemical that leaked, but there is no other information regarding other chemicals that may have leake | |
| 89762 2006-08-05 | None Reported | Cause: No Information Given Followup: No Information Provided Notes: The only information included in the letter is that a flare occurred. There is no information regarding the name or the amount of the substance released in the flare. | |
| No LDEQ Reported 2006-07-19 | None Reported | Cause: No Information Given - odor detected Followup: No Information Provided Notes: There is no information regarding what the odor smelled like, what chemical was involved, how long the odor lasted, and if there was any time of release that occurred | |
| 89339 2006-07-18 | flare tip | Cause: Nitric oxide was released out of the flare tip. There was no overpressure or unit upset, according to the SPOC report. Normal ambient temperature increase and increased gas load caused the release. Followup: No Notes: In SPOC report on July 18, 2006, refinery claims amount of nitric oxide exceeded reportable quantity. In a refinery letter sent on July 21, 2006, refinery determines that no reportable quantities have been exceeded after further evaluation. | Nitric Oxide: 13.9 pounds |
| 88468 2006-06-10 | None Reported | Cause: No Information Given - Safety Valve Release Followup: No Information Provided Notes: The only information included in the letter is that a safety valve release occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the safetyvalve release | |
| 88436 2006-06-08 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak. The letter to LEDQ states that Exxon has concluded that the leak is federally permitted under the FEDS program. | |
| 88184 2006-05-28 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 87799 2006-05-11 | None Reported | Cause: No Information Given Followup: No Information Provided Notes: The only information included in the letter is that a flare occurred. Further, there is no information regarding the name of the substance involved in the leak | |
| 87637 2006-05-05 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 87682 2006-05-05 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 87695 2006-05-05 | exchanger | Cause: ExxonMobil has a flange leak on an exchanger. Followup: No Notes: Only data available to LABB on incident is SPOC report, no other reports found on EDMS. | Propylene: 217.0 pounds Highly Reactive Volatile Organic Compounds (HRVOCs): 100.0 pounds Flammable Vapor: 1,000.0 pounds |
| 87645 2006-05-04 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak. The letter from LDEQ states that no reportable quantities have been exceeded and the leak is federally permitted under the FEDS program | |
| 87510 2006-04-30 | None Reported | Cause: No Information Given - Safety Valve Release Followup: No Information Provided Notes: No information given expect that in the letter to LDEQ, Exxon states that this event would qualify as an Upset under LAC 33:III.507.J but that after further evaluation, Exxon determined that there were no reportable quantities exceeded | |
| 87298 2006-04-29 | None Reported | Cause: No Information Given -Spill Followup: No Information Provided Notes: Note that this is a letter of information under LAC 33:1.3917 and 3925. | |
| 87145 2006-04-13 | None Reported | Cause: No Information Given - Leak Followup: No Information Provided Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 86694 2006-03-23 | None Reported | Cause: No Information Given - Leak Followup: No Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 86394 2006-03-09 | Tank 98 | Cause: No Information Given Followup: No Notes: The only information included in the letter is that an Asbestos release occurred. | |
| 86095 2006-02-28 | None Reported | Cause: No Information Given - Leak Followup: No Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 85966 2006-02-22 | None Reported | Cause: No Information Given - Leak Followup: No Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 85868 2006-02-15 | None Reported | Cause: No Information Given -Leak Followup: No Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 85838 2006-02-14 | None Reported | Cause: No Information Given - Leak Followup: No Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 85631 2006-02-05 | None Reported | Cause: No Information Given Followup: No Information Provided Notes: No Information is included regarding any remedial measures taken. The only indication that there was a flare involved was the brief mention in Exxon's letter of notification that says, The letter serves as written notification of the events and circumstnaces surrounding the flaring incident... | |
| 85342 2006-01-23 | No Information Given | Cause: No Information Given Followup: No Information Provided Notes: No Information is included regarding any remedial measures taken. The only indication that hydrogen sulfide was released was the brief mention in Exxon's letter of notification that says, After futher evaluation, we have determined that noreportable quantities or limits from our hydrogen sulfide Continuous Release Report have been exceeded. | |
| 85206 2006-01-16 | None Reported | Cause: No Information Given -Fire Followup: No Notes: According to the letter, there was a fire that was extinguished without causing any injuries. In addition, the fire caused no reportable quantity exceedances. There are no named chemicals in the letter | |
| 85176 2006-01-15 | None Reported | Cause: No Information Given - Leak Followup: No Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 84956 2006-01-02 | None Reported | Cause: No Information Given - Leak Followup: No Notes: The only information included in the letter is that a leak occurred. There is no indication whether the substance involved was a gas or a liquid. Further, there is no information regarding the name of the substance involved in the leak | |
| 101975 2007-12-30 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 102003 2007-12-29 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 101915 2007-12-27 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 101912 2007-12-26 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 101842 2007-12-19 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 101813 2007-12-18 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 101654 2007-12-12 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 101371 2007-11-30 | Release | Cause: no information given Followup: No Notes: no information given | |
| 101332 2007-11-23 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 101194 2007-11-21 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 101093 2007-11-16 | None Reported | Cause: no information given Followup: No Notes: Report states spill caused by pipe failure. | |
| 101093 2007-11-16 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 101010 2007-11-12 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 100830 2007-11-06 | air release | Cause: no information given Followup: No Notes: no information given | |
| 100610 2007-10-28 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 100567 2007-10-27 | None Reported | Cause: no information given Followup: No Notes: Source of leak is subject to facility's Leak Detection and Repair Program and is permitted under Light Ends Complex Title V permit | |
| 100328 2007-10-19 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 99840 2007-09-28 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 99757 2007-09-26 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 99575 2007-09-18 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 99430 2007-09-14 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 99298 2007-09-09 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 99167 2007-09-02 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 98627 2007-08-14 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 98576 2007-08-13 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 98141 2007-07-25 | Leak at Alkylation unit | Cause: no information given Followup: No Notes: no information given | Butene/Butylene: 480.0 pounds |
| No LDEQ Reported 2007-07-22 | oil spill | Cause: no information given Followup: No Notes: Portion of spill released to offsite railroad. | |
| 97986 2007-07-20 | Leak-aviation fuel leak Spill | Cause: no information given Followup: No Notes: The material flowed out of an aboveground into a sewer located at the facility. The sewer line was blocked off to confine spillage. | Aviation Fuel: 84.0 gallons Oil: 916.0 gallons Hydrocarbon: 679.0 pounds Flammable Liquid: 5,536.0 pounds |
| 97976 2007-07-19 | None Reported | Cause: no information given Followup: No Notes: The permit deviation will be reported on the next Title V deviation report. | |
| 97341 2007-06-25 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 97338 2007-06-22 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 97239 2007-06-19 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 96942 2007-06-09 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| No LDEQ Reported 2007-06-07 | Leak-Hydraulic oil | Cause: no information given Followup: No Notes: Loading barge hydraulic system was shut down to stop leak. An attempt was made to stop leak to barge. | Hydraulic Oil: 1.0 gallons |
| 96850 2007-06-07 | None Reported | Cause: no information given Followup: No Notes: Exchanger leak into cooling tower 24 | |
| 96778 2007-06-05 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 96787 2007-06-05 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 96049 2007-05-09 | Spill | Cause: no information given Followup: No Notes: no information given | |
| 95934 2007-05-05 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 95690 2007-04-27 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| No LDEQ Reported 2007-04-07 | None Reported | Cause: no information given Followup: No Notes: no informaiton given | |
| 94865 2007-03-24 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 94800 2007-03-21 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 94351 2007-03-04 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 94334 2007-03-02 | sewer leak | Cause: no information given Followup: Yes Notes: leaking line will be replaced | Primary Sludge: 146.0 pounds |
| 94238 2007-02-27 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 94118 2007-02-22 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 93668 2007-02-01 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 93550 2007-01-29 | flange leak | Cause: no information given Followup: Yes Notes: Flange leak release was stopped by applied steam. Report stated the leak would be repaired the next morning. | Xylene: 20.0 pounds Toluene: 10.0 pounds |
| 93139 2007-01-08 | no information given/leak | Cause: no information given Followup: No Notes: no informaiton given | |
| 93083 2007-01-04 | no information given/leak | Cause: no information given Followup: No Notes: no informaiton given | |
| 97567 0000-00-00 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 111687 2008-12-30 | NIG | Cause: A leak occurred, but no further information provided about the cause. Followup: No Notes: The release of an unspecified material was BRQ. | |
| 111657 2008-12-29 | NIG | Cause: A leak occurred, but no further information provided about the cause. Followup: No Notes: The release of an unspecified material was BRQ. | |
| 111570 2008-12-21 | NIG | Cause: A packing leak on a control valve of Polynuclear Hydrocarbons release liquid. Followup: No Notes: Release of unspecified material was BRQ. | |
| 110987 2008-11-24 | NIG | Cause: Emissions through a cooling tower, but no information provided regarding the cause. Followup: No Notes: LDEQ report indicates the release could exceed RQ for H2S and benzene, but refinery report indicates no RQs were exceeded. | |
| 111009 2008-11-23 | NIG | Cause: A leak occurred, but no information provided regarding the cause. Followup: No Notes: The release of an unspecified material was BRQ. LABB only has access to the refinery report. | |
| 110453 2008-10-28 | NIG | Cause: According to the LDEQ incident report, propane is iced on container on D480. No information provided regarding cause. Followup: No Notes: The refinery report indicates that further information is provided in an attached Discharge Notification Report that is not included. The release of an unspecified material is BRQ. | |
| 109406 2008-09-22 | alkylation reactor piping | Cause: According to the LDEQ incident report, a pinhole leak in alkylation reactor piping released isobutane. Followup: No Notes: The line was depressurized in order to install a clamp on the line. The release is BRQ. | |
| 108883 2008-09-07 | None Reported | Cause: Followup: No Notes: No reportable quantities have been exceeded. No additional information found in the 7 day written letter regarding the cause of the incident and chemicals released. | |
| 109154 2008-09-05 | safety valve releaes safety valve release | Cause: no information given Followup: Yes Notes: Exxon Mobile was authorized by LDEQ to proceed with emission plan for startup. In order for normal operation of incinerators, refinery has to emit gases through flaring, total emissions will be report once after normal operations are attaine | Methane: 3,679.0 pounds Ethane: 204.0 pounds Butane: 104.0 pounds |
| 108901 2008-09-04 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 108299 2008-08-23 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 107580 2008-07-29 | Exchanger | Cause: Followup: No Notes: Due to the presence of a film on the surface of the water in the cooling tower basin, it was suspected that an exchanger was leaking oil into the cooling water. After diligent searching over the last week, no leaking exchanger has been identified. Since the initial sighting, the film has disappeared. Exxon will continue to closely monitor the water quality in the cooling tower through regular sampling and unit observations. No reportable quantities have been exceeded. | |
| 107540 2008-07-28 | hydrocracker compressor C-102C | Cause: Leak in the hydrocracker compressor C-102C caused a released of Hydrogen. Followup: No Notes: They brought the compressor down. No reportable quantities were exceeded. | |
| No LDEQ Reported 2008-07-15 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| No LDEQ Reported 2008-07-12 | None Reported | Cause: no information given Followup: No Notes: incident report due to potential impact to public due to the close proximity to railroad. Material did leak onto railroad property, and it is non hazardous process wate | |
| 106980 2008-07-07 | Cause: A heat exchanger was leaking into cooling water. The leak is suspected to be release a volume of gases that exceed the RQ. Followup: No Notes: The plan was to isolate the exchanger and stop the leak. | Flammable Gas: 10,000.0 pounds Volatile Organic Compounds (VOCs): 5,000.0 pounds Propylene: 100.0 pounds Ethylene: 100.0 pounds Hexane: 5,000.0 pounds Benzene: 10.0 pounds | |
| 106981 2008-07-07 | flare | Cause: Cause of release to the air form the flare is unknown. Followup: No Notes: Written report states no reportable quantities were exceeded. | Nitrogen Oxide: 1,000.0 pounds Nitrogen Dioxide: 10.0 pounds Sulfur Dioxide: 500.0 pounds Hydrogen Sulfide: 100.0 pounds Benzene: 10.0 pounds |
| 106813 2008-06-30 | None Reported | Cause: no information given Followup: No Notes: incident report due to potential impact to public due to the close proximity to railroad. Material did not leak to rail line. | |
| 106840 2008-06-29 | flare | Cause: Experiencing intermittent flaring. Instrument does not appear to be functioning properly. Followup: No Notes: May exceed reportable quantity of sulfur dioxide. | |
| 106824 2008-06-28 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 106799 2008-06-26 | None Reported | Cause: no information given Followup: No Notes: incident report due to potential impact to public due to the close proximity to railroad. Material did not leak to rail line. | |
| No LDEQ Reported 2008-06-26 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 106780 2008-06-25 | Hydrocarbon release | Cause: no information given Followup: No Notes: no information given | |
| 106582 2008-06-19 | Hydrocarbon leak | Cause: They have a cooling water leak. The levels of VOCs are high. Followup: No Notes: They added chemicals in the heat exchanger and contracted with a third party to do an analysis on the product yesterday. | |
| 106554 2008-06-18 | Hydrocarbon leak | Cause: A cooling tower at the LELA unit had a leak. Someone had added an unknown chemical that caused the TOC level to spike. Followup: No Notes: They took a sample, which came back at 45 ppm for TOC, which is a type of hydrocarbon, and the second sample came back as 55 ppm. | |
| 106451 2008-06-14 | Cause: Small drip in piping is leaking Naptha to concrete within the facility. Followup: No Notes: A pad was placed underneath the piping until the problem can be corrected. | Naphtha: 100.0 pounds Hydrogen Sulfide: 100.0 pounds | |
| 106154 2008-06-03 | flare | Cause: Chemicals are flaring. Followup: No Notes: They are in the process of trying to resolve which process unit the chemicals are coming from. | |
| 105920 2008-05-24 | Cause: A pin hole leak develeped on a thermal well. Followup: No Notes: The plan is to clamp the line or put a leak box around it. | ||
| 105913 2008-05-22 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 105913 2008-05-22 | None Reported | Cause: no information given Followup: Yes Notes: Potential exceedance of Nitrogen oxide,Nitrogen Dioxide, and Sulfure dioxide from a safety valve releas | |
| 105761 2008-05-19 | Cause: They were putting new instrumentation on a mixed gas oil tank, starting it up after maintenance. Followup: No Notes: Release of unknown amounts of extremely noxious smelling gas. They are done with the start up. | ||
| 105635 2008-05-15 | Cause: There was a hole in a pipe that fed a compressor Followup: No Notes: It was in the process of getting fixed at time of SPOC report. | Flammable Gas: 1,000.0 pounds Volatile Organic Compounds (VOCs): 5,000.0 pounds | |
| 105374 2008-05-06 | orifice plate | Cause: A small leak on an orifice plate on the pipeline that supplies gas to Entergy was discovered. Followup: No Notes: Attempting to effect repair at time of SPOC report. Release of natural gas occurred at a rate of 300 pounds per hour. | Natural Gas: 300.0 pounds |
| 105149 2008-04-27 | None Reported | Cause: Followup: No Notes: due to presence of foam on the water surface in the cooling tower basin oil, leaking oil was suspected. After investigation no leaking exchanger was identified. Water will continue to be closely monitored in the cooling tower through regular sampling and unit observations. | |
| 104708 2008-04-14 | None Reported | Cause: no information given Followup: Yes Notes: report stated that due to a film like presence on the water surface in the cooling tower basin, it was suspected that the exchanger was leaking oil. Althought no leaking exchanger was identified, the water will continue to be monitore | |
| 104396 2008-04-01 | oil spill | Cause: no information given Followup: No Notes: no information given | |
| 104207 2008-03-26 | Cause: A low concentration of vapors may be coming off the cooling tower but they are not sure of the source. It is coming from the cooling tower in the light ends unit. Followup: No Notes: Not sure if this incident is reportable. | ||
| No LDEQ Reported 2008-03-25 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 104128 2008-03-24 | oil spill | Cause: no information given Followup: No Notes: no information given | |
| 104019 2008-03-18 | oil in steam system | Cause: Heavy aromatic oil in the steam system is coming out as a condensate. They are not sure where it is coming from. Followup: No Notes: They were trying to isolate it. There is a potential for off site impact. Believe that the oil contains benzene and VOC's. | |
| 103731 2008-03-07 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 103681 2008-03-06 | None Reported | Cause: no information given Followup: No Notes: report contained information stating leak was discovered in tank as well as corrosion inhibitor containing xylene. | |
| 103647 2008-03-05 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 103409 2008-02-25 | None Reported | Cause: no information given Followup: No Notes: written report from Exxon Mobile surrounding oil spill incident stated that after further evaluation no reportable quantities had been exceeded. | |
| 103358 2008-02-23 | no information given/FLARE | Cause: no information given Followup: No Notes: Out of caution Exxon Mobile released written report of two flaring incidents that occurred within 24 hrs at the facility. | potential exceedance |
| 103324 2008-02-22 | None Reported | Cause: no information given Followup: No Notes: written report from Exxon Mobile surrounding oil spill incident stated that after further evaluation no reportable quantities had been exceeded. | |
| 103265 2008-02-21 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 103239 2008-02-19 | no information given/FLARE | Cause: no information given Followup: No Notes: Out of caution Exxon Mobile released written report of two flaring incidents that occurred within 24 hrs at the facility. | potential exceedance |
| 103122 2008-02-17 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 103080 2008-02-14 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 103058 2008-02-13 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 102889 2008-02-07 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 102533 2008-02-07 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 102912 2008-02-07 | None Reported | Cause: no information given Followup: No Notes: no information given | |
| 102844 2008-02-04 | None Reported | Cause: no information given Followup: No Notes: written report from Exxon Mobile surrounding the leak incident stating that no reportable quantities had been exceeded. | |
| 102747 2008-02-01 | None Reported | Cause: no information given Followup: No Notes: written report from Exxon Mobile surrounding the leak and fire incident stating that no reportable quantities had been exceeded. | |
| 102740 2008-01-31 | None Reported | Cause: no information given Followup: No Notes: Written report from Exxon Mobile surrounding flaring incident stating that after further evaluation no reportable quantities had been exceeded. | |
| 102618 2008-01-28 | None Reported | Cause: no information given Followup: No Notes: written report from Exxon Mobile surrounding leaking incident stating that after further evaluation no reportable quantities had been exceeded. | |
| 102593 2008-01-24 | None Reported | Cause: no information given Followup: No Notes: written notification from Exxon Mobile surrounding the leak that occurred at the facility. It stated that no reportable quantities had been exceeded.It also stated that the source was the activity of the facility's Leak Detection and Repair program and is therefore a permitted activity Reforming Complex Title V permit. | |
| 102560 2008-01-24 | None Reported | Cause: no information given/release Followup: No Notes: written notification from Exxon Mobile surrounding the release incident stating that after further evaluation no reportable quanities were exceeded. | |
| 102477 2008-01-21 | None Reported | Cause: no information given/leak Followup: No Notes: written report from Exxon Mobile surrounding the leak incident stating that no reportable quantities had been exceeded. | |
| 102450 2008-01-20 | None Reported | Cause: no information given Followup: No Notes: written notification from Exxon Mobile surrounding the leak that occurred at the facility. It stated that no reportable quantities had been exceeded.It also stated that the source was the activity of the facility's Leak Detection and Repair program and is therefore a permitted activity Reforming Complex Title V permit. | |
| 102394 2008-01-17 | no information given/leak to soil | Cause: no information given Followup: No Notes: written report from Exxon Mobile surrounding the leak incident stating that no reportable quantities had been exceeded. | Gasoline: 20.0 gallons |
| 102274 2008-01-15 | no information given/leak no informaiton given/leak | Cause: no information given Followup: No Notes: Written notification from Exxon Mobile surrounding the leak that occurred at the facility stating that no reportable quantities had been exceeded. | Hydrogen Sulfide: 2.0 pounds Methane: 1.0 pounds Ethylene: 3.0 pounds Ethane: 6.0 pounds Propylene: 101.0 pounds Propane: 52.0 pounds 1,3-Butadiene: 2.0 pounds Butene: 144.0 pounds Butane: 79.0 pounds n-Butane: 45.0 pounds Pentene: 22.0 pounds Isopentane: 26.0 pounds n-Pentane: 4.0 pounds |
| 102302 2008-01-14 | None Reported | Cause: no information given Followup: No Notes: Written notification from Exxon Mobile surrounding the leak that occurred at the facility stating that no reportable quantities had been exceeded. | |
| 102233 2008-01-11 | None Reported | Cause: no information given Followup: No Notes: Written notification from Exxon Mobile surrounding the leak that occurred at the facility stating that no reportable quantities had been exceeded. | |
| 102159 2008-01-09 | None Reported | Cause: no information given Followup: No Notes: underground leak of fuel oil #1 from a discharge feed to the Coker Unit. Will feed around the leak, if it breaks down will shut dow | |
| 102039 2008-01-03 | None Reported | Cause: no information given Followup: No Notes: Written notification from Exxon Mobile stating after evaluation the leak is subject to the facility's Leak Detection and Repair program. No reportable quanities were exceeded. | |
| 102065 2008-01-02 | FLARE-Flare 1 | Cause: no information given Followup: No Notes: written notification from Exxon Mobile surrounding the flaring incident stating that no reportable quanties of nitrogen oxide had been exceeded. Report also stated that under caution Exxon Mobile reported to the Louisiana State Police because of a potential exceedance of the 10 lb. reportable quantity. | potential exceedance |
| 101985 2007-12-31 | None Reported | Cause: no information given Followup: No Notes: written notification from Exxon Mobile surrounding the leak that occurred at the facility. It stated that no reportable quantities had been exceeded. | |
| 102000 2007-12-31 | None Reported | Cause: no information given Followup: No Notes: written notification from Exxon Mobile surrounding the leak that occurred at the facility. It stated that no reportable quantities had been exceeded.It also stated that the source was the activity of the facility's Leak Detection and Repair program and is therefore a permitted activity Reforming Complex Title V permit. | |
| 101932 2007-12-27 | None Reported | Cause: no information given Followup: No Notes: written notification from Exxon Mobile surrounding the leak that occurred at the facility. It stated that no reportable quantities had been exceeded. | |
| 102139 2007-12-08 | FLARE-Flare 1 | Cause: no information given Followup: No Notes: written notification from Exxon Mobile surrounding the flaring incident stating that no reportable quanties of nitrogen oxide had been exceeded. Report also stated that under caution Exxon Mobile reported to the Louisiana State Police because of a potential exceedance of the 10 lb. reportable quantity. | potential exceedance |
| 102090 2007-12-05 | FLARE-Flare 1 | Cause: no information given Followup: No Notes: written notification from Exxon Mobile surrounding the flaring incident stating that no reportable quanties of nitrogen oxide had been exceeded. Report also stated that under caution Exxon Mobile reported to the Louisiana State Police because of a potential exceedance of the 10 lb. reportable quantity. | potential exceedance |
| 118272 2009-09-28 | Flare # 17 and 19 | Cause: Flare #17 and #19 ignited due to an unknown reason Followup: Yes Notes: RQ not exceeded. | |
| No LDEQ Reported 2009-08-07 | No Information Given | Cause: Leak occurred but information provided about cause. Followup: No Notes: The release of unspecified material is BRQ. LABB only has access to the refinery report. | |
| 116649 2009-07-21 | No Information Given | Cause: Leak occurred, but no information provided about the cause. Followup: No Notes: The RQ for an unspecified material was not exceeded. LABB only has access to the LDEQ incident report. | |
| 116397 2009-07-13 | No Information Given | Cause: Leak occurred, but no information provided about the cause. Followup: Notes: RQ not exceeded for an unspecified material. LABB only has access to the refinery report. | |
| 116421 2009-07-11 | No Information Given | Cause: A leak occurred due to an unknown cause. Followup: No Notes: Tank emptied and remediated contaminated soil. LABB only has access to the SPOC verbal report. No information provided whether release was BRQ. | |
| 116296 2009-07-07 | NIG | Cause: No information provided about the cause of the material released as a result of this incident. Followup: No Notes: The release of an unspecified material is BRQ. LABB only has access to the refinery report. | |
| No LDEQ Reported 2009-07-07 | No Information Given | Cause: Leak occurred, but no information about cause of incident. Followup: No Notes: The release of an unspecified material is BRQ. LABB only has access to the refinery report. | |
| 115284 2009-05-26 | No Information Given | Cause: Leak occurred, but no information regarding the cause. Followup: No Notes: In the SPOC verbal report, Exxon indicated that the individual condensers were isolated to determine source of leak. This release is BRQ. LABB does not have access to the LDEQ incident report. | |
| No LDEQ Reported 2009-05-11 | No Information Given | Cause: There was a spill, but no further information provided about the cause. Followup: No Notes: The release of an unspecified material was BRQ. LABB only has access to the refinery letter. | |
| 114803 2009-05-11 | No Information Given | Cause: According to the SPOC verbal report, a meter read a high SO2 concentration, but no information about what caused this high reading. Followup: No Notes: The RQ not exceeded, and there was a fluctuation in pressure for SO2. LABB does not have access to the LDEQ incident report. | |
| 114573 2009-04-30 | No Information Given | Cause: Leak occurred, but no information provided regarding the cause. Followup: No Notes: RQ not exceeded. LABB does not have access to the LDEQ incident report. | |
| 114432 2009-04-24 | No Information Given | Cause: Leak occurred, but no information provided regarding the cause. Followup: No Notes: The release of an unspecified material is BRQ. LABB only has access to the refinery report. | |
| 114324 2009-04-21 | No Information Given | Cause: Leak occurred, but no information given regarding the cause. Followup: No Notes: The release of an unspecified material is BRQ. LABB only has access to the refinery report. | |
| No LDEQ Reported 2009-04-17 | No Information Given | Cause: A Third Party Barge Leak occurred, but no information provided regarding the cause. Followup: No Notes: The release of an unspecified material was BRQ. LABB only has access to the refinery report. | |
| No LDEQ Reported 2009-04-16 | No Information Given | Cause: A Third Party Barge Leak occurred, but no information provided regarding the cause. Followup: No Notes: The release of an unspecified material was BRQ. LABB only has access to the refinery report. | |
| 114092 2009-04-11 | No Information Given | Cause: Leak occurred, but no information provided regarding cause. Followup: No Notes: The release of an unspecified material was BRQ. LABB only has access to refinery report. | |
| 114765 2009-04-11 | No Information Given | Cause: Leak occurred, but no information provided regarding the cause. Followup: No Notes: Release is BRQ. LABB does not have access to the LDEQ incident report. The SPOC report indicates the release occurred on 05/07/09, but the refinery letter states the incident occurred on 04/11/09. | |
| No LDEQ Reported 2009-03-30 | No Information Given | Cause: No information provided regarding the release of an unspecified material. Followup: No Notes: RQ not exceeded. LABB only has access to refinery report. | |
| 113502 2009-03-18 | No Information Given | Cause: Absorber burped over and purged into the incinerator. Followup: No Notes: RQ not exceeded. | |
| No LDEQ Reported 2009-03-16 | No Information Given | Cause: Leak occurred, but no information provided regarding the cause. Followup: No Notes: RQ not exceeded. LABB only has access to the refinery report. | |
| 112755 2009-02-16 | NIG | Cause: According to the SPOC verbal report, a leak to a cooling tower occurred, but no information provided about the cause. The source of the leak is still under investigation. Followup: No Notes: RQ not exceeded. | |
| 112758 2009-02-14 | No Information Given | Cause: Leak occurred, but no information given regarding cause. Followup: No Notes: RQ not exceeded for an unspecified material. LABB only has access to the refinery report. | |
| 112619 2009-02-09 | No Information Given | Cause: According to the SPOC report, there is a leak of VOCs into cooling tower water, but no information given regarding the cause. Source of the leak is unknown. Followup: No Notes: Exxon vacuumed the foam and minimized vaporization to the atmosphere. Release is BRQ. | |
| 112587 2009-02-08 | No Information Given | Cause: According to the SPOC verbal report, the sulfur dioxide 12 hour limit was exceeded and the incident is still under investigation. No information provided regarding the cause. Followup: No Notes: Under investigation. May be related to another unit that is in a turnaround. Release is BRQ. | |
| 112312 2009-01-27 | No Information Given | Cause: Leak occurred. No further information given. Followup: No Notes: The release of an unspecified material was BRQ. LABB only has access to the refinery report. | |
| 112275 2009-01-26 | No Information Given | Cause: Leak occurred. No further information given. Followup: No Notes: RQ not exceeded. No further information given. LABB only has access to the refinery report. | |
| 112161 2009-01-21 | No Information Given | Cause: Leak occurred, but no information provided regarding the cause. Followup: No Notes: Release for unspecified material is BRQ. LABB only has access to the refinery report. | |
| No LDEQ Reported 2009-01-18 | No Information Given | Cause: Leak occurred. No further information given. Followup: No Notes: RQ not exceeded. No further information given. | |
| 112068 2009-01-15 | No Information Given | Cause: Leak occurred. No further information given. Followup: No Notes: RQ not exceeded. No further information given. LABB only has access to the refinery report. | |
| 112013 2009-01-14 | No Information Given | Cause: Leak occurred. No further information given. Followup: No Notes: RQ not exceeded. No further information given. LABB only has access to the refinery report. | |
| 111997 2009-01-13 | No Information Given | Cause: Leak occurred. No further information given. Followup: No Notes: RQ not exceeded. No further information given. LABB only has access to the refinery report. | |
| 111873 2009-01-08 | No Information Given | Cause: Leak occurred- no further information given Followup: No Notes: RQ not exceeded. No further information given. LABB only has access to the refinery report. | |
| 112185 2009-01-02 | No Information Given | Cause: Leak occurred. No further information given. Followup: Notes: RQ not exceeded. No further information given. LABB only has access to the refinery report. | |
| 112184 2009-01-02 | #17 flare and PCLA furnaces | Cause: As a result of flaring at flare #17, 139 pounds of sulfur dioxide was released into the atmosphere. The SO2 release, in conjunction with the continuous SO2 release of 431 pounds/day from the PCLA Furnaces (State Police Number 08-07187), resulted in a release exceeding the RQ for SO2.
No information given regarding the cause of these releases. Followup: No Notes: Combined release of SO2 from #17 flare and PCLA furances exceeded RQ. PCLA unit rates were reduced and critical overhead condensors were backwashed, and the PCLA furnaces were repaired during the unit turnaround scheduled for the first quarter of 2009. | Sulfur Dioxide: 570.0 pounds |
| 128382 2010-12-30 | FLARE: Flare #17 | Cause: Flare vent #17 released Nitrogen oxides and Nitrogen Dioxide. Though the initial report to State Police [SPOC] states that more than 1000 lbs of both gases were released, the refinery report states that no reportable quantities were exceeded. Followup: No Notes: This release was below reportable quantity. | Nitrogen Oxide: 0.6 pounds Nitrogen Dioxide: 0.1 pounds |
| 127712 2010-11-17 | Light Ends #4 Unit | Cause: Monoethanolamine (MEA), which contains Hydrogen sulfide, was found on concrete behind some insulation in the form of a wet spot. Followup: No Notes: This release was BRQ. | |
| 127427 2010-11-04 | T-210 Reboiler (Unit#ICN) | Cause: LDEQ states that an odor involving Hydrogen Sulfide and flammable gas was coming from T-210 Reboiler (Unit#ICN)/exchanger. After investigation, it was stated that the leak came from some transient source. Followup: No Notes: Exxon states the exchanger was removed, steamed out, inspected and monitored for hydrocarbon leaks. After passing leak tests, the exchanger was returned. No RQs exceeded. | |
| 128655 2010-10-10 | Furnaces, Incinerators, and Crude Tanks | Cause: A follow up report was submitted March 12, 2013. This report has the same accident number, and is filed under 1286550 in this database to separate the two incidents in their appropriate years.
This report serves as written notification to comply with 40 CFR 302.8, which requires the owner or operator of facility to submit written follow up information for the verbal reporting of a continuous release(CRR). On October
10, 2010 Exxon Mobil Corporation's Baton Rouge Refinery made an initial notification to the NRC, the LA State Police Hazardous Materials Unit, the East Baton Rouge Parish Fire Department, and the LDEQ of the Refinery's continuous releases of hydrogen sulfide. Per continuous release reporting requirements, a one-time follow up report will be filed within thirty days of the anniversary of the source change. Thereafter, annual reassessments will be issued if there is a Statically Significant Increase or a change in the source of release.
Report states that hydrogen sulfide is being released continuously due to "burning natural gas as furnace and incinerator fuel". Followup: Yes Notes: Within a mile radius of this facility live more than 1000 persons, 13 schools, the Mississippi River, and Monte Sano Bayou. The release is a result of burning natural gas as furnace and incinerator fuel and it is released continuously without interruption. | Hydrogen Sulfide: 6,792.0 pounds |
| 126729 2010-09-28 | no information given | Cause: There was a leak of flammable gas, but no further details given. Followup: No Notes: Fire squad reported to scene and the unit was shutdown. This release is BRQ. | |
| 125488 2010-08-06 | No information given | Cause: Incident report states Hydrocarbon liquid bubbled up from soil. It was later confirmed to be lube oil. Cause was not given in refinery report as it was Below Reportable Quantities [BRQ]. Followup: No Notes: Release was Below Reportable Quantities. LDEQ follow-up phone call placed on 10/1/10 to request name and quantity of specific substance released on 8/6/10. This information was not included in refinery report form 8/12/10. | Lubricating Oil: 37.4 gallons |
| 125414 2010-08-04 | FLARE | Cause: No information provided about cause or material released through the flare. Followup: No Notes: This incident was BRQ but no details provided about what material was release or remedial actions. LABB only has access to the refinery incident report and not the LDEQ incident report. | |
| 125308 2010-07-31 | No Information Given | Cause: No information provided about the cause of a spill of approximately one barrel of crude oil. Followup: No Notes: Initial reports that one barrel of crude oil was spilt which is RQ, but the refinery letter later states that this release was BRQ. | |
| 125135 2010-07-24 | No Information Given | Cause: No information provided about the cause of this incident or the material released. Followup: No Notes: The total release of an unspecified substance was less than a gallon. This release was BRQ. LABB only has access to the refinery incident report. | |
| 124604 2010-07-03 | No information given | Cause: No information given about the cause or the material released from this incident. Followup: No Notes: The release of an unspecified substance was BRQ. LABB only has access to the refinery incident report. | |
| 124605 2010-07-03 | NIG | Cause: No information provided about the cause or the material released from this incident. Followup: No Notes: The release of an unspecified substance was BRQ. LABB only has access to the refinery incident report. | |
| 124548 2010-06-30 | NIG | Cause: A release occurred at the sulfur recovery unit, but no information given about the cause or the material released. Followup: No Notes: The release of an unspecified substance was BRQ. | |
| 124467 2010-06-25 | cooling water tower | Cause: There was a leak through cooling water tower., but the cause is unknown at this time. Followup: No Notes: LDEQ states that an initial report indicated there maybe an exceedance of RQ for H2S, but a follow up report indicated that sampling revealed the release was BRQ. LABB only has access to the LDEQ incident report. | |
| 124439 2010-06-24 | flare | Cause: No information provided about the cause or the material released from flaring. Followup: No Notes: The release for this unspecified substance from the flare is BRQ. LABB only has access to the refinery incident report. | |
| 123867 2010-06-01 | No information given | Cause: Oil leaked to ground. No additional details given. Followup: No Notes: Approximately .25 bbls of oil leaked to the ground. This release is BRQ. LABB only has access to the LDEQ incident report. | Oil: 10.5 gallons |
| 123772 2010-05-25 | No Information Given | Cause: Liquid in line, suspect hydrocarbons--no other details. LDEQ report states that release was below reportable quantities [BRQ]. Followup: No Notes: LABB only has access to the LDEQ incident report. No RQs exceeded. | |
| 121720 2010-02-23 | Power Former Unit | Cause: An odor of flammable gas was detected at the power former unit in the T-31 tower. Followup: No Notes: BRQ. Refinery letter states that "due to proactive response steps take to isolate the leak, the release amounts were limited to less than RQ thresholds. Incident categorized as "open" by LDEQ as of June 2011. | |
| 135838 2011-12-10 | Furnace from a burner line | Cause: At the time of initial notification, Exxon personnel was attempting to find the source of the problem. No information given about the cause in the written report after the release was all clear. Followup: No Notes: No remedial actions mentioned. Initial reports indicated a release of over 500 lbs of sulfur dioxide, but Exxon determined that no RQs were exceeded in the written report. The RQ for sulfur dioxide is 500 pounds. | |
| 135706-141385 2011-12-02 | Fluid Catalytic Cracking | Cause: Hydrogen Cyanide is being released from the Fluid Catalytic Cracking, but no information was given on the cause of the release (based on first written notification).
(There was an initial followup on 8/17/2012 and a final follow up on 1/8/2013 - the following information is from follow up report 8/17/2012): The refinery is reporting a statistically significant increase above the upper bound of the initial reported quantity for hydrogen cyanide (HCN).
The increase is based on stack testing on the Fluid Catalytic Cracking Unit Wet Gas Scrubber. Followup: Yes Notes: This is a continuous without interruption release of Hydrogen Cyanide from a 250 foot Fluid Catalytic Cracking unit. ExxonMobil reported the initial release based on a change in methodology as a result of the EPA Information Collection Request and subsequent test data becoming publicly available to other facilities. In the Section II Source Information it states that the normal range for HCN has a lower bound of 44.63 lbs/day and an upper bound of 444.3 lbs/day. Per year, the lower bound would result in 16289.95 lbs/year and the upper bound would result in 162169.5 lbs/year of HCN. If ExxonMobil reported the median of these bounds, the reported amount would be 244.47 lbs/day, or 89229.73 lbs/year. The total quantity released over the year reported by ExxonMobil was 22,000 lbs/year. Breaking this down, they are saying that 60.27 lbs/day of HCN was being released, which much closer to their lower bound limit (44.63 lbs/day). In the written notification they state that they have now found that they are releasing a statistically significant increase above their upper bound (444.3 lbs/day), meaning there is a discrepancy between their reported release amounts. In the initial written notification, Exxon reported a release of 82 lbs/day in the upper bound and 25.6 lbs/day in the lower bound. The reportable quantity for a continuous release of Hydrogen Cyanide is 10 lbs/day. | Hydrogen Cyanide: 22,000.0 pounds |
| 135083 2011-10-30 | No information given | Cause: ExxonMobil Baton Rouge Refinery provided a written notification to the LDEQ about a release that occurred at the facility on October 30, 2011. Approximately 24 pounds of Methyl Ethyl Ketone and Methyl Isobutyl Ketone were release. Followup: No Notes: No information given. 24 pounds approximately released. Approximately 12 pounds of each was assumed from broad description for numerical accounting. LABB does not have access to the LDEQ incident report. | Methyl Ethyl Ketone: 12.0 pounds MIBK(Methyl Isobutyl Ketone): 12.0 pounds |
| 134920 2011-10-27 | No information given | Cause: ExxonMobil Baton Rouge Refinery provided a written notication to the LDEQ of the events and circumstances surrounding the release that occurred on October 27, 2011, at the facility. Less than 1 pound of the listed hazardous waste F037, primary sludge, was spilled to soil. After further evaluation, ExxonMobil has determined that no reportable quantities were exceeded. Followup: No Notes: No information given. | F037 Hazardous Waste: 1.0 pounds |
| 133485 2011-08-25 | No information given | Cause: ExxonMobil Baton Rouge Refinery wrote a letter to the LDEQ as notification of the events and circumstances surrounding the oil spill that occurred at the facility on August 25, 2011. Due to prompt incident response to mitigate the event duration, no reportable quantities were exceeded. Approximately 15 gallons of diesel were released. There were no complaints, injuries, or offsite impact as a result of this incident. Soil remediation is underway. Followup: No Notes: Soil remediation is underway. | Diesel Fuel: 15.0 gallons |
| 132863 2011-08-02 | NIG | Cause: No information provided about the cause of an 18 gallon oil release. Followup: No Notes: Soil was re-mediated. No RQs were exceeded as a result of this event. 6 gallons of oil reached off site. LABB does not have access to the LDEQ incident report. | Oil: 18.0 gallons |
| 132752 2011-07-27 | CT-39 | Cause: A release of benzene was discovered when a routine sampling of cooling water tower was analyzed. The release occurred from cooling tower CT-39. No information about what caused the leak. Followup: No Notes: After further testing the cooling tower water, no RQs were exceeded. | |
| 132481 2011-07-18 | Cooling Tower 39 | Cause: Cooling Tower 39 sample had high VOC content, but no information is provided about the cause of the release. Followup: No Notes: This release does not exceed reportable quantity. The RQ for VOCs by the LDEQ is 5,000 pounds. | Volatile Organic Compounds (VOCs): 1,829.0 pounds |
| 132049 2011-06-24 | Cooling tower 39 | Cause: Notification was given that there was a potential leak at cooling tower 40. Diesel was seen in sample results without physical signs. It was later determined that the sample result for cooling tower 39 was erroneously reported as being from cooling tower 40. Cooling tower 39 was already reported as having a leak. Followup: No Notes: No remedial actions reported. Exxon Refinery found exchangers that might be the source of the tower 39 leak and fixed those. The facility also took a new sample and the TOC levels are now normal. Cooling tower 39 has previously been reported as having a leak, as discovered during routine sampling using El Paso method (LSP incident #11-03335 and 11-03511) and all emissions from it will be reported under those incident numbers. | |
| 131949 2011-06-21 | flange fire | Cause: ExxonMobil Baton Rouge Refinery provided a written notification to the LDEQ on June 21, 2011 of the events and circumstances surrounding the flange fire that occurred at the facility. After further evaluation, they have determined that no reportable quantities were exceeded. Approximately 127 pounds of material were released during the event, excluding any combustion effects. Upon discovery, steam was applied to the flange to extinguish the fire until flange bolts could be tightened. Followup: No Notes: Steam was applied to the flange to extinguish the fire until flange bolts could be tightened. | No Information Given: 127.0 pounds |
| 131867 2011-06-17 | No Information Given | Cause: Sulfur dioxide was released when hydrogen gas was flared. No further information given. Followup: No Notes: BRQ. Flaring only lasted 8 minutes. No further information was given. | Sulfur Dioxide: 59.0 pounds |
| 131860 2011-06-16 | Cooling Tower | Cause: ExxonMobil Baton Rouge Refinery wrote a notification to the LDEQ of the events and circumstances surrounding the sample results indication there was a release to a cooling tower at the facility on June 16, 2011. After further evaluation, ExxonMobil determined that no reportable quantities were exceeded. The results were erroneously high, and there was no release to the cooling tower. Followup: No Notes: There was no release. | |
| 131217 2011-05-14 | No Information Given | Cause: An oil sheen was reported in ExxonMobil's Baton Rouge Refinery #2 Basin and Callahan Bayou with an oil sheen of 20x30 feet. No further information was given. There was offsite impact at Callahan Bayou. Followup: No Notes: This release is BRQ. The approximate amount of oil released was about 10 gallons. LDEQ report states that the sheen was cleaned the same day it was discovered. LABB only has access to the LDEQ incident report. | Oil: 10.0 gallons |
| No LDEQ Reported 2011-04-07 | No Information Given | Cause: No Information Given. Followup: No Notes: BRQ. No Information Given. LABB only has access to the Refinery letter and not the LDEQ or SPOC incident report. | |
| 130413 2011-04-03 | FLARE | Cause: LDEQ states that when bringing a unit online, flaring occurred. Followup: No Notes: BRQ. The unit was secured. | Sulfur Dioxide: 153.0 pounds |
| 129998 2011-03-22 | Cooling Tower | Cause: Refinery letter states that a cooling tower release occurred. After further evaluation, it was determined that results from the samples were erroneously high as confirmation samples did not indicate a release. Followup: No Notes: This release was BRQ. No further information given. LABB only has access to the refinery report and not the LDEQ incident report. | |
| 129080 2011-02-07 | Unspecified line | Cause: There is no information regarding the cause, but oil was observed below the line and a small vapor was seen coming from the line. Followup: No Notes: The majority of what was released was water. The line was repaired. The incident date on the SPOC report and LDEQ (2/7/11) do not coincide with the incident date on the Incident Report (2/6/11) submitted by the refinery. Wrong Date Reported. | |
| 143315 2012-09-21 | No information given | Cause: From the verbal report, states that there was a crack in the primary burner at the sulfur plant. Followup: No Notes: SPOC report states that H2S was being released, but details not clear if it exceeded the 100 lbs RQ, 500 lbs of SO2 was released, and that the material did go offsite. The highest air monitoring readings inside the facility were 11-20 ppm. | Sulfur Dioxide: 67.0 pounds |
| 143115 2012-09-19 | NIG | Cause: A release occured at ExxonMobil Baton Rouge Refinery. Followup: No Notes: Due to prompt incident response to mitigate the event duration no reportable quantities were exceeded. The refinery letter fails to mention what pollutant was released. | |
| 141608 2012-07-30 | No Information Given | Cause: Followup: No Notes: Prompt incident response to mitigate the event duration. | Flammable Vapor: 385.0 pounds |
| 140708 2012-06-25 | analyzer supply line | Cause: An analyzer supply line was discovered leaking. Followup: No Notes: Upon discovery the liquid material was collected on absorbent pads, and properly disposed of. The line was immediately isolated and depressured to stop the leak. | Toluene: 7.8 pounds Xylene: 10.4 pounds Volatile Organic Compounds (VOCs): 7.8 pounds |
| 138624 2012-04-03 | FLARE: Flare #5 | Cause: The facility is unsure what caused the flare of SO2 at flare #5. Followup: No Notes: There is no information regarding remedial actions. Initially ExxonMobil Refinery reported approximately 500 lbs of sulfur dioxide being released in their verbal notification to the LDEQ, but in their 7 day letter they reported that less than one pound of sulfur dioxide was released. ExxonMobil Refinery did not monitor the air during this event. | Sulfur Dioxide: 1.0 pounds |
| 138531 2012-03-31 | NIG | Cause: The facility made the report an employee noticed approximately 20 gallons of oil in an existing excavation hole inside the facility. Followup: No Notes: In the intial phone call at 11:02 AM on 3/31/2012 the employee stated that a vacuum truck was onsite vacuuming up the oil, while looking for the source of the leak. In a follow-up call at 11:11 PM on 3/31/2012 the employee stated that there was no off-site impact, and that excavation was located at Avenue F inside the facility. A letter of notification/unauthorized discharge report was submitted on 4/5/2012, stating that no reportable quantities were exceeded, and the quantity of spilled oil was raised from 20 gallons to 23.4 gallons spilled to soil. | Crude Oil: 23.4 gallons |
| 138106 2012-03-20 | No information given | Cause: Followup: No Notes: There is no information given regarding the cause or the remedial actions of this release. LABB does not have access to the LEDQ report or the SPOC report. | Flammable Vapor: 785.0 pounds |
| 1286550 2012-03-12 | Furnaces, Incinerators Crude Tanks | Cause: This is an update on a continuous release notification submitted by ExxonMobil on 1/18/2011. The 2011 report has the same incident number, and is filed in this database under 128655 (SERNO # 4813), without a following zero, to keep the two reports in their respective years.
This report serves as written notification to comply with 40 CFR 302.8, which requires the owner or operator of facility to submit written follow up information for the verbal reporting of a continuous release(CRR). On October 10, 2010 Exxon Mobil Corporation's Baton Rouge Refinery made an initial notification to the NRC, the LA State Police Hazardous Materials Unit, the East Baton Rouge Parish Fire Department, and the LDEQ of the Refinery's continuous releases of hydrogen sulfide. Per continuous release reporting requirements, a one-time follow up report will be filed within thirty days of the anniversary of the source change. Thereafter, annual reassessments will be issued if there is a Statically Significant Increase or a change in the source of release. Followup: No Notes: On March 12, 2013, a first anniversary follow-up letter to initial notifications made in February 2012 of a change in sources of the continuous releases of hydrogen sulfide with updates on these sources and amount release. In addition to continuous release from furnaces and incinerators, ExxonMobil identified the potential for hydrogen sulfide to be present in selected crude and process oil streams. Exxon Mobil has submitted a permit renewal to the LDEQ to incorporate hydrogen sulfide emissions in crude tanks. For 2012-2013, estimates for the rate of release of hydrogen sulfide ranged from 5 lb/day to 14 lb/day from furnaces and incinerators. This corresponds to annual emissions of 1825 lbs for the lower bound and 5110 lbs for the upper bound. LABB researchers have averaged these two estimates for the release amount here. ExxonMobil's total estimate of hydrogen sulfide releases from crude tanks was 54 lb for the year, which is slightly below the lower bound rate of 0.15 lb/day. The lower bound for daily emissions is .15 lbs/day and the upper bound is .58 lb/s day. This corresponds to annual emissions of 54.75 lbs for the lower bound and 211.7 lbs for the upper bound. LABB researchers have averaged these two estimates for the release amount included here. | Hydrogen Sulfide: 3,467.5 pounds Hydrogen Sulfide: 133.2 pounds |
| No LDEQ Reported 2012-03-08 | No information given | Cause: There is no information given regarding the cause of the release of MEK/MIBK and waxy feed. Followup: No Notes: There is no information regarding cause or remedial actions. LABB does not have access to the LDEQ report and this incident was not processed by SPOC. Approximately 4 gallons of MEK/MIBK solvent and 6 gallons of waxy feed were released. | MIBK(Methyl Isobutyl Ketone): 2.0 gallons Methyl Ethyl Ketone: 2.0 gallons Waxy Feed: 6.0 gallons |
| 142210 2012-02-24 | No Information Given | Cause: Less than 1 lb of H2S was released as a result of this event. Followup: No Notes: The report was made later than 7 days after the incident and verbal notification occurred. | Hydrogen Sulfide: 1.0 pounds |
| 152638 2013-12-01 | No Information Given | Cause: Flaring occurred at the ExxonMobil Baton Rouge Refinery (BRRF) on December 1, 2013. Approximately 0.75 pounds of PAH and 214 pounds of VOC were released. Followup: No Notes: After further evaluation, ExxonMobil Baton Rouge Refinery determined that no reportable quantities were exceeded. | Polycyclic Aromatic Hydrocarbons: 0.8 pounds Volatile Organic Compounds (VOCs): 214.0 pounds |
| 152556 2013-11-21 | No Information Given | Cause: Followup: No Notes: After further review, ExxonMobil Baton Rouge Refinery determined that no reportable quantities were exceeded. | |
| 152163 2013-11-05 | Unknown | Cause: Remediation water well material released onto soil due to a leak in a line. Cause unknown. Followup: No Notes: Exxon Mobil evaluated that no reportable quantities were exceeded. In the SPOC report, there was a report that 2-3 barrels of unknown chemical were found in the water-well material and clean up was unknown. | Unknown Liquid: 126.0 gallons |
| 152086 2013-10-30 | No Information Given | Cause: Followup: No Notes: Due to prompt incident response to mitigate the event duration, no reportable quantities were exceeded. | Benzene: 5.0 pounds Flammable Vapor: 29.0 pounds Volatile Organic Compounds (VOCs): 140.0 pounds |
| 151767 2013-10-22 | Combined cooling tower return line | Cause: Followup: No Notes: Initial El Paso sampling of the combined cooling tower return line indicated a leak rate of 16 lbs/day of hydrogen sulfide and 7 lbs/day of benzene. Additional sampling was performed on the individual cooling tower return lines that combine to become the main line that was initially tested. Results from this additional sampling of the three individual lines showed no active leak. With this additional information, it was determined that there were issues with the original sampling of the combined return line. Therefore, no reportable quantities were exceeded as a result of this event. | |
| 151830 2013-10-22 | No Information Given | Cause: Followup: No Notes: Initial verbal notifications were completed by K. Joseph to Louisiana State Police at 11:25am, LDEQ via SPOC, East Baton Rouge LEPC at 11:30, and the NRC at 11:35am. Due to prompt incident response to mitigate the event duration, no reportable quantities were exceeded. | Hydrogen Sulfide: 9.0 pounds |
| 151605 2013-10-11 | No Information Given | Cause: Letter serves as written notification of the events and circumstances surrounding the flaring that occurred at the ExxonMobil Baton Rouge Refinery on Oct 11, 2013. Courtesy notifications were completed by V. Stewart to the Louisiana State Police at 8:52 pm adn LDEQ via SPOC. Followup: No Notes: No reportable quantities were exceeded as result of this event. | |
| 150874 2013-09-08 | No Information Given | Cause: A refinery letter dated September 13, 2013 serves as a notification surrounding an event dated September 8, 2013. No reportable quantities were exceeded as a result of this event. No additional information was provided beyond this information. Followup: No Notes: No reportable quantities were exceeded as a result of this event. The substance released was also not made available in the refinery report. The duration and point source were also not provided. | |
| 150820 2013-09-04 | No Information Given | Cause: Followup: No Notes: Due to prompt incident response to mitigate the event duration, we have determined that no reportable quantities were exceeded. | Hydrogen Sulfide: 1.0 pounds |
| No LDEQ Reported 2013-06-07 | No Information Given | Cause: On June 7, 2013, there was an oil spill that occurred at the ExxonMobil Baton Rouge Refinery. Approximately 1 pint of jet fuel was released into the Mississippi River. Followup: No Notes: Due to prompt incident response to mitigate the event duration, we have determined that no reportable quantities were exceeded. | Fuel: 0.1 gallons |
| 148727 2013-05-15 | Sewer | Cause: On May 15, 2013 at approximately 8:20 a.m. Exxon Mobil received an odor complaint from an employee checking the sewer seal box near the KDLA unit along 15th street. Upon further investigation light hydrocarbon material was detected coming from the sewer. Precautionary safety measures were taken by limiting access to this area within the facility. Air monitoring was conducted at the sewer grade, 6 feet away from the sewer, and along the fence line. Directly at the sewer Exxon Mobil received a maximum benzene reading of 8 pp. Six feet away from the closed sewer and at the fence line all readings for benzene and VOC were below the detection limit 0.05 ppm and 1 ppm respectively. Followup: No Notes: The sewer system was flushed at approximately 11:50 a.m. and an all clear notice was given at approximately 12:30 p.m. Due to prompt incident response to mitigate the event duration, no reportable quantities were exceeded. Less than 1 pound of benzene and VOC were released as a result of this event. | |
| 148805 2013-05-15 | No Information Given | Cause: On May 15, 2013, a release of benzene occurred at the ExxonMobil Baton Rouge Refinery. Due to prompt incident response to mitigate the event duration, it was determined that no reportable quantities were exceeded. Followup: No Notes: | Benzene: 9.2 pounds |
| 147078 2013-02-28 | NIG | Cause: Approximately 355 pounds of flammable vapor were released on February 28, 2013. No reportable quantities were exceeded. No information was provided regarding the point source or duration of this release. Followup: No Notes: | Flammable Vapor: 355.0 pounds |
| 146414 2013-02-02 | storage tank | Cause: On February 2, 2013, a tank roof separated from the rim of tank releasing material to air. Initial contact with SPOC indicated a possible release exceeding 1 pound RQ limit of PAHs. The rim had separated from the roof of a storage tank at the facility. The tank was isolated. No estimate was available of how much material the tank contained. At approximately 5:08pm, Louisiana State Police was notified of a potential release of hydrogen sulfide over the reportable quantity. Followup: No Notes: Flow to the tank was shut off. SPOC states that caller reported 6ppm for VOCs during one update call. | |
| No LDEQ Reported 2013-01-15 | NIG | Cause: Oil sheen discovered in Callahan Bayou at the ExxonMobil Baton Rouge Refinery on January 15, 2013. The current LPDES permit, effective October 2012 (LA0005584, Part1, Page 5 of 5) states "There shall be no visible sheen or stain attributable to this discharge in the drainage area downstream from the permitted outfall. The drainage area downstream is defined as the area in the outfall canal located downstream of any control device, prior to entering the main channel of the Mississippi River." Followup: Yes Notes: All material was contained within the last containment boom prior entering into the Mississippi River. After further evaluation, we have determined that no reportable quantities were exceeded. Approximately 1 pint of diesel was release into Callahan Bayou. | Diesel Fuel: 0.1 gallons |
| 145689 2013-01-03 | NIG | Cause: At 11:24 AM ExxonMobil notified the LSP that approximately 734 pounds of flammable vapor were released. No information was given about the root cause of the event. Followup: No Notes: LABB's file only contains the letter from the refinery dated 1/10/13, but no LDEQ or SPOC report. | Flammable Vapor: 734.0 pounds |
| 160387 2014-12-03 | Cooling tower | Cause: Exxonmobil had a cooling tower leak in the parking lot that is used for air conditioning. Water leaked onto Scenic Highway. Exxon reported that no chemicals or hydrocarbons were spilled. Followup: No Notes: At time of report to Louisiana Department of Environmental Quality, Exxon was working to isolate the leak. | |
| 160151 2014-11-18 | No information given | Cause: Release of flammable vapor, hydrogen sulfide and ammonia between 11/18 and 11/22. No information about accident cause given. Followup: No Notes: | Flammable Vapor: 488.0 pounds Hydrogen Sulfide: 294.0 pounds Ammonia: 35.0 pounds |
| 160130 2014-11-17 | None Reported | Cause: Release occurred at the ExxonMobil Refinery on November 17, 2014. No information given about release or accident cause. Followup: No Notes: | |
| 159495 2014-10-13 | No information given | Cause: Oil spill reported at ExxonMobil Refinery. Report states no reportable quantities were exceeded and no information given about accident cause. Followup: No Notes: | Benzene: 4.5 pounds Flammable Vapor: 264.0 pounds Oil: 39.0 gallons |
| 159407 2014-10-12 | No information given | Cause: Release of methyl ethyl ketone, Methyl isobutyl ketone, flammable vapor and volatile organic compounds. No information about accident cause provided. Followup: No Notes: | Methyl Ethyl Ketone: 198.0 pounds MIBK(Methyl Isobutyl Ketone): 395.0 pounds Flammable Vapor: 395.0 pounds Volatile Organic Compounds (VOCs): 395.0 pounds |
| 159404 2014-10-10 | No information given | Cause: Release of hydrogen sulfide on October 11, 2014. No information given about cause of accident. Followup: No Notes: | Hydrogen Sulfide: 22.0 pounds |
| 159209 2014-10-06 | None Reported | Cause: Exxon reported a potential reportable quantity exceedance on 10/6/14. Upon further review, they determined that no reportable quantities were exceeded. Followup: No Notes: | |
| 159147 2014-10-02 | No information given | Cause: Release of flammable vapor, methyl ethyl ketone and Methyl isobutyl ketone at ExxonMobil on October 2. No other information given about cause of accident. Followup: No Notes: | Flammable Vapor: 410.0 pounds Methyl Ethyl Ketone: 328.0 pounds MIBK(Methyl Isobutyl Ketone): 82.0 pounds |
| 158761 2014-09-12 | No Information Given | Cause: No Information Given Followup: No Notes: No Information Given | Hydrogen Sulfide: 0.1 pounds |
| 158161 2014-08-18 | No Information Given | Cause: No Information Given on event, only that approximately 9.8 gallons of gas oil were released to the soil as a result. Followup: No Notes: No Information Given, prompt incident response mitigated the event duration. | Gas Oil: 9.8 gallons |
| 157412 2014-07-14 | no information given | Cause: Followup: No Notes: | Polycyclic Aromatic Hydrocarbons: 0.0 pounds |
| 157413 2014-07-14 | No Information Given | Cause: Followup: No Notes: | Volatile Organic Compounds (VOCs): 52.0 pounds Flammable Vapor: 100.0 pounds |
| 156772 2014-06-11 | No Information Given | Cause: An incident resulted in the release of approximately 1,562 pounds of Volatile Organic Compounds and 244 pounds of flammable vapor. Followup: No Notes: | Volatile Organic Compounds (VOCs): 1,562.0 pounds Flammable Vapor: 244.0 pounds |
| No LDEQ Reported 2014-06-10 | No Information Given | Cause: An oil sheen was discovered in Callahan Bayou at the ExxonMobil Baton Rouge Refinery. Followup: No Notes: All material was contained with the last containment boom prior to entering the Mississippi River. | Oil: 0.0 gallons |
| 155849 2014-05-08 | None Reported | Cause: No information about cause of accident, unit involved or amounts released.
Report states that following initial sample results, additional sampling was performed using the El Paso Method. Sampling using the El Paso Method showed a release, but no active leak. Followup: No Notes: | |
| 155808 2014-05-06 | Storage Tank | Cause: While loading material into a storage tank, the tank overfilled and material spilled into the containment area. Spilled material was then directed into a wastewater facility but some leached into soil. Followup: No Notes: Release was stopped and cleanup was initiated. Material spilled into a containment area, then was directed through the sewer system to be treated in the wastewater facility. | Calcium hydroxide: 2,441.0 pounds |
| 155266 2014-04-15 | Cooling Water Tower | Cause: On 04/15/2014 at 11:19, ExxonMobile received a high reading on a cooling tower water sample. A follow up letter from refinery on 04/22/2014 indicates that release was below reportable quantity Followup: No Notes: No information given. ExxonMobile designated event as non-emergency release. | |
| 155128 2014-04-07 | No Information Given | Cause: Approximately 20 pounds of highly-reactive volatile organic compounds and 538 pounds of flammable vapor were released during this event. Followup: No Notes: Prompt incident response mitigated the event duration. | Highly Reactive Volatile Organic Compounds: 20.0 pounds Flammable Vapor: 538.0 pounds |
| 155023 2014-04-02 | No Information Given | Cause: Approximately 528 pounds of flammable vapor was released during this event. Followup: No Notes: Prompt incident response mitigated the event duration. | Flammable Vapor: 528.0 pounds |
| 154203 2014-02-27 | None Reported | Cause: One February 27, 2014 at approximately 2:57, the Far East Coker unit experienced an unplanned combustion incident (UCI) from an unknown leaking source. Feed was immediately taken out of the unit and a water spray was applied to minimize air emissions. Followup: Notes: The incident is under investigation to determine the root cause and material emitted to the air and to provide mitigating steps to prevent recurrence. Details of the investigation will be provided in a 60-day follow-up notification. | |
| 154029 2014-02-21 | NIG | Cause: On February 21, 2014 at the ExxonMobil Baton Rouge Refinery (BRRF), 82 pounds of flammable vapor were released. Followup: No Notes: Prompt incident response mitigated event duration. | Flammable Vapor: 82.0 pounds |
| 153956 2014-02-17 | NIG | Cause: On February 17, 2014, there was a release of 565 lbs of propane at the ExxonMobil refinery in Baton Rouge, LA. There were no reportable quantities exceeded. Followup: No Notes: | Propane: 565.0 pounds |
| 153723 2014-02-07 | Cause: Flaring occurred at the ExxonMobil Baton Rouge Refinery (BRRF). Followup: No Notes: No reportable quantities were exceeded. | Sulfur Dioxide: 189.0 pounds Highly Reactive Volatile Organic Compounds (HRVOCs): 0.5 pounds | |
| 153588 2014-01-28 | NIG | Cause: On January 28, 2014, flaring occurred at the refinery due to an unknown cause. Followup: No Notes: | Sulfur Dioxide: 19.0 pounds Highly Reactive Volatile Organic Compounds (HRVOCs): 0.1 pounds |
| 153571 2014-01-25 | NIG | Cause: On January 25, 2014 at 09:15, there was a release of volatile organic compounds (VOCs) from a process unit leak. Followup: No Notes: To secure the leak, the unit of origin was in the process of shutting down. State police notification states that VOC readings 60 ft away from the incident has a reading of 6.8 ppm, VOC reading at 120 ft away has no reading. | Volatile Organic Compounds (VOCs): 180.0 pounds |
| 153389 2014-01-14 | NIG | Cause: On January 14, 2014, a release of benzene and hydrogen sulfide was released. Followup: No Notes: Only document related to accident that LABB has access to is a one-page refinery letter dated January 21, 2014. | Benzene: 6.0 pounds Hydrogen Sulfide: 0.0 pounds |
| 153226 2014-01-09 | NIG | Cause: On January 9, 2014, a release of sulfur dioxide was reported. Followup: No Notes: The only document related to this accident that LABB has access to is a one-page refinery letter dated January 16, 2014. | Sulfur Dioxide: 260.0 pounds |
Connect With Us: