<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:media="http://search.yahoo.com/mrss/"
	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>NJ | George Hatcher's Air Flight Disaster</title>
	<atom:link href="https://airflightdisaster.com/tag/nj/feed/" rel="self" type="application/rss+xml" />
	<link>https://airflightdisaster.com</link>
	<description>Aviation News, Headlines &#38; Alerts</description>
	<lastBuildDate>Tue, 15 Jul 2014 02:36:25 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>Air India Emergency Bird Strike in Newark NJ</title>
		<link>https://airflightdisaster.com/air-india-emergency-bird-strike-in-newark-nj/</link>
		
		<dc:creator><![CDATA[GJHatcher]]></dc:creator>
		<pubDate>Tue, 15 Jul 2014 02:29:17 +0000</pubDate>
				<category><![CDATA[Air India]]></category>
		<category><![CDATA[bird strike]]></category>
		<category><![CDATA[Boeing]]></category>
		<category><![CDATA[Diversion]]></category>
		<category><![CDATA[Emergency]]></category>
		<category><![CDATA[engine shut down]]></category>
		<category><![CDATA[engine stall]]></category>
		<category><![CDATA[engine trouble]]></category>
		<category><![CDATA[hard]]></category>
		<category><![CDATA[USA]]></category>
		<category><![CDATA[Boeing 777]]></category>
		<category><![CDATA[George Hatcher]]></category>
		<category><![CDATA[NJ]]></category>
		<category><![CDATA[wrongful death]]></category>
		<guid isPermaLink="false">http://airflightdisaster.com/?p=28409</guid>

					<description><![CDATA[<p>An Air India Boeing 777 en route from Newark to Mumbai had 292 passengers and 21 crew aboard when it took off at 4:36 in the afternoon. Witnesses saw flames shooting from the left engine when flight 144 took off. Pilots reported problems with the left engine, and twenty-two minutes after taking off, returned to...</p>
<p>The post <a href="https://airflightdisaster.com/air-india-emergency-bird-strike-in-newark-nj/" data-wpel-link="internal" target="_self">Air India Emergency Bird Strike in Newark NJ</a> first appeared on <a href="https://airflightdisaster.com" data-wpel-link="internal" target="_self">George Hatcher's Air Flight Disaster</a>.</p>]]></description>
										<content:encoded><![CDATA[<p><a href="https://airflightdisaster.com/wp-content/uploads/2014/07/duck77.jpg" data-wpel-link="internal" target="_self"><img fetchpriority="high" decoding="async" src="https://airflightdisaster.com/wp-content/uploads/2014/07/duck77-300x259.jpg" alt="duck77" width="300" height="259" class="alignleft size-medium wp-image-28411" /></a>An Air India Boeing 777 en route from Newark to Mumbai had 292 passengers and 21 crew aboard when it took off at 4:36 in the afternoon.  Witnesses saw flames shooting from the left engine when flight 144 took off. </p>
<p>Pilots reported problems with the left engine, and twenty-two minutes after taking off, returned to land in Newark.  </p>
<p>The landing must have been pretty hard, because tires were blown. The airport&#8217;s New Jersey spokeswoman Erica Dumas described it as a &#8220;rough landing.&#8221;  Also, the left engine problems were attributed to a bird strike.</p>
<p>Passengers disembarked and were provided hotel accommodations while they rebooked. </p>
<p>*No ducks were injured in the photoshopping of this B777 windowseat snapshot. </p><p>The post <a href="https://airflightdisaster.com/air-india-emergency-bird-strike-in-newark-nj/" data-wpel-link="internal" target="_self">Air India Emergency Bird Strike in Newark NJ</a> first appeared on <a href="https://airflightdisaster.com" data-wpel-link="internal" target="_self">George Hatcher's Air Flight Disaster</a>.</p>]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
