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
Content control: EUROCONTROL EUROCONTROL

Definition

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

  • 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.)
  • 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.)
  • B773, Auckland Airport New Zealand, 2007 (On 22 March 2007, an Emirates Boeing 777-300ER, started its take-off on runway 05 Right at Auckland International Airport bound for Sydney. The pilots misunderstood that the runway length had been reduced during a period of runway works and started their take-off with less engine thrust and flap than were required. During the take-off they saw work vehicles in the distance on the runway and, realising something was amiss, immediately applied full engine thrust and got airborne within the available runway length and cleared the work vehicles by about 28 metres.)
  • B738, Manchester UK, 2003 (On 16 July 2003, a Boeing 737-800, being operated by Excel Airlines on a passenger flight from Manchester to Kos began take off on Runway 06L without the flight crew being aware of work in progress at far end of the runway. The take off calculations, based on the full runway length resulted in the aircraft passing within 56 ft of a 14 ft high vehicle just after take off.)
  • B737, Southend UK, 2010 (On 21 Nov 2010, a Boeing 737-700 being operated by Arik Air on a non revenue positioning flight from Southend to Lagos with only the two pilots on board carried out a successful take off in daylight and normal ground visibility from runway 06 but became airborne only just before the end of the runway.)

Overrun on Landing

Overrun on Landing.jpg

  • B733, Yogyakarta Indonesia, 2011 (On 20 December 2011, the experienced Captain of a Sriwijaya Air Boeing 737-300 flew an unstabilised non-precision approach to a touchdown at Yogyakarta at excessive speed whilst accompanied by a very inexperienced First Officer. The aircraft overran the end of the 2200 metre-long wet runway by 75 metres . During the approach, the Captain 'noticed' several GPWS PULL UP Warnings but no action was taken. The Investigation attributed the accident entirely to the actions of the flight crew and found that there had been no alert calls from the First Officer in respect of the way the approach was flown.)
  • E190, Kupang Indonesia, 2015 (On 21 December 2015, an Embraer 195 crew continued a significantly unstable approach which included prolonged repetition of 'High Speed' and a series of EGPWS Alerts which were both ignored and which culminated in a high speed late touchdown which ended in a 200 metre overrun. The Investigation attributed the event to poor flight management and noted the systemic lack of any effective oversight of pilot operating standards compounded in the investigated event by the effects of a steep flight deck authority gradient and the failure to detect anomalies in the normal operating behaviour of both the pilots involved.)
  • B752, Girona Spain, 1999 (On 14th September 1999, a Britannia Airways Boeing 757 crash landed and departed the runway after a continued unstabilised approach in bad weather to Girona airport, Spain.)
  • A343, Toronto Canada, 2005 (On 2 August 2005, an Air France Airbus A340 attempted a daylight landing at destination on a rain-soaked runway during an active thunderstorm and overran for 300 metres ending up in a ravine from where, despite its destruction by fire, all occupants escaped. The Investigation recommendations focussed mainly on crew decision making in adverse weather conditions and issues related to the consequences of such an overrun on survivability.)
  • BN2P, Montserrat (British Overseas Territory), 2011 (On 22 May 2011 a Britten-Norman BN2A Islander being operated by Bermudian domiciled carrier Montserrat AW on a scheduled passenger flight from Antigua to Montserrat was considered at risk of an overrun after visual positioning to a day landing on runway 28 at destination in normal ground visibility. The pilot intentionally steered the aircraft off one side of the runway to decrease the degree of potential hazard and the aircraft came to a stop beside the runway and 46 metres from its end without injuries to any of the 8 occupants or damage to the aircraft.)

Veer Off

Directional Control.jpg

  • F28, Saint John NB Canada, 2002 (On 27 March 2002, a Fokker F28 being operated by Air Canada Regional Airlines (t/a Air Canada Jazz) on a scheduled night passenger flight from Toronto to Saint John, having made an uneventful procedural ILS approach to Runway 05 at destination, departed the slippery landing runway to the left shortly after touchdown in normal visibility conditions but regained it before coming to a stop. Aircraft damage was limited to minor cuts in the tyres of the right main and nose landing gear and damage to one runway edge light. There were no injuries to any of the occupants.)
  • B733, Birmingham UK, 2012 (On 21 September 2012, an Aurela Boeing 737-300 lost directional control and left the paved surface when attempting to turn off the landing runway at Birmingham expeditiously to avoid the following aircraft having to go around. The Investigation noted that the range of the approaching aircraft - still 2.5nm as the incident aircraft began to clear the runway - had not been communicated and concluded that the speed of the aircraft had been inappropriate for the prevailing wet surface conditions as well as unnecessary to prevent a go around by the following aircraft.)
  • E145, Stuttgart Germany, 2009 (On 5 January 2009, a Flybe Embraer 145 made a late touchdown with slight snow falling on a runway pre-notified as affected by slush deposits and failed to stop until it had overrun into the RESA where it finally stopped on a heading 25º off the runway alignment. The Investigation concluded that although the airport operator process for determining braking action was flawed and two Safety Recommendations were made in that respect, the overrun of the 3045metres LDA was attributable to flight crew action and that operator guidance was deficient.)
  • A306, Stockholm Sweden, 2010 (On 16 January 2010, an Iran Air Airbus A300-600 veered off the left side of the runway after a left engine failure at low speed whilst taking off at Stockholm. The directional control difficulty was attributed partly to the lack of differential braking but also disclosed wider issues about directional control following sudden asymmetry at low speeds. The Investigation concluded that deficiencies in the type certification process had contributed to the loss of directional control. It was concluded that the engine malfunction was due to the initiation of an engine stall by damage caused by debris from a deficient repair.)
  • DH8C, Kimberley South Africa, 2010 (On 16 July 2010, a South African Express Airways Bombardier DHC 8-300 hit an animal during a night landing at Kimberley after a passenger flight from Johannesburg. The nose landing gear took a direct hit and collapsed but after a temporary loss of directional control, the runway centreline was regained and the aircraft brought to a stop. The Investigation found wildlife access to the aerodrome was commonplace and the attempts at control inadequate.)


Related Articles

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