Emirates Flight 407

The scheduled flight departed from Melbourne as planned at 22:30 using runway 16, which was 3,657 metres (11,998 feet) long. The captain ordered the first officer to rotate 1,043 metres (3,422 ft) before the end of the runway, travelling at a speed of 270 km/h (146 kn; 168 mph).[2] As the aircraft pitched upward, it failed to leave the ground and the tail section struck and continued to scrape along the runway. The captain took over the controls and applied maximum thrust on all four engines by using the takeoff/go-around detent.[3][4][5] After exhausting the entire length of the runway, the aircraft failed to become airborne, and did not leave the ground until 148 m (486 ft) beyond the end of the runway.[2]^: 9 The captain later said, "I thought we were going to die. It was that close".[3][4]

Subsequently, the aircraft hit a strobe light at the end of the runway[2]^: 11 and continued to climb with difficulty. At 350 metres (1,148 ft) beyond the end of the runway, the landing gear hit and damaged the 1.8-metre-high (5 ft 11 in) localiser antenna array. At 500 metres (1,640 ft) beyond the end of the runway, the aircraft barely missed the 2.24-metre-tall (7 ft 4 in) airport perimeter fence.

The aircraft eventually climbed away over Port Phillip Bay. The first officer then reviewed the takeoff performance calculations in his electronic flight bag, and discovered that he had understated the aircraft's weight by 100 tonnes (262.9 tonnes instead of 362.9).[2]^: 3[3][5][6][7] This meant that an incorrect flex temp was applied, which had resulted in a lower than necessary engine thrust and consequently insufficient acceleration and airspeed.[5]

The pilots finished dumping fuel over the bay by 23:27, and they subsequently received a report of smoke in the cabin. They requested an immediate return, which air traffic control granted, and they returned to the airport at 23:36 without further incident.[5]

Despite having tailstrike protection built into the A340-500, the rear pressure bulkhead and the underlying structure were severely damaged during the take-off roll when the tail struck the runway with considerable force. The aircraft also suffered extensive damage to the bottom of the fuselage as it scraped along the runway, a large surface having been completely stripped off its external sheet.[2]^: 4–8

The aircraft was not written off, but was instead returned to Airbus by way of a low-altitude flight without pressurisation routed from Melbourne to Toulouse on 19 June via Perth, Singapore, Dubai, and Cairo with the crew flying below 12,000 feet (3,700 m).[8]

The aircraft made its first revenue flight after repairs on 1 December 2009 as flight EK424, and remained in service operating short- to medium-haul international flights out of Dubai, until it was withdrawn from service in October 2014. It was stored at Tarbes–Lourdes–Pyrénées Airport.[9][10]

After being interviewed by investigators, the two pilots of the flight returned to Dubai. The captain and the first officer were asked to resign from Emirates upon their arrival in Dubai, and both did so.[11]

The captain of Flight 407 had slept for only 6 hours during the 24 hours before the accident, while the first officer had had 8 hours of sleep in the same period.[2]^: 18[lower-alpha 1] The captain had flown a total 99 hours during the prior month, 1 hour short of the maximum 100 flying hours allowed by Emirates, while the first officer had flown 90 hours in the same period.[2]^: 13–14[3][4][12]

The accident investigation was performed by the Australian Transport Safety Bureau (ATSB). 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-kilometre (12,000-foot) runway.[2]^: ix

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.[13]

In October 2011, the ATSB released the findings of their investigation into the incident. 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.[14]

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.[14][15]

The events of the incident are documented in a season 2 episode of the TV series Aircrash Confidential, titled "Take-off".[16]

• On 22 May 2015, an Air France Boeing 777 operating cargo flight AF-6724 from Paris to Mexico City was involved in a serious incident when both captain and first officer independently entered an erroneous weight value of 243 tons rather than 343 tons into their electronic flight bags. The erroneously calculated performance data were subsequently entered into the flight management system. When the aircraft failed to lift off at the calculated speed, maximum (TOGA) power was applied and the aircraft became airborne and continued without further incident to its destination. The automatic tail-strike prevention system activated to limit the aircraft's pitch angle to avoid a tail strike.[17]
• On 15 September 2015, Qatar Airways Flight 778, a Boeing 777-300ER registered A7-BAC, struck several approach lights immediately following takeoff from Miami on its way to Doha, tearing a 46 cm (18 in) gash in the fuselage behind the rear cargo door. The flight continued on without incident for the remainder of the 13.5-hour flight duration. The pilots had mistakenly taken off from intersection T1 on runway 09, using only 2,600 m (8,500 ft) of the full 3,968 m (13,018 ft) runway length, after misreading information printed on their electronic flight bag.[18]
• On 21 July 2017, a Sunwing Boeing 737 operating Thomson Airways flight BY-1526 with 6 crew and 179 passengers on board, struck a runway approach light immediately after takeoff from Belfast at the start of its flight to Corfu. The pilots had entered an incorrect outside air temperature into the aircraft's flight management computer, which caused it to use a lower thrust setting than required (81% N₁, instead of 93%).[19]

• Pan Am Flight 845
• Air Florida Flight 90

Australian Transport Safety Bureau Aviation Occurrence Investigation AO-2009-012 "Tailstrike and runway overrun - Airbus A340-541, A6-ERG, Melbourne Airport, Victoria, 20 March 2009"

• "Summary". Retrieved 9 September 2016.
• "Preliminary Report" (PDF). 30 April 2009. Retrieved 9 September 2016.
• "Interim Factual Report" (PDF). 18 December 2009. Retrieved 9 September 2016.
• "Final Report" (PDF). 16 December 2011. Retrieved 9 September 2016.

Other external links

• Accident / Serious Incident Report for Emirates Flight 407 on SKYbrary categorised under Runway Excursion / Human Factors
• "Emirates near-miss Photo Gallery, ATSB Transport Safety Report into the March 20 tail strike at Melbourne Airport". Herald Sun. 30 April 2009. Archived from the original on 30 December 2012. Retrieved 26 January 2011.