ASN Wikibase Occurrence # 184331
This record has been locked for editing.
| Date: | Thursday 7 January 2016 |
| Time: | 14:46 UTC |
| Type: |  Boeing 737-76J (WL) |
| Owner/operator: | Germania |
| Registration: | D-ABLB |
| MSN: | 36115/2692 |
| Year of manufacture: | 2008 |
| Fatalities: | Fatalities: 0 / Occupants: 140 |
| Aircraft damage: | None |
| Category: | Incident |
| Location: | Las Palmas-Airport de Gran Canaria (LPA/GCLP) -
 Spain
|
| Phase: | Take off |
| Nature: | Passenger - Scheduled |
| Departure airport: | Las Palmas-Airport de Gran Canaria (LPA/GCLP) |
| Friedrichshafen Airport (FDH/EDNY) | |
| Investigating agency: | CIAIAC |
| Confidence Rating: |  Accident investigation report completed and information captured |
Germania flight ST6129 was involved in a takeoff incident at Las Palmas-Airport de Gran Canaria in the Canary Islands, Spain.
The aircraft was authorized by the Tower controller in the local position (LCL) to cross runway 03L and align and wait on 03R. The aircraft crew reported that the red lights on the stop bar were illuminated on taxiway S4. The LCL controller re-authorized the aircraft to line up and wait on the runway and then take off.
At that time a work was being carried out on track 03R/21 L and a vehicle was present just off the right side of the runway. Because of that, once the GMI6129 aircraft had started the takeoff run from runway 03R, the LCL controller instructed it to cancel take-off. Maximum speed reached was about 60 knots. The aircraft passed the vehicle and the takeoff was safely aborted.
The incident was caused by a loss of situational awareness of the controller, who instructed the crew of GMI6129 to enter and then take off from runway 03R, even though he knew it was closed.
Contributing factors:
- The controller did not detect the error even though the visual aids in the tower indicated that the runway was closed. He neither visually detected the presence of the car near runway 03R, although possibly contributing was the fact that the car did not have active anti collision lights.
- The controller partially heard a communication from the crew that indicated that the stop bar was active, however he did not request a repeat of the communication and instructed the aircraft to enter the runway and lign up.
- The crew crossed an illuminted stop bar, without having information that there were ongoing contingency measures for not being able to shut it down. Regulations regarding stop bars and the manuals deriving from it are not clear and specific.
- The aircraft crew started the take-off run despite having visual contact with the car that was standing to the side of the runway.
- The mitigating measure of placing cones on the threshold of the closed runway was not implemented, since the minutes of the meeting of the Local Runway Safety Committee where it was proposed were not approved.
At the time of the incident the following Notam was in force:
B9738/15 NOTAMN Q) GCCC/QMRLC/IV/NBO/A /000/999/2756N01523W005 A) GCLP B) 1601070800 C) 1601071820 EST E) RWY 03R/21L CLSD EXC EMERG MIL CREATED: 30 Dec 2015 13:58:00 SOURCE: EUECYIYN
Accident investigation:
 |
|
Sources:
CIAIAC
History of this aircraft
Other occurrences involving this aircraft
| 12 September 2011 | D-ABLB | Air Berlin | 0 | Berlin-Tegel Airport (TXL) |  |
sub |
| 28 March 2018 | D-ABLB | Germania | 0 | Tel Aviv-Ben Gurion International Airport (TLV) |  |
sub |
| 15 October 2021 | SU-TMM | FlyEgypt | 0 | Cluj-Napoca International Airport (CLJ/LRCL) |  |
min |
| Tire failure | ||||||
Images:
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 09-Feb-2016 18:43 | harro | Added |
| 27-Nov-2016 20:54 | harro | Updated [Time, Narrative] |
| 28-Nov-2016 11:29 | harro | Updated [Photo, ] |
| 28-Nov-2016 11:32 | harro | Updated [Source] |
| 05-Nov-2017 20:12 | harro | Updated [Location] |
| 28-Nov-2021 20:06 | harro | Updated [Source] |
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