27.04.2015 Views

Runway excursions - SKYbrary

Runway excursions - SKYbrary

Runway excursions - SKYbrary

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Figure 24: Airbus A320 overrun accident, Congonhas Airport, Sao Paulo,<br />

Brazil, 17 July 2007<br />

Source: USA Today<br />

How did it happen?<br />

At the time of writing, the accident was being investigated by the Brazilian Centro<br />

de Investigação e Prevenção de Acidentes Aeronáuticos (CENIPA).<br />

Initial analysis of the flight data recorder and cockpit voice recorder data by the<br />

NTSB several days after the accident indicated that the flight crew were aware that<br />

the aircraft's right thrust reverser was unserviceable and not available for the<br />

landing. The cockpit voice recorder transcript also indicates that the spoilers did not<br />

activate after touchdown, delaying the deceleration of the aircraft on the runway.<br />

In the wet conditions, it is possible that the aircraft aquaplaned and hence did not<br />

stop before the end of the runway. Flight crew error may have also potentially<br />

played a role in the delayed braking of the aircraft<br />

Why did it happen?<br />

The runway conditions at the time of the accident were ‘wet and slippery’, and the<br />

wind was reported from 330 degrees at 8 kts. <strong>Runway</strong> 35L had an asphalt surface<br />

and had recently been resurfaced; however, it was not grooved at the time. The<br />

accident happened in darkness (1850 local time). <strong>Runway</strong> 35L had a published<br />

landing distance of 1,879 m at the time of the accident.<br />

At the time of the accident, the aircraft was operating with a deactivated thrust<br />

reverser on the number 2 (right) engine.<br />

(Ascend, 2007; Aviation Safety Network, 2008).<br />

- 59 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!