Initial AAIB Report On BA 777 Accident Released | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

Airborne Unlimited -- Most Recent Daily Episodes

Episode Date

Airborne-Monday

Airborne-Tuesday

Airborne-Wednesday Airborne-Thursday

Airborne-Friday

Airborne On YouTube

Airborne-Unlimited-04.29.24

Airborne-NextGen-04.30.24

Airborne-Unlimited-05.01.24 Airborne-AffordableFlyers--05.02.24

Airborne-Unlimited-05.03.24

Mon, Jan 21, 2008

Initial AAIB Report On BA 777 Accident Released

Says Engines Did Not Respond To Throttle-Up Commands

Below is the unedited, initial textual report on the January 17 accident involving a British Airways Boeing 777-200. As ANN reported, the aircraft, inbound from Beijing, touched down short of the runway at London's Heathrow Airport, skidding to a violent stop that, fortunately, only resulted in some minor injuries to those onboard.

Early theories regarding potential reasons why the Rolls-Royce Trent-powered airliner apparently lost power on approach were varied, with some obviously more credible than others.

In their initial report released Sunday, officials with the UK Air Accidents Investigation Branch AAIB) confirm the plane's engines failed to respond to throttle inputs from the cockpit -- first from the plane's autopilot, then manual inputs from the plane's flight crew.

What caused that potentially catastrophic scenario, however, has not yet been determined -- Ed.  

Following an uneventful flight from Beijing, China, the aircraft was established on an ILS approach to Runway 27L at London Heathrow. Initially the approach progressed normally, with the Autopilot and Autothrottle engaged, until the aircraft was at a height of approximately 600 ft and 2 miles from touch down. The aircraft then descended rapidly and struck the ground, some 1,000 ft short of the paved runway surface, just inside the airfield boundary fence. The aircraft stopped on the very beginning of the paved surface of Runway 27L. During the short ground roll the right main landing gear separated from the wing and the left main landing gear was pushed up through the wing root. A significant amount of fuel leaked from the aircraft but there was no fire. An emergency evacuation via the slides was supervised by the cabin crew and all occupants left the aircraft, some receiving minor injuries.

The AAIB was notified of the accident within a few minutes and a team of Inspectors including engineers, pilots and a flight recorder specialist deployed to Heathrow. In accordance with the established international arrangements the National Transportation Safety Board (NTSB) of the USA, representing the State of Design and Manufacture of the aircraft, was informed of the event. The NTSB appointed an Accredited Representative to lead a team from the USA made up of investigators from the NTSB, the FAA and Boeing. A Boeing investigator already in the UK joined the investigation on the evening of the event, the remainder of the team arrived in the UK on Friday 18th January. Rolls-Royce, the engine manufacturer is also supporting the investigation, an investigator having joined the AAIB team.

Activity at the accident scene was coordinated with the Airport Fire and Rescue Service, the Police, the British Airports Authority and British Airways to ensure the recovery of all relevant evidence, to facilitate the removal of the aircraft and the reinstatement of airport operations.

The flight crew were interviewed on the evening of the event by an AAIB Operations Inspector and the Flight Data Recorder (FDR), Cockpit Voice Recorder (CVR) and Quick Access Recorder (QAR) were removed for replay. The CVR and FDR have been successfully downloaded at the AAIB laboratories at Farnborough and both records cover the critical final stages of the flight. The QAR was downloaded with the assistance of British Airways and the equipment manufacturer. All of the downloaded information is now the subject of detailed analysis.

Examination of the aircraft systems and engines is ongoing.

Initial indications from the interviews and Flight Recorder analyses show the flight and approach to have progressed normally until the aircraft was established on late finals for Runway 27L. At approximately 600 ft and 2 miles from touch down, the Autothrottle demanded an increase in thrust from the two engines but the engines did not respond. Following further demands for increased thrust from the Autothrottle, and subsequently the flight crew moving the throttle levers, the engines similarly failed to respond. The aircraft speed reduced and the aircraft descended onto the grass short of the paved runway surface.

The investigation is now focussed on more detailed analysis of the Flight Recorder information, collecting further recorded information from various system modules and examining the range of aircraft systems that could influence engine operation.

FMI: www.aaib.dft.gov.uk, www.ba.com

Advertisement

More News

ANN's Daily Aero-Linx (05.02.24)

Aero Linx: Model Aeronautical Association of Australia MAAA clubs are about fun flying, camaraderie and community. For over 75 years, the MAAA has been Australia’s largest fl>[...]

ANN's Daily Aero-Term (05.02.24): Touchdown Zone Lighting

Touchdown Zone Lighting Two rows of transverse light bars located symmetrically about the runway centerline normally at 100 foot intervals. The basic system extends 3,000 feet alon>[...]

Aero-News: Quote of the Day (05.02.24)

“Discovery and innovation are central to our mission at Virgin Galactic. We’re excited to build on our successful record of facilitating scientific experiments in subor>[...]

ANN FAQ: Contributing To Aero-TV

How To Get A Story On Aero-TV News/Feature Programming How do I submit a story idea or lead to Aero-TV? If you would like to submit a story idea or lead, please contact Jim Campbel>[...]

NTSB Final Report: Cirrus Design Corp SR20

Student Pilot Reported That During Rotation, “All Of A Sudden The Back Of The Plane Kicked To The Right..." Analysis: The student pilot reported that during rotation, “>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

© 2007 - 2024 Web Development & Design by Pauli Systems, LC