Loganair Flight 670A

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Loganair Flight 670A
Loganair Short 360-100 Watt-1.jpg
Sister ship of accident aircraft
Accident summary
Date 27 February 2001
Summary Double engine failure; ditching[1]
Site Firth of Forth, Scotland
Passengers 0
Crew 2
Fatalities 2 (all)
Survivors 0
Aircraft type Short 360-100
Operator Loganair
Registration G-BNMT
Flight origin Edinburgh Airport
Destination Belfast International Airport

Loganair Flight 670A (LC670A) was a scheduled cargo flight for the Royal Mail from Edinburgh-Turnhouse Airport, Scotland to Belfast International Airport. On 27 February 2001 the Short 360 operating the flight ditched in the Forth estuary off Edinburgh at around 17:30 local time; the two crewmembers' bodies were found in the wreckage a few hours after the crash.[2]

Aircraft and crew

The accident aircraft was a Short 360-100 turboprop airliner manufactured by Short Brothers Limited in 1987, constructor's serial number SH 3723 and registered G-BMNT.[3] It was powered by two Pratt & Whitney Canada PT6A-67R engines.[3] Its passenger seats had been removed for use as a freighter and its Certificate of Airworthiness was valid until 15 October 2001.[3][4] The aircraft was loaded with 1,360 kg (3,000 lb) of fuel and carried 1,040 kilograms (2,293 lb) of cargo with a total weight at takeoff of 10,149 kilograms (22,375 lb). Maximum certified takeoff weight of the Short 360 is 12,292 kg (27,100 lb).[5]

The crew consisted of a 58-year-old male holding a valid Airline Transport Pilot's licence and with 13,569 hours' flying experience, as the pilot in command.[6] The co-pilot was a 29-year-old male, also with a valid licence and 438 total flight hours.[7][8]

Accident

At 17:10 local time the first officer requested clearance and, after a short delay, the crew taxied to depart from runway 06. With the pilot flying, a normal takeoff was followed by a normal reduction in power at 1,200 feet amsl. At 2,200 feet the co-pilot selected the anti-icing systems on while the pilot changed to a new radio frequency. Four seconds later the torque indicators for both engines rapidly fell to zero and the aircraft suffered a complete loss of propeller thrust. As the first officer radioed a Mayday call on the Air traffic control frequency, the pilot initiated a descent with a reduced airspeed of 110 kt while turning right towards the coast. Realizing they couldn't reach shore the crew prepared for ditching. At an airspeed of 86 kt with a 6.8 degree nose up and 3.6 degree left wing down attitude the aircraft impacted the water heading 109 degrees magnetic.[9]

Aftermath

The aircraft was found 65 metres off shore in a 45 degree nose down attitude, with the forward half of the fuselage submerged in a water depth of approximately 6 metres. The flight deck was almost completely destroyed and the fuselage was firmly embedded in the sand. The empennage had separated and was found floating 100 metres to the east of the main wreckage. Both crew seats remained attached to the flight deck floor with no failure of the safety harnesses. The cockpit voice recorder (CVR) and flight data recorder (FDR) were both recovered intact. The Short 360 was eventually salvaged with some difficulty, and was dismantled before it was transported to Air Accidents Investigation Branch (AAIB) headquarters at Farnborough for a detailed examination.[10]

Cause

Upon investigation, it was concluded that the crash had been caused primarily by the lack of an established practical procedure for flight crews to install engine air intake covers in adverse weather conditions.

The aircraft landed at Edinburgh Airport, Scotland, at midnight in snow conditions and was then parked heading directly into moderate to strong surface winds for approximately 17 hours. Because no protecting plugs were put inside the engine intakes, the wind drove a significant amount of snow into the intakes. The intake plugs were not carried as part of the aircraft's onboard equipment and they were not readily available at Edinburgh Airport. Information concerning freezing weather conditions in the aircraft manufacturer's maintenance manual had not been including in the airline's Short 360 Operations Manual and was therefore not complied with. The AAIB discovered that large volumes of snow or slush could have accumulated where it would not have been readily visible to the crew during a pre-flight inspection (the engine intakes on a Short 360 are about 2.8 m (9 ft) above the ground[11]). On takeoff this snow changed the engine intake air flow, causing both engines to flame out after both engines' anti-ice vanes were simultaneously opened as per the standard operating procedure. It was noted by the investigators that selecting engine anti-ice 'on' sequentially with a time interval between would have prevented a simultaneous dual engine flameout.[12]

Similar occurrence

During the course of the investigation the AAIB was made aware of a similar incident eight years before the loss of G-BNMT. A Short 360 operated by a different airline suffered a dual engine power loss while on its takeoff run. The source of the problem was found to be the accumulation of ice and snow during operation in sub-zero temperatures.[13]

Recommendations

As a result of this incident several recommendations were released by the AAIB and the aircraft manufacturer suggesting changes to current operations of Short 360 aircraft in near-zero or sub-zero temperature conditions, including:

  • Flight Operation Department Communication 17/2001 published on Oct. 20, 2001 by the AAIB.
  • All Operator Message SD002/02 released by Short Brothers on March 4, 2002.
  • Recommendations 2002-39, 2002–40 and 2002–41 based on findings of the investigation, issued by the AAIB.[14]

References

  1. ↑ Accident description for Short SD3-60 registration G-BNMT at the Aviation Safety Network. Retrieved on 3 May 2015.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ 3.0 3.1 3.2 Accident report, page 8; accessed 6 May 2015
  4. ↑ Accident report, page 9; accessed 13 May 2015
  5. ↑ Accident Prevention, page 4; accessed 10 May 2015
  6. ↑ Accident report, page 6; accessed 6 May 2015
  7. ↑ Accident report, page 7; accessed 6 May 2015
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Accident report, page 27; accessed 9 May 2015
  11. ↑ Accident report, Appendix III, Figure 4, accessed 13 May 2015
  12. ↑ Appendices to Aircraft Accident Report, page 50; accessed 9 May 2015
  13. ↑ Appendices to Aircraft Accident Report, page 32; accessed 9 May 2015
  14. ↑ Accident Prevention, page 7; accessed 10 May 2015
Retrieved from "https://infogalactic.com/w/index.php?title=Loganair_Flight_670A&oldid=723105812"