If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user

Accident and Serious Incident Reports: RE

From SKYbrary Wiki
Article Information
Category: Runway Excursion Runway Excursion
Content source: SKYbrary About SKYbrary


Reports relating to accidents which include Runway Excursion as an outcome.

The reports are organised according to the sub-categories Overrun on Take Off, Overrun on Landing, and Veer Off

Overrun on Take Off

Overrun on Take Off.jpg

  • B742, Brussels Belgium, 2008 (On 25 May 2008 a Kalitta Air B747-200F, which was departing Brussels on a cargo flight to Bahrain, overran Runway 20 at Brussels Airport, Belgium during a rejected take-off. The aircraft came to a stop 300m beyond the end of runway 20 and broke into three parts. The crew of four and one passenger safely evacuated from the aircraft and suffered only minor injuries.)
  • DC86, Manston UK, 2010 (On 11 August 2010, a Douglas DC8-63F being operated by Afghanistan-based operator Kam Air on a non scheduled cargo flight from Manston UK to Sal, Cape Verde Islands failed to get airborne until after the end of departure runway 28 during a daylight take off in normal visibility. The aircraft eventually became airborne and climbed away normally and when ATC advised of the tail strike, the aircraft commander elected to continue the flight as planned and this was achieved without further event. Minor damage to the aircraft was found after flight and there was also damage to an approach light for the reciprocal runway direction.)
  • B703, Sydney Australia, 1969 (On 1 December 1969, a Boeing 707-320 being operated by Pan Am and making a daylight take off from Sydney, Australia ran into a flock of gulls just after V1 and prior to rotation and after a compressor stall and observed partial loss of thrust on engine 2 (only), the aircraft commander elected to reject the take off. Despite rapid action to initiate maximum braking and the achievement of full reverse thrust on all engines including No 2, this resulted in an overrun of the end of the runway by 170m and substantial aircraft damage. A full emergency evacuation was carried out with no injuries to any of the occupants. There was no fire.)
  • DHC6, Jomson Nepal, 2013 (On 16 May 2013, a DHC6-300 on a domestic passenger flight made a tailwind touchdown at excessive speed in the opposite direction of the of 740 metre-long runway to the notified direction in use and, after departing the runway to one side during deceleration, re-entered the runway and attempted to take off. This failed and the aircraft breached the perimeter fence and fell into a river. The Investigation identified inappropriate actions of the aircraft commander in respect of both the initial landing and his response to the subsequent runway excursion and also cited the absence of effective CRM.)
  • AT43, Madang Papua New Guinea, 2013 (On 19 October 2013, the Captain of an ATR42 on a cargo flight taking off from Madang was unable to rotate the aircraft for take off and was forced to reject the take off from above V1. It was not possible to stop on the runway and the aircraft ended up semi submerged in a shallow creek beyond the airfield perimeter. The Investigation has established that the aircraft had not been loaded as instructed and as stated on the load and trim sheet, in particular in respect of the distribution of the load. The Investigation is continuing.)

Overrun on Landing

