Incident Overview

Description
Avianca flight AV011, a Boeing 747-200, impacted a mountain while on approach to Madrid-Barajas Airport, Spain, killing 181 occupants; 11 survived the accident. Flight AV011 took off from Paris-Charles de Gaulle (CDG) at 22:25 for a flight to Bogot (BOG) via Madrid (MAD). The Boeing 747 climbed to a cruising altitude of FL370. At 23:31 the crew contacted Madrid ACC, receiving clearance to continue to the Madrid VOR via Pamplona, Barahona, and Castej¢n. Fifteen minutes later the flight was cleared to descend to FL190. At 23:52 they were cleared down to FL90: “Avianca 011 est pasando Barahona, proceda ya directo a Charlie Papa Lima, y contin£e descenso para el nivel nueve cero, cambio.” After contacting Madrid Approach ar 23:56 they were cleared for a runway 33 approach. After reaching FL90 at 00:00 they were cleared further down. Madrid Tower at 00:03 then cleared the flight to land. Instead of turning right at the Madrid VOR, the crew initiated a turn short of the VOR beacon. The aircraft descended below the MDA for that area. The right main gear and no. 4 engine contacted a hill at an altitude of 2247 feet and a speed of 142 knots. Three seconds later the aircraft impacted a second hill at a speed of 135 knots and a 4,9deg. nose-up attitude. Six seconds after contacting the second hill, the aircraft (at 126 kts) hit the ground with the right wing, which broke off. The Boeing cartwheeled, broke in five pieces and came to rest upside down. PROBABLE CAUSE: “The pilot-in-command, without having any precise knowledge of his position, set out to intercept the ILS on an incorrect track without initiating the published instrument approach manoeuvre; in so doing he descended below all; the area safety minima until he collided with the ground. Contributory factors were: a) Inaccurate navigation by the crew, which placed them in an incorrect position for initiating the approach manoeuvre.; b) Failure of the crew to take corrective action in accordance with the operating instructions of the ground proximity warning system.; c) Deficient teamwork on the flight deck.; d) Imprecise position information supplied to the aircraft by APP.; e) The APP controller, in failing to inform the aircraft that radar service had terminated, did not maintain a proper watch on the radar scope.” (Accident Investigation Board, Spain)
Primary Cause
Inaccurate navigation by the crew, which placed them in an incorrect position for initiating the approach manoeuvre; failure of the crew to take corrective action in accordance with the operating instructions of the ground proximity warning system; defective teamwork on the flight deck; imprecise position information supplied to the aircraft by APP; and the pilot-in-command, without having any precise knowledge of his position, set out to intercept the ILS on an incorrect track without initiating the published instrument approach manoeuvre.Inaccurate navigation by the crew, which placed them in an incorrect position for initiating the approach manoeuvre; failure of the crew to take corrective action in accordance with the operating instructions of the ground proximity warning system; defective teamwork on the flight deck; imprecise position information supplied to the aircraft by APP; and the pilot-in-command, without having any precise knowledge of his position, set out to intercept the ILS on an incorrect track without initiating the published instrument approach manoeuvre.Share on: