JuliusWong 0 Report post Posted July 5, 2017 (edited) Not sure if this has been shared, came out on 28 June 2017, AirAsia X incident had 'engine-related cause': Rolls-Royce Preliminary inquiries into an AirAsia X Airbus A330 incident on 25 June have confirmed a cause relating to its Rolls-Royce Trent 700 powerplants. Rolls-Royce says it is working to "fully understand" the reason behind the failure which led the Kuala Lumpur-bound aircraft, operating flight D7237, to return to Perth. But it stresses that the AirAsia X engine was being maintained under its TotalCare pact with the long-haul budget carrier. "TotalCare is Rolls-Royces highest level of service and is available to any airline," says the manufacturer. "Rolls-Royce would like to make it clear that there is no difference in the level of service provided between airlines, including low-cost carriers." Investigators are still looking into the event involving an eight-year old A330-300 (9M-XXE) which had 359 passengers on board. Source: https://www.flightglobal.com/news/articles/airasia-x-incident-had-engine-related-cause-rolls-438869/ Edited July 5, 2017 by JuliusWong Share this post Link to post Share on other sites
Mohd Suhaimi Fariz 2 Report post Posted July 5, 2017 Not sure if this ahs been shared, came out on 28 June 2017, AirAsia X incident had 'engine-related cause': Rolls-Royce Preliminary inquiries into an AirAsia X Airbus A330 incident on 25 June have confirmed a cause relating to its Rolls-Royce Trent 700 powerplants. Rolls-Royce says it is working to "fully understand" the reason behind the failure which led the Kuala Lumpur-bound aircraft, operating flight D7237, to return to Perth. But it stresses that the AirAsia X engine was being maintained under its TotalCare pact with the long-haul budget carrier. "TotalCare is Rolls-Royces highest level of service and is available to any airline," says the manufacturer. "Rolls-Royce would like to make it clear that there is no difference in the level of service provided between airlines, including low-cost carriers." Investigators are still looking into the event involving an eight-year old A330-300 (9M-XXE) which had 359 passengers on board. Source: https://www.flightglobal.com/news/articles/airasia-x-incident-had-engine-related-cause-rolls-438869/ Tell it to the Aussies. They're having a field day bashing D7 to kingdom come over the double incidents. Share this post Link to post Share on other sites
JuliusWong 0 Report post Posted July 5, 2017 Tell it to the Aussies. They're having a field day bashing D7 to kingdom come over the double incidents.Yes indeed. Double whammy for MH and double whammy for D7. Haiz, we need lucky charm for both airlines. Peter is now in Sydney to meet up with agents to thank and shore up supports. He also hint at new destinations. Tony also hints at Adelaide and Broome. Share this post Link to post Share on other sites
Radzi 2 Report post Posted July 6, 2017 Tony also hints at Adelaide and Broome. Broome? Really? Share this post Link to post Share on other sites
Tom/PER 0 Report post Posted July 6, 2017 Broome? Really? No doubt in response to Silkair's proposed SIN-BME flights. Would think it'd have to be DPS-BME operated by QZ or XT, either way it's bound to attract plenty of publicity. Share this post Link to post Share on other sites
KK Lee 5 Report post Posted July 6, 2017 (edited) DPS-BME is more likely than KUL-BME. Edited July 6, 2017 by KK Lee Share this post Link to post Share on other sites
flee 5 Report post Posted July 11, 2017 9M-XXE has left PER - looks like it may be heading to Manila, where Lufthansa Teknik is... https://www.flightradar24.com/XAX688/e0c098c Share this post Link to post Share on other sites
Sri Ramani K. 0 Report post Posted August 23, 2017 https://www.atsb.gov.au/publications/investigation_reports/2017/aair/ao-2017-066/ Updated: 23 August 2017 The ATSB is investigating an engine malfunction involving Airbus A300, registered 9M-XXE, near Carnarvon, Western Australia, on 25 June 2017. The aircraft had earlier departed Perth, Western Australia bound for Kuala Lumpur, Malaysia. While conducting a climb from flight level (FL) 380 to FL 400, [1] a fan blade on the number 1 engine failed resulting in engine damage and significant airframe vibration. Interviews and analysis of recorded flight data, indicated that the flight crew conducted an in-flight engine shutdown and returned to Perth. The shutdown engine continued to rotate in the airflow, resulting in ongoing airframe vibration. The aircraft returned to Perth and landed safely. The engine manufacturer found that a section of the fan blade separated at about one quarter of its length from the blade base. The blade section and associated engine debris were retained within the engine cowls. Examination of the retained fan blade section identified that the separation was likely due to metal fatigue that originated within the blades internal structure. Investigation and analysis of the failure mode are on-going. The findings of the engine manufacturer will be included in the ATSBs draft safety investigation report. The draft report will be provided to relevant parties for comment before the completion and release of the final report. Share this post Link to post Share on other sites
Chris Tan 0 Report post Posted August 23, 2017 The ATSB is investigating an engine malfunction involving Airbus A300, registered 9M-XXE, near Carnarvon, Western Australia, on 25 June 2017. They got it wrong. We all know it's a Boeing 330-343LR. Share this post Link to post Share on other sites