Overrun on Landing.jpg

  • B738, Kingston Jamaica, 2009 (On 22 December 2009, the flight crew of an American Airlines’ Boeing 737-800 made a long landing at Kingston at night in heavy rain and with a significant tailwind component and their aircraft overran the end of the runway at speed and was destroyed beyond repair. There was no post-crash fire and no fatalities, but serious injuries were sustained by 14 of the 154 occupants. The accident was attributed almost entirely to various actions and inactions of the crew. Damage to the aircraft after the overrun was exacerbated by the absence of a RESA.)
  • C56X, Port Harcourt Nigeria, 2013 (On 14 July 2011, the crew of a Cessna Citation intentionally continued a night ILS approach at Port Harcourt below the applicable DA without having any visual reference with the runway and a crash landing and lateral runway excursion which severely damaged the aircraft followed. The Investigation did not establish any reason for the violation of minima but noted the complications which had arisen in respect of CRM because of two-Captain flight crew. Absence of two-way radio communications between the fire trucks and both ATC and the AFS Watch Room was noted to have delayed discovery of the crashed aircraft.)
  • B739, Yogyakarta Indonesia, 2015 (On 6 November 2015, a Boeing 737-900 overran the 2,200 metre-long landing runway at Yogyakarta after a tailwind approach with airspeed significantly above the applicable Vref followed by a long landing on a wet runway without optimum use of deceleration devices. The flight crew management of the situation once the aircraft had come to a stop was contrary to procedures in a number of important respects. The aircraft operator took extensive action to improve crew performance following the event. The Investigation found significant fault with the airport operator's awareness of runway surface condition and an absence of related significant risk management.)
  • B737, Chicago Midway USA, 2005 (On 8 December 2005, a delay in deploying the thrust reversers after a Boeing 737-700 touchdown at night on the slippery surface of the 1176 metre-long runway at Chicago Midway with a significant tailwind component led to it running off the end, subsequently departing the airport perimeter and hitting a car before coming to a stop. The Investigation concluded that pilots’ lack of familiarity with the autobrake system on the new 737 variant had distracted them from promptly deploying the reversers and that inadequate pilot training provision and the ATC failure to provide adequate braking action information had contributed.)
  • E170, Cleveland OH USA, 2007 (On 18 February 2007, while landing at Cleveland Hopkins International Airport, USA, an Embraer ERJ170 overran the snow contaminated runway. The crew failed to execute a go-around at the minimum decision altitude (MDA) of the localizer approach when adequate visual reference was not available.)

Veer Off

Directional Control.jpg

  • B734, Barcelona Spain, 2004 (On 28 November 2004, a KLM B737-400 departed laterally from the runway on landing at Barcelona due to the effects on the nosewheel steering of a bird strike which had occured as the aircraft took off from Amsterdam.)
  • SF34, Lappeenranta Finland, 2008 (On 31 January 2008 a Saab 340B being operated by Czech airline Job Air on a scheduled passenger service from Helsinki to Lappeenranta under a wet lease contract for a Company called ‘Fly Lappeenranta’ which was not an aircraft operator. During the night landing at Lappeenranta, it departed the left side of the runway after touch down in normal visibility with snow falling. Propeller damage was caused when an attempt was then made to return the aircraft to the runway after the excursion. None of the 16 occupants was injured.)
  • GLF4, Le Castellet France, 2012 (On 13 July 2012, a Gulfstream G-IV left the side of the runway at high speed during the landing roll at Le Castellet following a positioning flight after ineffective deceleration after the flight crew had forgotten to arm the ground spoilers. The Investigation found that pilot response to this situation had been followed by a loss of directional control, collision with obstructions and rapid onset of an intense fire. Contributory factors identified included poor procedural compliance by the pilots, their lack of training on a relevant new QRH procedure which Gulfstream had ineffectively communicated and ineffective FAA oversight of the operation.)
  • B752, Mumbai India, 2010 (On 9 June 2010, a Boeing B757-200 being operated by Chennai-based Blue Dart Aviation on a scheduled cargo flight from Mumbai to Bangalore lined up and commenced a night take off in normal ground visibility aligned with the right hand runway edge lights of 45 metre wide runway 27. ATC were not advised of the error and corrective action and once airborne, the aircraft completed the intended flight without further event. A ground engineer at Bangalore then discovered damage to the right hand landing gear assembly including one of the brake units. After being alerted, the Mumbai Airport Authorities discovered a number of broken runway edge lights.)
  • A30B, Bratislava Slovakia, 2012 (On 16 November 2012, an Air Contractors Airbus A300 departed the left the side of the landing runway at Bratislava after an abnormal response to directional control inputs. Investigation found that incorrect and undetected re-assembly of the nose gear torque links had led to the excursion and that absence of clear instructions in maintenance manuals, since rectified, had facilitated this. It was also considered that the absence of any regulation requiring equipment in the vicinity of the runway to be designed to minimise potential damage to aircraft departing the paved surface had contributed to the damage caused by the accident.)

Related Articles

For all accident reports held on SKYbrary, see the main section on Accident Reports.