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

 Actions

Special

Semantic search

  • B732, Pekanbaru Indonesia, 2002 (Synopsis: On 14 January 2002, a Boeing 737-200, operated by Lion Air, attempted to complete a daylight take off from Pekanbaru, Indonesia without flaps set after a failure to complete the before take off checks. The rejected take off was not initiated promptly and the aircraft overran the runway. The take off configuration warning failed to sound because the associated circuit breaker was so worn that it had previously auto-tripped and this had not been noticed.)
  • B732, vicinity Washington National DC USA, 1982 (Synopsis: On 13 January 1982, an Air Florida Boeing 737-200 took off in daylight from runway 36 at Washington National in moderate snow but then stalled before hitting a bridge and vehicles and continuing into the river below after just one minute of flight killing most of the occupants and some people on the ground. The accident was attributed entirely to a combination of the actions and inactions of the crew in relation to the prevailing adverse weather conditions and, crucially, to the failure to select engine anti ice on which led to over reading of actual engine thrust.)
  • B733, Tabing Padang Indonesia, 2012 (Synopsis: On 13 October 2012, the crew of a Boeing 737-300 destined for the new Padang airport at Minangkabau inadvertently landed their aircraft on runway 34 at the old Padang Airport at Tabing which has a similarly-aligned runway. The Investigation found that the Captain disregarded ILS indications for the correct approach after visually acquiring the similarly aligned runway when the correct runway was not also in sight. Since the chosen runway was some 6 miles ahead of the intended one, a high descent rate achieved through sideslip, followed with this unstable approach, continued to an otherwise uneventful landing.)
  • B733, vicinity Belfast Aldergrove UK, 2006 (Synopsis: On 18 July 2006, a Boeing 737-300 being operated by a Spanish Airline commenced a daylight non precision approach with a 12 degree offset FAT towards Belfast Aldergrove but then made an unstable descent to 200 feet agl towards an unlicensed runway at a different airport before being told by ATC radar to go around. A further also unstable approach to the correct airport/runway followed. The Investigation noted that there were multiple cues indicating that an approach to the wrong airport was being made and was not able to establish any reason why two successive unstable approaches were not discontinued)
  • B734, Lahore Pakistan, 2015 (Synopsis: On 3 November 2015, a Boeing 737-400 continued an unstabilised day approach to Lahore. When only the First Officer could see the runway at MDA, he took over from the Captain but the Captain took it back when subsequently sighting it. Finally, the First Officer took over again and landed after recognising that the aircraft was inappropriately positioned. Both main gear assemblies collapsed as the aircraft veered off the runway. The Investigation attributed the first collapse to the likely effect of excessive shimmy damper play and the second collapse to the effects of the first aggravated by leaving the runway.)
  • B734, Yogyakarta Indonesia, 2007 (Synopsis: On 7 March 2007, a Boeing 737-400 being operated by Garuda landed on a scheduled passenger flight from Jakarta to Yogyakarta overran the end of the destination runway at speed in normal daylight visibility after a late and high speed landing attempt ending up 252 metres beyond the end of the runway surface in a rice paddy field. There was a severe and prolonged fire which destroyed the aircraft (see the illustration below taken from the Investigation Report) and 21 of the 140 occupants were killed, 12 seriously injured, 100 suffered minor injuries and 7 were uninjured.)
  • B734, en-route, Daventry UK, 1995 (Synopsis: On 23 February 1995, a British Midland Boeing 737-400 made an emergency landing at Luton airport UK after losing most of the oil from both engines during initial climb out from East Midlands airport UK, attributed to failures in the quality of maintenance work and procedures during routine inspections of both engines prior to the flight.)
  • B735, vicinity Perm Russian Federation, 2008 (Synopsis: On September 13 2008, at night and in good visual conditions*, a Boeing 737-500 operated by Aeroflot-Nord executed an unstabilised approach to Runway 21 at Bolshoye Savino Airport (Perm) which subsequently resulted in loss of control and terrain impact.)
  • B737 / B737, vicinity Geneva Switzerland, 2006 (Synopsis: On 11 May 2006, B737-700 taking off from Geneva came into close proximity with a Boeing Business Jet (BBJ) on a non revenue positioning flight which had commenced a go around from the same runway following an unstabilised approach. The Investigation attributed the conflict to the decision of ATC to give take off clearance to the departing aircraft when the approach of the inbound aircraft could have been seen as highly likely to result is a go around which would lead to proximity with the slower departing aircraft.)
  • B737 en-route, Glen Innes NSW Australia, 2007 (Synopsis: On 17 November 2007 a Boeing 737-700 made an emergency descent after the air conditioning and pressurisation system failed in the climb out of Coolangatta at FL318 due to loss of all bleed air. A diversion to Brisbane followed. The Investigation found that the first bleed supply had failed at low speed on take off but that continued take off had been continued contrary to SOP. It was also found that the actions taken by the crew in response to the fault after completing the take off had also been also contrary to those prescribed.)
  • B737, Chicago Midway USA, 2005 (Synopsis: 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.)
  • B737, manoeuvring, west of Norwich UK 2009 (Synopsis: On 12 January 2009, the flight crew of an Easyjet Boeing 737-700 on an airworthiness function flight out of Southend lost control of the aircraft during a planned system test. Controlled flight was only regained after an altitude loss of over 9000 ft, during which various exceedences of the AFM Flight Envelope occurred. The subsequent investigation found that the Aircraft Operators procedures for such flights were systemically flawed.)
  • B738, Belfast International UK, 2017 (Synopsis: On 21 July 2017, a Boeing 737-800 taking off from Belfast was only airborne near the runway end of the runway and then only climbed at a very shallow angle until additional thrust was eventually added. The Investigation found that the thrust set had been based on an incorrectly input surface temperature of -52°C, the expected top of climb temperature, instead of the actual surface temperature. Although inadequate acceleration had been detected before V1, the crew did not intervene. It was noted that neither the installed FMC software nor the EFBs in use were conducive to detection of the data input error.)
  • B738, Dubai UAE, 2013 (Synopsis: On 6 December 2013, a Boeing 737-800 passenger aircraft was flown from Amman to Dubai out of revenue service with a quantity of 'live' boxed chemical oxygen generators on board as cargo without the awareness of the aircraft commander. The subsequent Investigation found that this was possible because of a wholesale failure of the aircraft operator to effectively oversee operational risk implicit in sub contracting heavy maintenance. As a result of the investigation, a previously unreported flight by the same operator in revenue service which had also carried live oxygen generators was disclosed.)
  • B738, Katowice Poland, 2007 (Synopsis: On 28 October 2007, a Boeing 737-800 under the command of a Training Captain occupying the supernumerary crew seat touched down off an ILS Cat 1 approach 870 metres short of the runway at Katowice in fog at night with the AP still engaged. The somewhat protracted investigation did not lead to a Final Report until over 10 years later. This attributed the accident to crew failure to discontinue an obviously unstable approach and it being flown with RVR below the applicable minima. The fact that the commander was not seated at the controls was noted with concern.)
  • B738, Lyon France, 2009 (Synopsis: On 29 August 2009, an Air Algérie Boeing B737-800 departed the side of the runway during take off but then regained the paved surface after sustaining damage from obstructions, completed the take off without further event and continued to destination. Damage to one of the engines, to tyres and to two lights was discovered at the destination. ATC remained unaware of the excursion until the Operator asked its representative at Lyon to ask the airport to carry out a runway inspection.)
  • B738, Manchester UK, 2003 (Synopsis: 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.)
  • B738, Mangalore India, 2010 (Synopsis: On 22 May 2010, an Air India Express Boeing 737-800 overran the landing runway at Mangalore when attempting a go around after thrust reverser deployment following a fast and late touchdown off an unstable approach. Almost all of the 166 occupants were killed when control was lost and the aircraft crashed into a ravine off the end of the runway. It was noted a relevant factor in respect of the approach, landing and failed go around attempt was probably the effect of ‘sleep inertia’ on the Captain’s performance and judgement after a prolonged sleep en-route)
  • B738, Perth Australia, 2008 (Synopsis: On 9 May 2008, a Boeing 737-800 made a low go around at Perth in good daylight visibility after not approaching with regard to the temporarily displaced runway threshold. A second approach was similarly flown and, having observed a likely landing on the closed runway section, ATC instructed a go around. However, instead, the aircraft flew level at a low height over the closed runway section before eventually touching down just beyond the displaced threshold. The Investigation found that runway closure markings required in Australia were contrary to ICAO Recommendations and not conducive to easy recognition when on final approach.)
  • B738, en-route, south west of Beirut Lebanon, 2010 (Synopsis: On 25 January 2010, a Boeing 737-800 being operated by Ethiopian Airlines on a scheduled passenger flight from Beirut to Addis Ababa in night IMC disappeared from ATC radar soon after departure from Runway 21 and was subsequently found to have impacted the sea in an unintentional out of control condition some five miles south west of the airport less than five minutes after getting airborne Impact resulted in the destruction of the aircraft and the death of all 90 occupants.)