Emirates Flight 407
Airbus A340-541 · Tailstrike on takeoff and runway overrun due to pilot error
From Auckland International Airport (AKL) to Dubai International Airport (DXB)
Event
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- Event fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- 275
- Survivors
- 275
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
Airbus A340-541
- Flight
- EK407
- Aircraft type
- Airbus A340
- Category
- Airplane · from aircraft type
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- A6-ERG
- Operator
- Emirates
- Onboard fatalities
- 0
- Route
- From Auckland International Airport (AKL)To Dubai International Airport (DXB)
Cause areas
- Personnel issues › Task performance
From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.
Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.
From the Wikipedia article
Emirates Flight 407 was a scheduled international passenger flight operated by Emirates from Auckland to Dubai with a stopover in Melbourne, operated by an Airbus A340 aircraft. On 20 March 2009, the aircraft failed to take off properly at Melbourne Airport, hitting several structures at the end of the runway before climbing and then returning to the airport for a safe landing. Although no fatalities or injuries resulted, damage to the aircraft was severe enough for the event to be classified by Australian Transport Safety Bureau as an "accident". It was subsequently determined that a data-entry error resulted in insufficient engine thrust during take off. It has been described "as close as we have ever come to a major aviation catastrophe in Australia" by aviation officials.
Investigation and cause
Investigation
The Australian Transport Safety Bureau (ATSB) performed the accident investigation. Central to the investigation was how the first officer had come to use the wrong aircraft weight, why that mistake was not picked up before takeoff, and why the flight crew had not realized the acceleration was much slower than expected until nearly entirely exhausting the 3.6 km runway.
Studies showed that aircrew could have difficulty recognising that incorrect data had been entered in avionic equipment, resulting in poor take-off performance. The ATSB issued a safety recommendation to the United States Federal Aviation Administration and a safety advisory notice to the International Air Transport Association and the Flight Safety Foundation. In addition, Airbus investigated the development of software to help pilots recognise unusual or poor performance on take-off.
In October 2011, the ATSB released their findings. They found that human error was the cause, and urged the development of technological aids that would alert pilots to incorrect data entry or insufficient take-off speed.
In response to the incident, Emirates reviewed its preflight procedures, mandating the duplication of laptop computers used for preflight planning so as to ensure dual data entry. They are also developing an avionics system for take-off acceleration-monitoring and alerting. Airbus updated its software to detect erroneous data. In October 2011, they announced plans to include a software program to calculate the required runway length. Furthermore, Airbus is developing a monitoring system to compute required acceleration rates and apply a "reasonableness test" to data input and alert the pilot to any potential errors.
Text from the Wikipedia article “Emirates Flight 407” (revision 1373882328, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
Sources
Wikipedia article: Emirates Flight 407
- Article
- Emirates Flight 407
- Revision
- 1373882328 · 2026-09-08 · retrieved 2026-09-18
- Wikidata
- Q4118137
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
Where each value comes from
- Record
- Wikipedia article "Emirates Flight 407" (page 22383845, revision 1373882328)
- Date
- Wikipedia infobox: date
- Place and country
- Wikipedia infobox: site
- Map position
- Wikipedia article coordinates
- Aircraft, operator and route
- Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- airline flight number in the infobox
- Fatalities
- Wikipedia infobox: aircraft fatalities
- Ground fatalities
- not stated in the Wikipedia infobox
- Summary
- Wikipedia infobox: summary
Source notes (1)
- Wikipedia · Facts from the Wikipedia article's infobox and coordinates, not checked against an investigation report. Independent review pending.