Reducing Risk of Spontaneous Combustion

Industry and academia work together to find a solution to the common biodiesel fire hazard of spontaneous combustion, which occurs when heat, resulting from chemical or biological reactions, accumulates in loosely piled flammable materials.
By Rob Fransham and Jon Van Gerpen | November 11, 2014

Biodiesel-coated materials can, in rare circumstances, spontaneously ignite causing damage both large and small. Much information on this phenomenon is available, including in Biodiesel Magazine archives. The mechanisms of biodiesel spontaneous combustion are not completely understood, which is why it is one of the subjects that the University of Idaho has researched for the USDA.

Spontaneous combustion occurs when heat, resulting from chemical or biological reactions, accumulates in loosely piled flammable materials. The resulting rise in temperature accelerates the reaction rate, which further increases the temperature, culminating in smoke and open flame. Biodiesel feedstocks with at least two double bonds in their carbon chains are particularly susceptible to oxidative reactions and are a greater risk than petroleum-based fuels, which have almost no double bonds in their structures. In addition to an oxidation-prone fuel, spontaneous combustion requires that the fuel have access to sufficient air to oxidize the fuel but not too much air circulation, which could cause the heat of reaction to be dissipated. This situation frequently involves fuel-soaked rags or filter media.

Plant operators and biodiesel transporters are encouraged to use good housekeeping practices to lessen the risk of a fire. A solution recommended by many is to store biodiesel-contaminated absorbent materials under water in a closed container. That solution, in Texon’s experience, is only temporary because eventually the biodiesel-coated material is removed from the container and when the water evaporates the biodiesel is again exposed to air.

At its biodiesel terminal site in Houston, Texon uses spun fiberglass cartridge filters in the biodiesel truck offloading system to protect the system from debris. After those filters accumulate contaminants they are removed and drained and stored in a waste receptacle. Texon’s recent experience was that, when exposed to the Houston summer heat without water submersion, a portion of the used filter elements could heat up enough to create visible smoke and some melting of the plastic container. Even with water submersion, in our experience, similar heat damage could occur as quickly as 24 hours after the filters were removed from the water bath.

A simple solution was employed at Texon’s site that has reduced its risk of spontaneous combustion, at a reasonable cost. Used filter elements were first submerged in a motor oil bath for a few minutes, and then allowed to drain before placing in the waste container. To ensure that there was no spontaneous combustion, the oil-treated filters were monitored for two weeks before they were released for disposal. Apparently, the biodiesel is leached from the filter elements into the motor oil and is replaced by the oil itself, which is much more oxidatively stable. Motor oil consists mostly of saturated hydrocarbon molecules with large amounts of antioxidants that serve to slow the degradation of the oil as it lubricates the engine. This lack of double bonds and the presence of antioxidants slows the heat production process so that natural dissipation of the heat of reaction lowers the ability to reach combustion temperatures.

A motor oil-wetted filter is easily recycled by the oil filter recycling industry, allowing for safe and efficient disposal. Eventually, the motor oil bath accumulates enough biodiesel contamination that Texon disposes of the oil via the waste fuels industry. The risk of spontaneous combustion in this specific situation was reduced by a simple and safe technique. We believe that this approach can be used in many other situations to reduce biodiesel handling risks. Of course, every plant or terminal operator should evaluate its own risks and determine its own best practices based on its unique circumstances and conditions.

An industry that shares safety best practices among themselves makes everyone better able to protect their employees, the communities within which we operate, and the industry itself. The authors present this safety tip with that principle in mind.

Authors: Rob Fransham, Jon Van Gerpen
Renewable Fuels General Manager, Texon LP
Associate Dean for Research, College of Engineering, University of Idaho
[email protected]
[email protected]

Array ( [REDIRECT_REDIRECT_HTTPS] => on [REDIRECT_REDIRECT_SSL_TLS_SNI] => [REDIRECT_REDIRECT_STATUS] => 200 [REDIRECT_HTTPS] => on [REDIRECT_SSL_TLS_SNI] => [REDIRECT_STATUS] => 200 [HTTPS] => on [SSL_TLS_SNI] => [HTTP_HOST] => [HTTP_CONNECTION] => Keep-Alive [HTTP_ACCEPT_ENCODING] => gzip [HTTP_X_FORWARDED_FOR] => [HTTP_CF_RAY] => 7701de397ac62028-IAD [HTTP_X_FORWARDED_PROTO] => https [HTTP_CF_VISITOR] => {"scheme":"https"} [HTTP_USER_AGENT] => CCBot/2.0 ( [HTTP_ACCEPT] => text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 [HTTP_ACCEPT_LANGUAGE] => en-US,en;q=0.5 [HTTP_CF_CONNECTING_IP] => [HTTP_CF_IPCOUNTRY] => US [HTTP_CDN_LOOP] => cloudflare [PATH] => /sbin:/usr/sbin:/bin:/usr/bin [SERVER_SIGNATURE] =>
Apache/2.2.15 (CentOS) Server at Port 443
[SERVER_SOFTWARE] => Apache/2.2.15 (CentOS) [SERVER_NAME] => [SERVER_ADDR] => [SERVER_PORT] => 443 [REMOTE_ADDR] => [DOCUMENT_ROOT] => /datadrive/websites/ [SERVER_ADMIN] => [email protected] [SCRIPT_FILENAME] => /datadrive/websites/ [REMOTE_PORT] => 29540 [REDIRECT_QUERY_STRING] => url=articles/235761/reducing-risk-of-spontaneous-combustion [REDIRECT_URL] => /app/webroot/articles/235761/reducing-risk-of-spontaneous-combustion [GATEWAY_INTERFACE] => CGI/1.1 [SERVER_PROTOCOL] => HTTP/1.1 [REQUEST_METHOD] => GET [QUERY_STRING] => url=articles/235761/reducing-risk-of-spontaneous-combustion [REQUEST_URI] => /articles/235761/reducing-risk-of-spontaneous-combustion [SCRIPT_NAME] => /app/webroot/index.php [PHP_SELF] => /app/webroot/index.php [REQUEST_TIME_FLOAT] => 1669457780.872 [REQUEST_TIME] => 1669457780 )