If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user
B763, Addis Ababa Ethiopia, 2014
From SKYbrary Wiki
|On 12 October 2014, a Boeing 767-300 commenced take-off at Addis Ababa in accordance with its clearance but rejected take-off at 135 knots when the crew saw an obstruction ahead in the centre of the runway and it stopped approximately 100 metres from a vehicle. The Investigation found that the GND controller had cleared the vehicle to enter the runway, the TWR controller had given take-off clearance without first checking that that the runway was clear. It could not be established whether the GND controller had obtained TWR controller permission to grant the vehicle runway access.|
|Actual or Potential
|Human Factors, Runway Incursion|
|Flight Conditions||On Ground - Normal Visibility|
|Type of Flight||Public Transport (Passenger)|
|Intended Destination||Julius Nyerere International Airport|
|Take off Commenced||Yes|
|Flight Phase||Take Off|
|Location - Airport|
|Tag(s)||Inadequate ATC Procedures,|
Inadequate Airport Procedures
|Tag(s)||ATC clearance error,|
Procedural non compliance
Incursion pre Take off,
Visual Response to Conflict
|Damage or injury||Yes|
|Causal Factor Group(s)|
|Group(s)||Air Traffic Management,|
|Group(s)||Air Traffic Management,|
On 12 October 2014, a Boeing 767-300 (ET-AMG) being operated by Ethiopian Airlines on a scheduled international passenger flight from Addis Ababa to Dar es Salaam as ET805 was approaching V1 for a normal visibility daylight take-off when the crew saw an obstruction ahead in the middle of the runway and immediately rejected the take-off, stopping about 100 metres before reaching a white vehicle. The aircraft taxied clear of the runway but then had to be towed in because of blown tyres due to the high energy rejected take-off.
An Investigation was carried out by the Ethiopian CAA Accident Investigation Bureau. It was noted that at the time of the conflict, aerodrome ATC was being provided by two controllers, one on GND frequency and one on the TWR frequency and that the 3,800 metre-long 45 metre wide principal runway 07R/25L was in use in the 07R direction. There was no ATC Supervisor present in the Tower as it was a Sunday and "supervisor coverage was not available during weekends". It was noted that whilst the TWR controller must give explicit permission for any vehicle or other access to the active runway, such an approval would normally be given by GND and there was no requirement for the person granted such access to communicate with the TWR or listen out on that frequency.
The 48 year-old Captain, who had been PF for the occurrence flight had accumulated 8,800 hours total flying experience of which 4,400 hours were on type. The 31 year-old First Officer had 3,029 hours total flying experience of which 958 hours were on type. The 27 year old TWR controller and the 28 year old GND controller both had 4½ years’ experience as controllers after each working for 6 years as an Assistant. A third on-duty controller was on a rest break and not present in the visual control room at the time of the investigated event.
It was established that after a departing aircraft had reported "flocks of birds" on the parallel taxiway, the GND controller had decided that after an initial inspection of the taxiway where bird activity had been observed and reported, a bird scaring run of the full length of the runway was required. The GND controller, after reportedly obtaining the necessary permission of the TWR controller during an un-recorded direct exchange, issued the driver of the tasked vehicle with clearance to enter the runway at 23L threshold and proceed along its full length before exiting at the opposite (07R threshold) end. Less than a minute after this, the GND controller issued the 767, which was taxiing as previously instructed to the full-length holding point of runway 07R, with its departure clearance and instructed the crew to call TWR on reaching its taxi clearance limit at the holding point, which they did.
Without scanning the runway, the TWR controller issued take-off clearance to the 767 and following that, it was stated by the crew that after the First Officer had checked that the approach was clear prior to entry and the Captain had checked that the runway ahead was clear once lined up, the take-off was commenced. As the aircraft approached V1 (138 KIAS), the Captain detected an object ahead on the runway centreline and, after a take-off roll of about 1,750 metres to abeam the taxiway 'C' access to the runway (see the diagram below), immediately commenced a rejected take-off from a speed of approximately 135 KIAS. The aircraft was brought to stop abeam the taxiway 'D' access to the runway an estimated 100 metres from the object, which by then was identifiable as a white truck which had been driving towards them - the bird scaring vehicle. It was then taxied clear of the runway and stopped on the parallel taxiway to await a tow back to the gate because of 4 deflated tyres resulting from high brake temperatures caused by the high-energy rejected take off.
Since both the bird scaring vehicle and the 767 were in possession of valid runway access and use clearances, albeit conflicting ones, the circumstances in which this had come about were examined. It was noted that:
- the GND controller subsequently claimed that he had received direct verbal approval from the TWR controller to allow the bird scaring vehicle onto the runway whereas the TWR controller stated that the GND controller "might or might not" have informed him of the issue of a clearance to the bird scaring vehicle to enter the active runway. It was noted that although the two controller positions were in proximity to each other and oral communications between the controllers at these positions "had been the usual practice for years", an intercom was installed and any use of it would be routinely recorded as with all other ATC communications.
- the 767 take-off clearance was given prior to the aircraft entering the runway and as a result, a rolling take-off was commenced which meant that "the crew did not have time to visualise the aerodrome and were unable to build up a picture of the situation on the taxiways and the runway".
- ATC procedures mandated a visual check by the controller that the runway was clear of obstructions "in the take-off area" before issuing a take-off clearance but this had not been done.
- The extent of the view along runway 07R from its beginning was limited by the initial (upward-sloping) longitudinal profile of the pavement.
The Investigation determined that the Probable Cause of the occurrence was "human error in that Tower controller inadvertently cleared ETH805 for take-off before he had cleared the airport service vehicle from runway and he didn’t check the runway before he issued the take-off clearance".
Two Contributory Factors were also identified as follows:
- The Ground controller provided inadequate support to the Tower controller.
- There was concentrated bird movement around and near the aerodrome.
Five Safety Recommendations were made:
- that Addis Ababa ATS should have a refresher/recurrent training program for controllers.
- that Addis Ababa ATS should provide human factors training for their operational personnel.
- that Addis Ababa ATS should make the presence of a Supervisor mandatory at all times.
- that Addis Ababa Airport should improve bird and wild life hazard management to prevent bird strikes by aircraft.
- that Addis Ababa Airport should require the drivers of vehicles which are permitted to enter an active RWY for any purpose to listen out on the TWR radio frequency (118.1) in order to be aware of any aircraft movement on the runway.
The Final Report was published in the English language at an unknown date following the completion of the Investigation.