<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>INDIATAB &#187; death</title>
	<atom:link href="http://www.indiatab.com/tag/death/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.indiatab.com</link>
	<description>Latest news, videos, classifieds from india and abroad</description>
	<lastBuildDate>Tue, 29 Nov 2011 06:06:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>Human error caused Jaipur IOC terminal fire</title>
		<link>http://www.indiatab.com/news/national/human-error-caused-jaipur-ioc-terminal-fire/550/</link>
		<comments>http://www.indiatab.com/news/national/human-error-caused-jaipur-ioc-terminal-fire/550/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 17:37:45 +0000</pubDate>
		<dc:creator>Amitabh Banik</dc:creator>
				<category><![CDATA[National]]></category>
		<category><![CDATA[death]]></category>
		<category><![CDATA[fire]]></category>
		<category><![CDATA[ioc]]></category>
		<category><![CDATA[jaipur]]></category>

		<guid isPermaLink="false">http://www.indiatab.com/?p=550</guid>
		<description><![CDATA[New Delhi, Feb 2 (IANS) Human failure, lack of observance of safety guidelines, defunct devices and faulty safety audits seemed to be some of the reasons for the fire at the Indian Oil Corp terminal in Jaipur in October last year, an independent inquiry committee has found out. “The basic or root cause is an [...]]]></description>
		<wfw:commentRss>http://www.indiatab.com/news/national/human-error-caused-jaipur-ioc-terminal-fire/550/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

