Deaths from Static Sparks

Jump to Last Post 1-3 of 3 discussions (6 posts)
  1. ngureco profile image82
    ngurecoposted 10 years ago

    Saturday, January 31st. 2009: In Molo, Nakuru, Kenya - 91 people are dead and over 100 others are injured after a petrol truck overturned and the surrounding community gathered with containers to benefit from the free fuel. With the volatile gasoline, the fumes of petrol and static electricity (relative humidity was below 25%), one of the villagers must have ignited static spark and then an explosion. It is a pity tens of souls has been lost this way.

    They can comfort themselves that one of them must have been smoking a cigarette but that is not true. The next time they get another truck, they will say, "no smoking", but the explosion will still happen.

    More on Static Sparks and Your Safety Here.

    1. ngureco profile image82
      ngurecoposted 10 years agoin reply to this

      The number of the dead has since gone up to 111 and over 176 others are injured.

    2. mohitmisra profile image60
      mohitmisraposted 10 years agoin reply to this

      This explosion is called BLEVE  or Boiling Liquid Evaporation  Vapor Explosion.It is extremely deadly and cannot be stopped.Initially there is too much gas- carbon content in the vehicle and it cannot explode.The gas leaks out and when the carbon vapor  reaches a flash point ,proper mixture of carbon and oxygen,the fumes ignite and  the vehicle explodes.Similar to oil tanker -ships and petrol pumps.Its possible someone dropped something metallic which let of  a spark.
      There are incidents when people stopped to look at a a burning tanker on a highway and got seriously injured and some died standing a kilometer away from the tanker due to the blast-shrapnel's.

  2. Jesus_saves_us_7 profile image63
    Jesus_saves_us_7posted 10 years ago

    this is so sad, and all because of static sad

  3. ngureco profile image82
    ngurecoposted 10 years ago

    In this case, the tanker overturned and there was a flood of petrol all over the tarmac. They say explosion happened after about 30 minutes. People scrabbled for the free gasoline with the hope they can resell it for some cash. The air was dry and relative humidity was low meaning the natural discharge of static electricity in their bodies through the air was poor. There was a high concentration of petrol fumes in the air and all it required was just a tiny spark for explosion to be complete. With a gathering of over 500 people and a relative humidity of less than 25%, this was almost 100% sure a static spark was to be achieved. And it was achieved and explosion occurred.

    The explosion heated the air creating a very low pressure sufficient to pull your lungs. People may have tried to escape but must have been pulled by the low pressure from left and right to the centre where fire was.

    The sad thing is that people will do it again and again because they have been led to believe these fires are started by one of them smoking a cigarette. Next time when a gasoline tanker overturns, they will say “make sure this time none of us smokes a cigarette” and the explosion will still happen.

    The death toll has now risen to 120.

    1. mohitmisra profile image60
      mohitmisraposted 10 years agoin reply to this

      In this case, the tanker overturned and there was a flood of petrol all over the tarmac.
      Where the fuel exits from the tanker  is where the fire will start.This fire will then spread inside the tanker when the carbon  oxygen ratio is correct which causes it to explode. Bronze coated tools are used to prevent static sparks. smile


This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

Show Details
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)