data entry error | George Hatcher's Air Flight Disaster https://airflightdisaster.com Aviation News, Headlines & Alerts Fri, 01 May 2009 12:10:50 +0000 en-US hourly 1 https://wordpress.org/?v=7.0 Preliminary Conclusion of Melbourne-March 20 Tail strike https://airflightdisaster.com/preliminary-conclusion-of-melbourne-march-20-tail-strike/ Fri, 01 May 2009 12:09:17 +0000 http://airflightdisaster.com/?p=3629 What: Airbus A340 en route for Dubai Where: Melbourne airport When: March 20 Who: 257 passengers and 18 crew Why: Incorrect weight data on an in-flight computer caused the tail of an Emirates plane to scrape the runway during take-off. ( The Australia’s air safety regulator concluded that the weight was incorrectly entered on the...

The post Preliminary Conclusion of Melbourne-March 20 Tail strike first appeared on George Hatcher's Air Flight Disaster.

]]> What: Airbus A340 en route for Dubai
Where: Melbourne airport
When: March 20
Who: 257 passengers and 18 crew
Why: Incorrect weight data on an in-flight computer caused the tail of an Emirates plane to scrape the runway during take-off. ( The Australia’s air safety regulator concluded that the weight was incorrectly entered on the onboard computer which resulted in thrust setting and take-off reference speeds lower than those required for the aircraft?s actual weight. (The weight entered was 112 tons too light.) The incident caused substantial damage to the plane’s tail. The tail ripped out at least one runway light, and dislodged a flight data recorder at the plane’s rear. Manual correction of thrust caused the rear fuselage to scrape the tarmac. The Emirates investigation is considering a flight computer double-entry system “to protect against single data source entry error.”

The post Preliminary Conclusion of Melbourne-March 20 Tail strike first appeared on George Hatcher's Air Flight Disaster.

]]>