ASN Wikibase Occurrence # 72581
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Wednesday 10 February 2010 |
| Time: | 20:36 |
| Type: |  Boeing 737-306 |
| Owner/operator: | KLM Royal Dutch Airlines |
| Registration: | PH-BDP |
| MSN: | 24404/1681 |
| Year of manufacture: | 1989 |
| Fatalities: | Fatalities: 0 / Occupants: 100 |
| Aircraft damage: | None |
| Category: | Serious incident |
| Location: | Amsterdam-Schiphol International Airport (AMS/EHAM) -
 Netherlands
|
| Phase: | Take off |
| Nature: | Passenger - Scheduled |
| Departure airport: | Amsterdam-Schiphol International Airport (AMS/EHAM) |
| Frederick Chopin International (WAW/EPWA ) | |
| Investigating agency: | Dutch Safety Board |
| Confidence Rating: |  Accident investigation report completed and information captured |
On February 10, 2010 KLM flight KL1369 was cleared for takeoff on runway 36C at Amsterdam-Schiphol International Airport (AMS/EHAM). Instead, the crew took off from the parallel taxiway B.
At the time of the incident, about 20:30, it was dark and it was snowing. The airplane had just been de-iced and was instructed to taxy down taxiway Alpha towards runway 36C. This meant that the crew had to use taxiway Alpha in the opposite direction, contrary to published procedures. Air traffic control is allowed to use this taxiway in the opposite direction if deemed necessary. This is sometimes the case when an aircraft leaves the Juliet platform after de-icing, just like KL1369.
The crew were very familiar with the airport and did not use a taxiway map although they were supposed one. The air traffic controller then offered the flight to enter the runway through intersection W-8. At that time a preceding Boeing 747 had taxied the wrong way and was blocking the taxiway. The KLM flight crew accepted the offer because this also meant an opportunity for an expedited takeoff.
At that point the crew started losing positional awareness. The workload increased because the an entry in the FMS now had to be changed because the crew had anticipated using intersection W-9. Meanwhile the captain was distracted by radio communications between the air traffic controller and the pilot of the Boeing 747. The crew had to cross parallel taxiway Bravo to enter runway 36C. However, they turned directly onto Bravo and initiated their takeoff roll. The crew did not notice their error and continued their takeoff, passing within about 300 metres of a Boeing 737-400.
It appears that the taxiway leading from taxiway Bravo to runway 36C was covered with a thin layer of snow, possibly obscuring the taxiway lights. Also, visibility of the lights of runway 36C was degraded because the lighting pattern matched that of the lights along the highway parallel to the runway.
Accident investigation:
 |
|
Sources:
https://www.onderzoeksraad.nl:443/index.php/onderzoeken/opgestegen-vanaf-taxibaan-2010011/
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 11-Feb-2010 13:04 | harro | Added |
| 12-Feb-2010 01:47 | harro | Updated [Narrative] |
| 12-Feb-2010 05:37 | jpiddink | Updated [Time, Registration, Cn, Destination airport, Source, Narrative] |
| 12-Feb-2010 14:36 | RobertMB | Updated [Time, Aircraft type, Destination airport, Source, Narrative] |
| 18-Jul-2010 10:42 | harro | Updated [Source] |
| 21-Dec-2011 13:41 | harro | Updated [Total fatalities, Source, Narrative] |
| 08-Jun-2022 23:41 | Ron Averes | Updated [Operator, Narrative] |
| 14-Jun-2022 02:54 | Ron Averes | Updated [Location] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation