<?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>Airline Industry Review &#187; Qantas</title>
	<atom:link href="http://airlineindustryreview.com/tag/qantas/feed/" rel="self" type="application/rss+xml" />
	<link>http://airlineindustryreview.com</link>
	<description></description>
	<lastBuildDate>Thu, 26 Jan 2012 08:28:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Qantas, RR and Airbus &#8211; What Really Happened ?</title>
		<link>http://airlineindustryreview.com/qantas-rr-and-airbus-what-really-happened/</link>
		<comments>http://airlineindustryreview.com/qantas-rr-and-airbus-what-really-happened/#comments</comments>
		<pubDate>Sat, 06 Nov 2010 15:25:03 +0000</pubDate>
		<dc:creator>Miyuru Sandaruwan</dc:creator>
				<category><![CDATA[Airbus]]></category>
		<category><![CDATA[Boeing]]></category>
		<category><![CDATA[747]]></category>
		<category><![CDATA[A380]]></category>
		<category><![CDATA[Qantas]]></category>
		<category><![CDATA[qf32]]></category>
		<category><![CDATA[rolls royce]]></category>
		<category><![CDATA[RR]]></category>

		<guid isPermaLink="false">http://www.airlineindustryreview.com/qantas-rr-and-airbus-what-really-happened/</guid>
		<description><![CDATA[<p><p><a href="http://airlineindustryreview.com/qantas-rr-and-airbus-what-really-happened/">Qantas, RR and Airbus &#8211; What Really Happened ?</a>
</br></p><p>It all happened on one fine Thursday. On 4th November, Qantas&#8217; A380 Nancy-Bird Walton ( VH-OQA, MSN014 ) had just departed from Singapore ( IATA : SIN ) to embark the final leg of its journey from London to Sydney as QF32. Just 6 minutes into the flight &#8211; the...</p></p><p></br>
Originally posted on <a href="http://airlineindustryreview.com">Airline Industry Review</a></p>]]></description>
			<content:encoded><![CDATA[<p><a href="http://airlineindustryreview.com/qantas-rr-and-airbus-what-really-happened/">Qantas, RR and Airbus &#8211; What Really Happened ?</a>
</br></p><p>It all happened on one fine Thursday. On 4th November, Qantas&#8217; A380 Nancy-Bird Walton ( VH-OQA, MSN014 ) had just departed from Singapore ( IATA : SIN ) to embark the final leg of its journey from London to Sydney as QF32.<br />
 Just 6 minutes into the flight &#8211; the passengers were treated with a loud bang that sure must have horrified some. The #2 engine ( left wing ) had blown out causing debris, including the cowling, to fall down to the nearby Indonesian island of Batam.</p>
<p><img src="http://img714.imageshack.us/img714/6702/debris42420x0.jpg" alt="Qantas flight 32 engine debris" /> Copyrighted photo. Author unknown.</p>
<p><img src="http://img180.imageshack.us/img180/8796/qantasa388vhoqasingapor.jpg" alt="Qantas QF32 engine damage" /> Photo copyright Retuters</p>
<p> The pilots acted calm and professionally, keeping passengers calm, and safely brought the aircraft back to SIN &#8211; touching down at 1146 local. Following landing, it was found that the engine debris had harmed a wiring system, making it impossible to shut down #1 engine, requiring it to be shut down by foaming.</p>
<p> Further inspection showed that the aircraft&#8217;s left wing had suffered damage from the engine debris. This type of engine error &#8211; causing parts of engine to blow out &#8211; is what we call an uncontained engine failure.</p>
<p> Just the following day &#8211; on 5th November &#8211; a Qantas Boeing 747-400 ( VH-OJD/ cn 24481 ) suffered yet another engine issue. This time too, on the climb from SIN and onwards to Sydney &#8211; as QF6 from Frankfurt. The issue occured 20 mins into the flight. The pilots decided to turn back and made a safe return to SIN. This engine error however, was not an uncontained error, and in fact could be categorised as minor.<br />
 The interesting fact ? Earlier QF32&#8242;s pilots too were passengers in this flight.</p>
<p><b>THE AIRCRAFT</b></p>
<p>Airbus A380<br />
Type: A380-842<br />
Registration: VH-OQA<br />
Serial number: MSN014<br />
Engines: Rolls Royce Trent 900 ( 972-84 variant )<br />
First flown: 25 Jan 2008<br />
Entered Qantas revenue service on: 20 Oct 2008<br />
In service with Qantas for: 2 years, 1 month plus since 19 Sep 2008<br />
Named Nancy-Bird Walton. Qantas&#8217; first A380.</p>
<p>Boeing 747<br />
Type: 747-438<br />
Registration: VH-OJD<br />
Serial number: 24481/LN765<br />
Engines: Rolls Royce RB-211-524G<br />
First flown: 13 Dec 1989<br />
Entered Qantas revenue service on: 20 Jan 1990<br />
In service with Qantas for: 20 years 9 months plus, since 16 Jan 1990</p>
<p><b>What do we know ?</b></p>
<p>- Two Qantas aircraft, operating on the same flight leg, had engine issues on consecutive days.<br />
- Both aircraft had engines made by the British manufacturer Rolls Royce.</p>
<p><b>Worth noticing</b></p>
<p>- Although they seem identical &#8211; the two events were almost totally unrelated to each other. They involved two very different mechanical issues.<br />
- The Trent 900, and RB-211 &#8211; despite being built by the same manufacturer &#8211; are very different in their core.<br />
- The A380 and Boeing 747 both are perfectly capable of flying with three working engines. One engine going out is not going to cause it to crash.<br />
- Qantas has operated the Trent 900 for two years, whereas they have operated the RB-211 for over thirty years. This particular RB-211 engine &#8211; *believed to be* a &#8220;Trent-ified&#8221; RB-211-524G- T &#8211; is one which Qantas has operated for ten years.</p>
<p>The Trent 900 -<br />
Available exclusively for the Airbus A380 &#8211; shares some features with the rest of the Trent lineup. Is used by three airlines &#8211; Lufthansa, Qantas and Singapore Airlines.<br />
It is also worth noting that Qantas operates a high power variant of the Trent 900, which has a higher thrust rating than the ones operated by the other two operators.</p>
<p>The RB-211<br />
Perhaps Rolls&#8217; most popular engine type ever &#8211; it began it&#8217;s life with Lockheed L1011 Tristar in 1972. The RB-211 has since powered many aircraft types with different variants of the engine.<br />
 The RB-211-524 model, available for the Boeing 747-400 and Boeing 767-300, is used by a number of operators worldwide and has logged over 65 million flying hours so far.<br />
 The model carries on the three-shaft architecture that is found in many RB-211 variants. The Trent-ified RB-211-524G/H-T was upgraded with the Trent 700 technology and is designed to operate at temperatures that are far higher than the normal variant.</p>
<p><b>What Could Have Happened ?</b><br />
 As individuals with no experience of the actual incident &#8211; we have no right to speculate &#8211; as it would not be accurate. Hence we cannot exactly determine what caused the A380 incident.<br />
 But the word in the aviation circles is that, this could be related to the Trent 900&#8242;s IP disc. The Qantas engineers indeed found out today that the IP turbine disc in #2 engine had stopped working &#8211; but the exact cause was yet to be found out.<br />
 In the meantime, Qantas has decided to change two engines in two A380s in its fleet. One of these, VH-OQC, will have its #3 engine changed due to an oil leak and some other issues. Another frame, currently in Los Angeles, will have one of its engines changed due to unspecified issues. This makes it clear that Qantas&#8217; immediate grounding of the fleet has not been over silly reasons.</p>
<p>Could volcanic ash from Mt. Merapi&#8217;s eruption have caused this ? Although there is a very distant probability &#8211; this remains very unlikely. Both of these incidents took place in a short time span from departure from SIN, which will not take the aircraft anywhere near the mountain. Someone could argue that although this is true, the ash could have been spread in a far wider area &#8211; and the current flight cancellations in the area might serve as a proof -, but this becomes very unlikely given that a number of aircraft have flown between SIN and Sydney on both of these days, without any irregularities. This includes SIA A380s, as well as Qantas aircraft. The fact that Indonesian local airlines still continue to fly despite the eruption, further rules out this as a cause for the Qantas engine issues.</p>
<p> The interesting factor is that, both of these engine issues have taken place during the aircraft&#8217;s climb phase. It would be worth finding out if Qantas uses a different power setting for climb than other operators of these aircraft.</p>
<p> There is also no reason for passengers to worry about flying on either the Airbus A380 or the Boeing 747. Both of these aircraft have a very good safety record &#8211; and alternative engine choices are available for both types as well. In the A380&#8242;s case, the Emirates and Air France aircraft powered by Engine Alliance GP7000 engines are yet to to report any abnormalities while the Trent 900 powered ones flown by Lufthansa and SIA too have been flying with a flawless safety record today.</p>
<p> Perhaps the key reason why this issue was highlighted so much is the fact that both the aircraft and the engine are two relatively new types and may be in fact because the A380 is the largest as well as the newest aircraft in commercial service today.</p>
<p> Whatever the cause of the incident is, we can expect that both the manufacturers and the operators will take their best effort to fix this issue and assure it never takes place again. In the meantime, VH-OQA, Qantas&#8217; first A380, will get some much needed rest inside a hangar in Singapore.<br />
Aircraft data courtesy of AussieAirliners.org
<div class="plus-one-wrap"><g:plusone size="small" href="http://airlineindustryreview.com/qantas-rr-and-airbus-what-really-happened/"></g:plusone></div>
<p></br>
Originally posted on <a href="http://airlineindustryreview.com">Airline Industry Review</a></p>]]></content:encoded>
			<wfw:commentRss>http://airlineindustryreview.com/qantas-rr-and-airbus-what-really-happened/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How Qantas Could Have Managed QF32 Incident Better</title>
		<link>http://airlineindustryreview.com/how-qantas-could-have-managed-qf32-incident-better/</link>
		<comments>http://airlineindustryreview.com/how-qantas-could-have-managed-qf32-incident-better/#comments</comments>
		<pubDate>Sat, 06 Nov 2010 08:30:47 +0000</pubDate>
		<dc:creator>Miyuru Sandaruwan</dc:creator>
				<category><![CDATA[Airbus]]></category>
		<category><![CDATA[Incidents]]></category>
		<category><![CDATA[New Media]]></category>
		<category><![CDATA[Qantas]]></category>
		<category><![CDATA[qf32]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://www.airlineindustryreview.com/how-qantas-could-have-managed-qf32-incident-better/</guid>
		<description><![CDATA[<p><p><a href="http://airlineindustryreview.com/how-qantas-could-have-managed-qf32-incident-better/">How Qantas Could Have Managed QF32 Incident Better</a>
</br></p><p>I believe that Qantas could have handled the Qantas flight 32 incident a lot better had they used social media. The key reason is, the speed of spreading the word. The other is, it was the exact medium that many people and media used to spread news about this incident....</p></p><p></br>
Originally posted on <a href="http://airlineindustryreview.com">Airline Industry Review</a></p>]]></description>
			<content:encoded><![CDATA[<p><a href="http://airlineindustryreview.com/how-qantas-could-have-managed-qf32-incident-better/">How Qantas Could Have Managed QF32 Incident Better</a>
</br></p><p>I believe that Qantas could have handled the <a href="http://airlineindustryreview.com/tag/qf32">Qantas flight 32</a> incident a lot better had they used social media.<br />
 The key reason is, the speed of spreading the word. The other is, it was the exact medium that many people and media used to spread news about this incident.<br />
 This distributed, and still continues to distribute, a large share of false information. Had Qantas been present on social media, they could have instantly presented the accurate info leaving no space for the false information. By turning the wave into their advantage, Qantas could have avoided a PR disaster.</p>
<p> Some very interesting views on this from former SIA VP of Public Affairs, Stephen Foreshaw, <a href="http://facebook.com/notes/stephen-forshaw/some-thoughts-on-qf32-crisis-management-and-the-media/167384773288830">here</a>.<br />
 The most important line perhaps is,</p>
<blockquote><p>Fill the information vacuum before others do. Simply, if the media can’ t get you to comment, they ’ ll find someone else, and you will have no control over what that someone else says.</p></blockquote>
<p> Qantas is still not too late.
<div class="plus-one-wrap"><g:plusone size="small" href="http://airlineindustryreview.com/how-qantas-could-have-managed-qf32-incident-better/"></g:plusone></div>
<p></br>
Originally posted on <a href="http://airlineindustryreview.com">Airline Industry Review</a></p>]]></content:encoded>
			<wfw:commentRss>http://airlineindustryreview.com/how-qantas-could-have-managed-qf32-incident-better/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Qantas 747 in Engine Issue Following Singapore Departure</title>
		<link>http://airlineindustryreview.com/qantas-747-in-engine-issue-following-singapore-departure/</link>
		<comments>http://airlineindustryreview.com/qantas-747-in-engine-issue-following-singapore-departure/#comments</comments>
		<pubDate>Fri, 05 Nov 2010 16:01:35 +0000</pubDate>
		<dc:creator>Miyuru Sandaruwan</dc:creator>
				<category><![CDATA[Boeing]]></category>
		<category><![CDATA[Incidents]]></category>
		<category><![CDATA[747]]></category>
		<category><![CDATA[Qantas]]></category>
		<category><![CDATA[qf32]]></category>
		<category><![CDATA[rolls royce]]></category>
		<category><![CDATA[RR]]></category>

		<guid isPermaLink="false">http://www.airlineindustryreview.com/qantas-747-in-engine-issue-following-singapore-departure/</guid>
		<description><![CDATA[<p><p><a href="http://airlineindustryreview.com/qantas-747-in-engine-issue-following-singapore-departure/">Qantas 747 in Engine Issue Following Singapore Departure</a>
</br></p><p>A Qantas Boeing 747-400, registered VH-OJD, operating as QF6 from Singapore, SIN to Sydney had an engine malfunction and returned safely to SIN. The flight, QF6, was on its way from Frankfurt to Sydney with a scheduled stopover in Singapore with 431 passengers and crew onboard. The issue had occured...</p></p><p></br>
Originally posted on <a href="http://airlineindustryreview.com">Airline Industry Review</a></p>]]></description>
			<content:encoded><![CDATA[<p><a href="http://airlineindustryreview.com/qantas-747-in-engine-issue-following-singapore-departure/">Qantas 747 in Engine Issue Following Singapore Departure</a>
</br></p><p>A Qantas Boeing 747-400, registered VH-OJD, operating as QF6 from Singapore, SIN to Sydney had an engine malfunction and returned safely to SIN.<br />
 The flight, QF6, was on its way from Frankfurt to Sydney with a scheduled stopover in Singapore with 431 passengers and crew onboard.<br />
 The issue had occured in #1 engine and more details were not available at the time of publishing.<br />
 The aircraft, VH-OJD, a Boeing 747-438 with serial number 24481 was built in 1990. This aircraft too, was powered by a Rolls Royce engine variant as the <a href="http://airlineindustryreview.com/qantas-a380-engine-issue-over-indonesia/">recent A380 did</a>. The 747 is powered by RB211, one of Rolls&#8217; oldest and most popular engine variants whereas the A380 was powered by newer Trent 900s.
<div class="plus-one-wrap"><g:plusone size="small" href="http://airlineindustryreview.com/qantas-747-in-engine-issue-following-singapore-departure/"></g:plusone></div>
<p></br>
Originally posted on <a href="http://airlineindustryreview.com">Airline Industry Review</a></p>]]></content:encoded>
			<wfw:commentRss>http://airlineindustryreview.com/qantas-747-in-engine-issue-following-singapore-departure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Qantas Cancels Orders for 15 787s</title>
		<link>http://airlineindustryreview.com/qantas-cancels-orders-15-787s/</link>
		<comments>http://airlineindustryreview.com/qantas-cancels-orders-15-787s/#comments</comments>
		<pubDate>Fri, 26 Jun 2009 03:42:48 +0000</pubDate>
		<dc:creator>Miyuru Sandaruwan</dc:creator>
				<category><![CDATA[Boeing]]></category>
		<category><![CDATA[787]]></category>
		<category><![CDATA[Qantas]]></category>

		<guid isPermaLink="false">http://www.aeroeveryday.co.cc/boeing/qantas-cancels-orders-15-787s/</guid>
		<description><![CDATA[<p><p><a href="http://airlineindustryreview.com/qantas-cancels-orders-15-787s/">Qantas Cancels Orders for 15 787s</a>
</br></p><p>Photo by mattdocampo FlightGlobal reports that Qantas Airways has cancelled orders for 15 787-9s and deferred the deliveries of 15 787-8s in a bid to reduce capital expenditure. This is the first major cancellation for the delayed Dreamliner. Qantas was the biggest customer for the 787 and still has orders...</p></p><p></br>
Originally posted on <a href="http://airlineindustryreview.com">Airline Industry Review</a></p>]]></description>
			<content:encoded><![CDATA[<p><a href="http://airlineindustryreview.com/qantas-cancels-orders-15-787s/">Qantas Cancels Orders for 15 787s</a>
</br></p><p><img src="http://farm3.static.flickr.com/2300/2150879759_4ee6b27951.jpg" /><br />
<i>Photo by <a href="http://www.flickr.com/photos/21203547@N07/">mattdocampo</a> </i></p>
<p>FlightGlobal reports that Qantas Airways has cancelled orders for 15 787-9s and deferred the deliveries of 15 787-8s in a bid to reduce capital expenditure.<br />
 This is the first major cancellation for the delayed Dreamliner.<br />
 Qantas was the biggest customer for the 787 and still has orders for 35 787-9s and 15 787-8s. It had planned to use the first 15 787-8s for JetStar, it&#8217;s low cost subsidiary, operations which were slated to arrive from 2010. Now it plans to provide JetStar with the 787-9s which will arrive from 2013 onwards.<br />
 Qantas CEO Alan Joyce has said that the delay was not a reason for the cancellation.<br />
 Boeing stock quote went down by 0.66% at the latest change ( 7.59pm ET ) . This is the 50th post in this blog and sadly, I had to post a bad news. This news comes in a week full of bad news with the 6th delay to 787 delivery schedule and Michael Jackson&#8217;s death this morning.
<div class="plus-one-wrap"><g:plusone size="small" href="http://airlineindustryreview.com/qantas-cancels-orders-15-787s/"></g:plusone></div>
<p></br>
Originally posted on <a href="http://airlineindustryreview.com">Airline Industry Review</a></p>]]></content:encoded>
			<wfw:commentRss>http://airlineindustryreview.com/qantas-cancels-orders-15-787s/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

