<?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>Pilot Error &#8211; News Analysis India</title>
	<atom:link href="https://newsanalysisindia.com/tag/pilot-error/feed/" rel="self" type="application/rss+xml" />
	<link>https://newsanalysisindia.com</link>
	<description>The news you need to know, explained</description>
	<lastBuildDate>Mon, 22 Sep 2025 00:00:00 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>Supreme Court Demands Response on Air India Crash Inquiry, Criticizes Preliminary Report</title>
		<link>https://newsanalysisindia.com/india/supreme-court-demands-response-on-air-india-crash-inquiry-criticizes-preliminary-report/</link>
		
		<dc:creator><![CDATA[News Analysis India]]></dc:creator>
		<pubDate>Mon, 22 Sep 2025 00:00:00 +0000</pubDate>
				<category><![CDATA[India]]></category>
		<category><![CDATA[Ahmedabad]]></category>
		<category><![CDATA[Air India]]></category>
		<category><![CDATA[Civil Aviation]]></category>
		<category><![CDATA[DGCA]]></category>
		<category><![CDATA[Investigation]]></category>
		<category><![CDATA[Legal]]></category>
		<category><![CDATA[Pilot Error]]></category>
		<category><![CDATA[plane crash]]></category>
		<category><![CDATA[Safety]]></category>
		<category><![CDATA[Supreme Court]]></category>
		<guid isPermaLink="false">http://newsanalysisindia.local/supreme-court-demands-response-on-air-india-crash-inquiry-criticizes-preliminary-report/</guid>

					<description><![CDATA[The Supreme Court has voiced concerns regarding the selective release of the preliminary inquiry report concerning the June 2025 crash of Air India Flight AI171. The court noted that the&#8230;]]></description>
										<content:encoded><![CDATA[
<p>The Supreme Court has voiced concerns regarding the selective release of the preliminary inquiry report concerning the June 2025 crash of Air India Flight AI171. The court noted that the report&#8217;s selective leak generated a media narrative that placed blame on pilot error for the tragic event. The Union Ministry of Civil Aviation and the Directorate General of Civil Aviation (DGCA) have been directed by the top court to respond to a petition submitted by the NGO Safety Matters Foundation. The petition calls for an independent, fair, and swift investigation into the Ahmedabad Air India crash, which occurred on June 21 and resulted in 260 fatalities. Further details will be provided as the story develops.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>FIP Voices Concerns Over AI-171 Crash Investigation, Cites Pilot Exclusion</title>
		<link>https://newsanalysisindia.com/india/fip-voices-concerns-over-ai-171-crash-investigation-cites-pilot-exclusion/</link>
		
		<dc:creator><![CDATA[News Analysis India]]></dc:creator>
		<pubDate>Thu, 17 Jul 2025 00:00:00 +0000</pubDate>
				<category><![CDATA[India]]></category>
		<category><![CDATA[AAIB]]></category>
		<category><![CDATA[Ahmedabad]]></category>
		<category><![CDATA[AI-171]]></category>
		<category><![CDATA[Air India]]></category>
		<category><![CDATA[Aviation Safety]]></category>
		<category><![CDATA[Cockpit Voice Recording]]></category>
		<category><![CDATA[Crash Investigation]]></category>
		<category><![CDATA[FIP]]></category>
		<category><![CDATA[Pilot Error]]></category>
		<category><![CDATA[Pilot Investigation]]></category>
		<guid isPermaLink="false">http://newsanalysisindia.local/fip-voices-concerns-over-ai-171-crash-investigation-cites-pilot-exclusion/</guid>

					<description><![CDATA[The Federation of Indian Pilots (FIP) has expressed &#8216;serious&#8217; concerns regarding the preliminary findings and public discussion surrounding the Air India flight AI-171 crash in Ahmedabad. The FIP stated its&#8230;]]></description>
										<content:encoded><![CDATA[
<p>The Federation of Indian Pilots (FIP) has expressed &#8216;serious&#8217; concerns regarding the preliminary findings and public discussion surrounding the Air India flight AI-171 crash in Ahmedabad. The FIP stated its dissatisfaction with the exclusion of pilot representatives from the Aircraft Accident Investigation Bureau (AAIB)&#8217;s investigation process. The pilots&#8217; body objects to how the preliminary report has been interpreted and presented publicly. The FIP claims that the preliminary report lacks comprehensive data and appears to rely selectively on paraphrased cockpit voice recordings, potentially suggesting pilot error and questioning the crew&#8217;s professional competence. The federation has urged stakeholders, including the media, to refrain from disseminating partial narratives or making unfounded assumptions, emphasizing the need for a fair, transparent, and evidence-based investigation. The AAIB&#8217;s preliminary report indicates that both engines were moved to &#8216;cutoff,&#8217; cutting off the fuel supply, with one pilot allegedly denying the action in cockpit recordings. The AI 171 crash resulted in the tragic loss of 260 lives.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Dhalla: Premature to Blame Pilots in Air India Crash, &#8216;Startle Effect&#8217; Possible</title>
		<link>https://newsanalysisindia.com/india/dhalla-premature-to-blame-pilots-in-air-india-crash-startle-effect-possible/</link>
		
		<dc:creator><![CDATA[News Analysis India]]></dc:creator>
		<pubDate>Sat, 12 Jul 2025 00:00:00 +0000</pubDate>
				<category><![CDATA[India]]></category>
		<category><![CDATA[Air India]]></category>
		<category><![CDATA[Aircraft Accident]]></category>
		<category><![CDATA[Aviation Investigation]]></category>
		<category><![CDATA[Cockpit Voice Recorder (CVR)]]></category>
		<category><![CDATA[Engine Failure]]></category>
		<category><![CDATA[Flight Safety]]></category>
		<category><![CDATA[Human Factors]]></category>
		<category><![CDATA[Pilot Error]]></category>
		<category><![CDATA[Ram Air Turbine (RAT)]]></category>
		<category><![CDATA[Startle Effect]]></category>
		<guid isPermaLink="false">http://newsanalysisindia.local/dhalla-premature-to-blame-pilots-in-air-india-crash-startle-effect-possible/</guid>

					<description><![CDATA[Former DGCA Flight Operations Inspector Captain Prashant Dhalla has cautioned against prematurely attributing the Air India flight 171 crash in Ahmedabad to pilot error. Dhalla suggests the &#8216;startle effect&#8217; could&#8230;]]></description>
										<content:encoded><![CDATA[
<p>Former DGCA Flight Operations Inspector Captain Prashant Dhalla has cautioned against prematurely attributing the Air India flight 171 crash in Ahmedabad to pilot error. Dhalla suggests the &#8216;startle effect&#8217; could have played a role in the incident, particularly in light of the preliminary report&#8217;s mention of a deployed Ram Air Turbine (RAT). He theorizes that pilots, faced with potential technical issues, may have inadvertently taken actions that contributed to the crash. Dhalla emphasized the need to examine all factors, including potential electrical failures and cockpit confusion, before drawing conclusions. He also highlighted the protective mechanisms on fuel switches and the importance of the Cockpit Voice Recorder (CVR) transcript. He noted the critical time constraints faced by the pilots, operating at low altitude while dealing with the emergency and contacting Air Traffic Control (ATC).</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Dhalla: Premature to Blame Pilot Error in Air India Crash</title>
		<link>https://newsanalysisindia.com/india/dhalla-premature-to-blame-pilot-error-in-air-india-crash/</link>
		
		<dc:creator><![CDATA[News Analysis India]]></dc:creator>
		<pubDate>Sat, 12 Jul 2025 00:00:00 +0000</pubDate>
				<category><![CDATA[India]]></category>
		<category><![CDATA[AAIB Report]]></category>
		<category><![CDATA[Air India]]></category>
		<category><![CDATA[Cockpit Voice Recorder (CVR)]]></category>
		<category><![CDATA[Crash Investigation]]></category>
		<category><![CDATA[Engine Failure]]></category>
		<category><![CDATA[Flight 171]]></category>
		<category><![CDATA[Pilot Error]]></category>
		<category><![CDATA[Prashant Dhalla]]></category>
		<category><![CDATA[Ram Air Turbine (RAT)]]></category>
		<category><![CDATA[Startle Effect]]></category>
		<guid isPermaLink="false">http://newsanalysisindia.local/dhalla-premature-to-blame-pilot-error-in-air-india-crash/</guid>

					<description><![CDATA[Former DGCA Flight Operations Inspector Captain Prashant Dhalla has cautioned against prematurely attributing the Air India flight 171 crash in Ahmedabad to pilot error. Dhalla, discussing the preliminary report by&#8230;]]></description>
										<content:encoded><![CDATA[
<p>Former DGCA Flight Operations Inspector Captain Prashant Dhalla has cautioned against prematurely attributing the Air India flight 171 crash in Ahmedabad to pilot error. Dhalla, discussing the preliminary report by the Aircraft Accident Investigation Bureau (AAIB), highlighted the possibility of a &#8216;startle effect&#8217; influencing pilot actions following the reported deployment of the Ram Air Turbine (RAT). He suggested pilots might have been attempting to manage the engines in response to potential technical issues. While acknowledging the possibility of human factors, Dhalla emphasized that it is too early to definitively conclude pilot error. He also pointed out the safety features of fuel switches, designed to prevent accidental shutoff, and the need for the Cockpit Voice Recorder (CVR) transcript to be released to the public. Dhalla indicated that the pilots&#8217; actions suggested engine-related issues and stressed the critical time constraints faced by pilots in such emergencies, especially at low altitudes.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
