Crash of an Airbus A400M in Seville: 4 killed

Date & Time: May 9, 2015 at 1257 LT
Type of aircraft:
Operator:
Registration:
EC-403
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Seville - Seville
MSN:
023
YOM:
2015
Flight number:
Casa423
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Aircraft flight hours:
0
Aircraft flight cycles:
0
Circumstances:
Brand new, the aircraft just came out from the manufacturer in Seville and was engaged in its first post assembly test flight. After take off from Seville-San Pablo Airport Runway 09 at 1254LT, the crew completed a 90° turn to the left bound to the north. Shortly later, three of the four engines (engines n°1, 2 and 3) got stuck at high power. The crew attempted to control the power setting to the normal mode but those three engines failed to respond. The crew reduced the engine power after selecting the thrust levers to idle. The regime of those three engines remained blocked in idle so the crew decided to return to the airport for an emergency landing. On approach, the aircraft collided with power lines, stalled and crashed in an open field located 1,6 km north of the airport, bursting into flames. Two crew members were rescued while four others were killed. The aircraft was totally destroyed by a post crash fire. The aircraft was following a test program prior to its delivery to the Turkish Air Force (Türk Hava Kuvvetleri).
Probable cause:
An Airbus official after the accident stated that engine control software was incorrectly installed during final assembly of the aircraft. This led to engine failure and the resulting crash.

Crash of a Beechcraft 200 Super King Air in Maracaibo

Date & Time: Apr 25, 2015 at 1710 LT
Registration:
YV2803
Survivors:
Yes
Schedule:
Caracas – Maracaibo
MSN:
BB-506
YOM:
1979
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
For unknown reason, the twin engine aircraft landed hard. Impact caused the tail to separate. The aircraft lost its undercarriage then slid for few dozen metres before coming to rest, bursting into flames. All five occupants evacuated safely and the aircraft was destroyed. It seems the aircraft suffered an engine failure shortly before landing.

Crash of an Airbus A320-232 in Istanbul

Date & Time: Apr 25, 2015 at 1041 LT
Type of aircraft:
Operator:
Registration:
TC-JPE
Survivors:
Yes
Schedule:
Milan – Istanbul
MSN:
2941
YOM:
2006
Flight number:
TK1878
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
91
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Milan-Malpensa Airport at 0700LT and proceeded to the east. Following an uneventful flight, the crew initiated the approach to Istanbul-Atatürk Airport Runway 05. At a height of 100 feet above the runway, the aircraft banked to the right, stalled and struck the runway surface. On impact, the right main gear was severely damaged and punctured the right wing. In such condition, the captain decided to abandon the landing manoeuvre and initiated a go-around procedure. The aircraft climbed to an assigned altitude of 3,800 feet then the crew declared an emergency and confirmed that the right engine was out of service. Few minutes later, the right engine caught fire. The crew followed a 20-minutes holding circuit over the bay of Marmara before a second approach to runway 35L. After touchdown, the right main gear collapsed, the aircraft slid for few dozen metres then veered off runway to the right, completed a 180 turn before coming to rest in a grassy area. All 97 occupants evacuated safely while the aircraft was damaged beyond repair. According to the operator, the loss of control during the last segment was caused by turbulences from a preceding Boeing 787 that landed on the same runway 05.

Crash of a Pilatus PC-12/45 in Ciudad Acuña

Date & Time: Apr 24, 2015 at 1245 LT
Type of aircraft:
Registration:
XA-BLU
Flight Type:
Survivors:
Yes
MSN:
481
YOM:
2003
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
3508
Circumstances:
Following an uneventful flight, the pilot initiated a VFR approach to Ciudad Acuña-El Bonito Airport runway 28 in good weather conditions with 9 km visibility and an OAT of +30° C. On short final, the pilot failed to realize his altitude was too low when the aircraft impacted ground five metres short of runway. The aircraft bounced, rolled for few dozen metres then veered off runway to the left and came to rest in a wooded area. All six occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The accident occurred after the pilot suffered a loss of situational awareness while completing a visual approach below the glide, causing the aircraft to struck the ground five metres short of runway 28 threshold.
The following contributing factors were identified:
- Overconfidence on part of the pilot,
- Unstabilized approach,
- Lack of visual aids.
Final Report:

Crash of an Airbus A320-232 in Hiroshima

Date & Time: Apr 14, 2015 at 2005 LT
Type of aircraft:
Operator:
Registration:
HL7762
Survivors:
Yes
Schedule:
Seoul – Hiroshima
MSN:
3244
YOM:
2007
Flight number:
OZ162
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
74
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8242
Captain / Total hours on type:
1318.00
Copilot / Total flying hours:
1588
Copilot / Total hours on type:
1298
Aircraft flight hours:
23595
Circumstances:
The approach to Hiroshima Airport was completed in marginal weather conditions. The autopilot was disengaged at 2,100 feet MSL when the aircraft descended below the glide path and hit approach lights and the localiser antenna located 325 meters short of runway 28. The aircraft continued the descent, hit the soft ground short of runway. Then it rolled on runway for some 1,154 meters, veered to the left, went off runway and came to rest 130 meters to the left of the concrete runway, some 1,477 meters past the runway threshold. All 82 occupants were evacuated, among them 27 (25 passengers and 2 crew members) were injured. The aircraft was considered as written off due to severe damages on both engines, ailerons, wings and the bottom of the fuselage. At the time of the accident, weather conditions were difficult with visibility up to 4 km, RVR on runway 28 variable from 300 to 1,800 meters, light rain, partial fog, one octa cloud at 0 feet, 4 octas at 500 feet, 6 octas at 1,200 feet.
Probable cause:
It is certain that when landing on RWY 28 at the Airport, the Aircraft undershot and the PIC commenced executing a go-around; however, it collided with the Aeronautical Radio Navigation Aids located in front of RWY 28 threshold, just before turning to climb. Regarding the fact that the Aircraft undershot, it is probable that there might be following aspects in causes: The PIC continued approaching without executing a go around while the position of the Aircraft could not be identified by visual references which should have been in view and identified continuously at or below the approach height threshold (Decision Altitude: DA); and as well, the FO, as pilot-monitoring who should have monitored meteorological conditions and flight operations, did not make a call-out of go-around immediately when he could not see the runway at DA. Regarding the fact that the PIC continued approaching without executing a go around while the position of the Aircraft could not be identified by visual references which should have been in view and identified continuously at or below DA, he did not comply with the regulations and SOP, and it is probable that there was a background factor that the education and trainings for compliance of rules in the Company was insufficient. In addition, regarding the fact that the FO did not make an assertion of go around, it is probable that the CRM did not function appropriately.
Final Report:

Crash of a Piper PA-31T Cheyenne I in Fort Lauderdale: 4 killed

Date & Time: Apr 12, 2015 at 1625 LT
Type of aircraft:
Operator:
Registration:
N119RL
Flight Type:
Survivors:
No
Schedule:
Orlando - Fort Lauderdale
MSN:
31T-7904002
YOM:
1979
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
1221
Aircraft flight hours:
3267
Circumstances:
Following an uneventful personal flight, the pilot contacted the air traffic control tower controller and was immediately cleared to land. About 36 seconds later, the pilot reported "smoke in the cockpit." When asked to repeat, the pilot repeated "smoke in the cockpit." The tower controller cleared the pilot to land on any runway. About 47 seconds after the initial call of smoke, the pilot reported "mayday mayday mayday mayday mayday (unintelligible)." The airplane then crashed about ¼ mile short of the airport in a wooded area and burned. Security video showed the airplane pitch nose-down suddenly just before impact. The video revealed no visible smoke or fire trailing the airplane before ground impact. The pilot reported about 1,221 hours of total flight time on his Federal Aviation Administration first class medical certificate, issued about two months prior to the accident. He completed an initial training course for the airplane make and model 1 week before the accident. The airplane had recently undergone an annual inspection and extensive upgrades to its avionics. Both the left and right engines displayed contact signatures to their internal components characteristic of engines developing significant power at the time of impact, likely in the mid-to-high power range. The engines displayed no indications of any pre-impact anomalies or distress that would have precluded normal engine operation. Both propeller assemblies broke free from the engine during the crash sequence and the blades on both engines revealed signatures consistent with the development of power at impact. The center fuselage and cockpit areas were completely consumed in the postcrash fire. An examination of all remaining wires, wire bundles, switches, terminals, circuit breakers, electrical components, instruments, and avionics did not reveal evidence of precrash thermal distress. However, a small fire just before impact likely would not have had time to create thermal damage that would be discernable after an extensive postcrash fire.
Probable cause:
A rapid onset of smoke and/or fire inflight for reasons that could not be determined due to the postimpact fire and the condition of the wreckage.
Final Report:

Crash of a Cessna 414A Chancellor in Bloomington: 7 killed

Date & Time: Apr 7, 2015 at 0006 LT
Type of aircraft:
Registration:
N789UP
Flight Type:
Survivors:
No
Schedule:
Indianapolis - Bloomington
MSN:
414A-0495
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
7
Captain / Total flying hours:
12100
Captain / Total hours on type:
1150.00
Aircraft flight hours:
8390
Circumstances:
The twin-engine airplane, flown by an airline transport pilot, was approaching the destination airport after a cross-country flight in night instrument meteorological conditions. The destination airport weather conditions about 1 minute before the accident included an overcast ceiling at 200 ft and 1/2-mile visibility with light rain and fog. According to air traffic control (ATC) data, the flight received radar vectors to the final approach course for an instrument landing system (ILS) approach to runway 20. As shown by a post accident simulation study based on radar data and data recovered from the airplane's electronic horizontal situation indicator (EHSI), the airplane's flight path did not properly intercept and track either the localizer or the glideslope during the instrument approach. The airplane crossed the final approach fix about 360 ft below the glideslope and then maintained a descent profile below the glideslope until it leveled briefly near the minimum descent altitude, likely for a localizer-only instrument approach. However, the lateral flight path from the final approach fix inbound was one or more dots to the right of the localizer centerline until the airplane was about 1 nautical mile from the runway 20 threshold when it turned 90° left to an east course. The turn was initiated before the airplane had reached the missed approach point; additionally, the left turn was not in accordance with the published missed approach instructions, which specified a climb on runway heading before making a right turn to a 270° magnetic heading. The airplane made a series of pitch excursions as it flew away from the localizer. The simulation study determined that dual engine power was required to match the recorded flight trajectory and ground speeds, which indicated that both engines were operating throughout the approach. The simulation results also indicated that, based on calculated angle of attack and lift coefficient data, the airplane likely encountered an aerodynamic stall during its course deviation to the east. The airplane impacted the ground about 2.2 miles east-northeast of the runway 20 threshold and about 1.75 miles east of the localizer centerline. According to FAA documentation, at the time of the accident, all components of the airport's ILS were functional, with no recorded errors, and the localizer was radiating a front-course to the correct runway. Additionally, a post accident flight check found no anomalies with the instrument approach.An onsite examination established that the airplane impacted the ground upright and in a nose-low attitude, and the lack of an appreciable debris path was consistent with an aerodynamic stall/spin. Wreckage examinations did not reveal any anomalies with the airplane's flight control systems, engines, or propellers. The glideslope antenna was found disconnected from its associated cable circuit. Laboratory examination and testing determined that the glideslope antenna cable was likely inadequately connected/secured during the flight, which resulted in an unusable glideslope signal to the cockpit avionics. There was no history of recent maintenance on the glideslope antenna, and the reason for the inadequate connection could not be determined. Data downloaded from the airplane's EHSI established that the device was in the ILS mode during the instrument approach phase and that it had achieved a valid localizer state on both navigation channels; however, the device never achieved a valid glideslope state on either channel during the flight. Further, a replay of the recorded EHSI data confirmed that, during the approach, the device displayed a large "X" through the glideslope scale and did not display a deviation pointer, both of which were indications of an invalid glideslope state. There was no evidence of cumulative sleep loss, acute sleep loss, or medical conditions that indicated poor sleep quality for the pilot. However, the accident occurred more than 2 hours after the pilot routinely went to sleep, which suggests that the pilot's circadian system would not have been promoting alertness during the flight. Further, at the time of the accident, the pilot likely had been awake for 18 hours. Thus, the time at which the accident occurred and the extended hours of continuous wakefulness likely led to the development of fatigue. The presence of low cloud ceilings and the lack of glideslope guidance would have been stresses to the pilot during a critical phase of flight. This would have increased the pilot's workload and situational stress as he flew the localizer approach, a procedure that he likely did not anticipate or plan to conduct. In addition, weight and balance calculations indicated that the airplane's center of gravity (CG) was aft of the allowable limit, and the series of pitch excursions that began shortly after the airplane turned left and flew away from the localizer suggests that the pilot had difficulty controlling airplane pitch. This difficulty was likely due to the adverse handling characteristics associated with the aft CG. These adverse handling characteristics would have further increased the pilot's workload and provided another distraction from maintaining control of the airplane. Therefore, it is likely that the higher workload caused by the pilot's attempt to fly an unanticipated localizer approach at night in low ceilings and his difficulty maintaining pitch control of the airplane with an aft CG contributed to his degraded task performance in the minutes preceding the accident.
Probable cause:
The pilot's failure to maintain control of the airplane during the instrument approach in night instrument meteorological conditions, which resulted in the airplane exceeding its critical angle of attack and an aerodynamic stall/spin. Contributing to the accident were pilot fatigue, the pilot's increased workload during the instrument approach resulting from the lack of glide slope guidance due to an inadequately connected/secured glide slope antenna cable, and the airplane being loaded aft of its balance limit.
Final Report:

Crash of an Antonov AN-74-200 at Barneo Ice Camp

Date & Time: Apr 3, 2015
Type of aircraft:
Registration:
RA-74056
Survivors:
Yes
Schedule:
Longyearbyen – Barneo
MSN:
470 98 951
YOM:
1995
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
4883
Aircraft flight cycles:
1690
Circumstances:
The approach to the Barneo Ice Station was completed in poor weather conditions. In low visibility, the aircraft landed hard with an acceleration of 2,4 g. This caused the right main gear to partially collapse and the aircraft came to rest in a nose up attitude on the icy runway. All 17 occupants evacuated safely and despite the fact the aircraft was slightly damaged, it was decided to abandon the aircraft that would not be repaired. An insurance claim was submitted 24APR2015 and the engines were removed. The aircraft drifted with the ice floe to the west then floe cracked between 26 and 27JUL2015, causing the aircraft to sank in the Arctic Ocean.
Probable cause:
Hard landing after the crew deployed the interceptors too early on approach.

Crash of an Airbus A320-211 in Halifax

Date & Time: Mar 29, 2015 at 0030 LT
Type of aircraft:
Operator:
Registration:
C-FTJP
Survivors:
Yes
Schedule:
Toronto – Halifax
MSN:
233
YOM:
1991
Flight number:
AC624
Country:
Crew on board:
5
Crew fatalities:
Pax on board:
133
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11765
Captain / Total hours on type:
5755.00
Copilot / Total flying hours:
11300
Copilot / Total hours on type:
6392
Aircraft flight hours:
75103
Circumstances:
On 29 March 2015, an Air Canada Airbus Industrie A320-211 (registration C-FTJP, serial number 233), operating as Air Canada flight 624, was on a scheduled flight from Toronto/Lester B. Pearson International Airport, Ontario, to Halifax/Stanfield International Airport, Nova Scotia, with 133 passengers and 5 crew members on board. At approximately 0030 Atlantic Daylight Time, while conducting a non-precision approach to Runway 05, the aircraft severed power lines, then struck the snow-covered ground about 740 feet before the runway threshold. The aircraft continued airborne through the localizer antenna array, then struck the ground twice more before sliding along the runway. It came to rest on the left side of the runway, about 1900 feet beyond the threshold. The aircraft was evacuated; 25 people sustained injuries and were taken to local hospitals. The aircraft was destroyed. There was no post-impact fire. The emergency locator transmitter was not activated. The accident occurred during the hours of darkness.
Probable cause:
Findings as to causes and contributing factors:

1. Air Canada’s standard operating procedure (SOP) and practice when flying in flight path angle guidance mode was that, once the aircraft was past the final approach fix, the flight crews were not required to monitor the aircraft’s altitude and distance from the threshold or to make any adjustments to the flight path angle. This practice was not in accordance with the flight crew operating manuals of Air Canada or Airbus.
2. As per Air Canada’s practice, once the flight path angle was selected and the aircraft began to descend, the flight crew did not monitor the altitude and distance from the threshold, nor did they make any adjustments to the flight path angle.
3. The flight crew did not notice that the aircraft had drifted below and diverged from the planned vertical descent angle flight profile, nor were they aware that the aircraft had crossed the minimum descent altitude further back from the threshold.
4. Considering the challenging conditions to acquire and maintain the visual cues, it is likely the flight crew delayed disconnecting the autopilot until beyond the minimum descent altitude because of their reliance on the autopilot system.
5. The approach and runway lights were not changed from setting 4 to setting 5; therefore, these lights were not at their maximum brightness setting during the approach.
6. The system to control the airfield lighting’s preset selections for brightness setting 4 was not in accordance with the NAV CANADA Air Traffic Control Manual of Operations requirement for the omnidirectional approach lighting system to be at its brightest settings.
7. The limited number of visual cues and the short time that they were available to the flight crew, combined with potential visual illusions and the reduced brightness of the approach and runway lights, diminished the flight crew’s ability to detect that the aircraft’s approach path was taking it short of the runway.
8. The flight crew’s recognition that the aircraft was too low during the approach would have been delayed because of plan continuation bias.
9. The aircraft struck terrain approximately 740 feet short of the runway threshold, bounced twice, and then slid along the runway before coming to a rest approximately 1900 feet beyond the runway threshold.
10. At some time during the impact sequence, the captain’s head struck the glare shield because there were insufficient acceleration forces to lock the shoulder harness and prevent movement of his upper body.
11. The first officer sustained a head injury and serious injury to the right eye as a result of striking the glare shield because the automatic locking feature of the right-side shoulder-harness inertia reel was unserviceable.
12. A flight attendant was injured by a coffee brewer that came free of its mounting base because its locking system was not correctly engaged.
13. Because no emergency was expected, the passengers and cabin crew were not in a brace position at the time of the initial impact.
14. Most of the injuries sustained by the passengers were consistent with not adopting a brace position.

Findings as to risk:

1. If aircraft cockpit voice recorder installations do not have an independent power supply, additional, potentially valuable information will not be available for an investigation.
2. If Transport Canada does not consistently follow its protocol for the assessment of aeromedical risk and ongoing surveillance in applicants who suffer from obstructive sleep apnea, some of the safety benefit of medical examinations will be lost, increasing the risk that pilots will fly with a medical condition that poses a risk to safety.
3. If new regulations on the use of child-restraint systems are not implemented, lap-held infants and young children are exposed to undue risk and are not provided with a level of safety equivalent to that for adult passengers.
4. If passengers do not dress appropriately for safe travel, they risk being unprepared for adverse weather conditions during an emergency evacuation.
5. If the type of approach lighting system on a runway is not factored into the minimum visibility required to carry out an approach, in conditions of reduced visibility, the lighting available risks being less than adequate for flight crews to assess the aircraft’s position and decide whether or not to continue the approach to a safe landing.
6. If they do not incorporate a means of absorbing forces along their longitudinal axis, vertically mounted, non-structural beams (channels, tubes, etc.) in cargo compartments could penetrate the cabin floor when the fuselage strikes the water or ground, increasing the risk of aircraft occupants being injured or emergency egress being impaired.
7. If an aircraft manufacturer’s maintenance instructions do not include the component manufacturer’s safety-critical test criteria, the component risks not being maintained in an airworthy condition.
8. If there is a complete loss of electrical and battery power and the passenger address system does not have an independent emergency power supply, the passenger address system will be inoperable, and the initial command to evacuate or to convey other emergency instructions may be delayed, putting the safety of passengers and crew at risk.
9. If passengers retrieve or attempt to retrieve their carry-on baggage during an evacuation, they are putting themselves and other passengers at a greater risk of injury or death.
10. If passengers do not pay attention to the pre-departure safety briefings or review the safety-features cards, they may be unprepared to react appropriately in an accident, increasing their risk of injury or death.
11. If an organization’s emergency response plan does not identify all available transportation resources, there is an increased risk that evacuated passengers and crew will not be moved from an accident site in a timely manner.
12. If organizations do not practise transporting persons from an on-airport accident site, they may be insufficiently prepared to react appropriately to an actual accident, which may increase the time required to evacuate the passengers and crew.

Other findings:

1. The service director assessed the evacuation flow as good and determined that there was therefore no need to open the R1 door.
2. The flight attendants stationed in the rear of the aircraft noted no life-threatening hazards. Because no evacuation order had been given, and deplaned passengers and firefighters were observed walking near the rear of the aircraft in an area where the deployment of the rear slides may have created additional hazards or risks, the flight attendants determined that there was no requirement to open the L2 and R2 doors.
3. Although Transport Canada required the dual-exit drill to be implemented in training, it did not require all cabin crew to receive the training before an organization implemented the 1:50 ratio.
4. At the time of the accident, neither the service director nor the flight attendants had received the dual-exit training, nor were they aware of the requirement for such training in order for Air Canada to operate with the exemption allowing 1 flight attendant for each unit of 50 passengers.
5. Although Transport Canada had reviewed and approved Air Canada’s aircraft operating manual and the standard operating procedures (SOPs), it had not identified the discrepancy between the Air Canada SOPs and the Airbus flight crew operating manual regarding the requirement to monitor the aircraft’s vertical flight path beyond the final approach fix when the flight path angle guidance mode is engaged.
6. A discrepancy in the Halifax International Airport Authority’s standby generators’ control circuitry caused the 2 standby generators to stop producing power.
7. Air Canada’s emergency response plan for Halifax/Stanfield International Airport indicated that the airline was responsible for the transportation of passengers from an accident site.
8. Air Canada’s emergency response plan did not identify the airport’s Park’N Fly minibuses as transportation resources. 9. The Halifax International Airport Authority’s emergency response plan did not identify that the airport Park’N Fly mini-buses could be used to transport the uninjured passengers, nor did it provide instructions on when and how to request and dispatch any transportation resources available at the airport.
10. The Air Canada Flight Operations Manual did not identify that the required visual reference should enable the pilot to assess aircraft position and rate of change of position in order to continue the approach to a landing.
11. In Canada, the minimum visibility that is authorized by the operations specification for non-precision approaches does not take into account the type of approach lighting system installed on the runway.
12. It is likely that, during the emergency, a passenger activated the L1 door gust lock release pushbutton while trying to expedite his or her exit, which allowed the door to move freely.
13. The passenger seatbacks were dislodged because the shear pins had sheared, likely as a result of contact with passengers during the impact sequence or emergency egress.
14. Recovery of the uninjured passengers from the accident site was delayed owing to a number of factors, including the severe weather conditions; the failure of the airport’s 2 standby generators to provide backup power after the loss of utility power; the loss of the airport operations radio network; and the lack of arrangements for the dispatch of transportation vehicles until after emergency response services had advised that all passengers were evacuated and the site was all clear.
15. Given that the captain rarely used continuous positive airway pressure therapy, he would have been at risk of experiencing fatigue related to chronic sleep disruption caused by obstructive sleep apnea. However, there was no indication that fatigue played a causal or contributory role in this occurrence.
Final Report:

Crash of a Raytheon 390 Premier I in Blackpool

Date & Time: Mar 12, 2015 at 1148 LT
Type of aircraft:
Operator:
Registration:
G-OOMC
Survivors:
Yes
Schedule:
Avignon – Blackpool
MSN:
RB-146
YOM:
2005
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3455
Captain / Total hours on type:
408.00
Circumstances:
The aircraft planned to fly from Avignon Airport, France to Blackpool Airport, with two flight crew and two passengers. The co-pilot performed the external checks; this included checking the fluid level in the hydraulic reservoir, as stated in the ‘Pilot Checklist’. The aircraft was refuelled to 3,000 lb and, after the passengers boarded, it departed for Blackpool. The commander was the pilot flying (PF). The takeoff and cruise to Blackpool were uneventful. Prior to the descent the crew noted ATIS Information ‘Lima’, which stated: Runway 10, wind from 150° at 18 kt, visibility 9 km, FEW clouds at 2,000 ft aal, temperature 11°C, dew point 8°C, QNH 1021 hPa, runway damp over its whole length. The commander planned and briefed for the NDB approach to Runway 10, which was to be flown with the autopilot engaged. Whilst descending through FL120, the left, followed by the right, hydraulic low pressure cautions illuminated. Upon checking the hydraulic pressure gauge, situated to the left of the commander’s control column, the pressure was noted to be ‘cycling up and down’, but for the majority of the time it indicated about 2,800 psi (in the green arc). During this time the hydraulic low pressure cautions went on and off irregularly, with the left caution being on more often than the right. The co-pilot then actioned the ‘HYDRAULIC SYSTEM - HYDRAULIC PUMP FAILURE’ checklist. It stated that if the hydraulic pressure was a minimum of 2,800 psi, the flight could be continued. Just before the aircraft reached the Blackpool NDB, the commander commented “it’s dropping”, but he could not recall what he was referring to. This was followed by the roll fail and speed brk [brake] fail caution messages illuminating. The co-pilot then actioned the applicable checklists. These stated that the Landing Distances Required (LDR) would increase by approximately 65% and 21%, respectively. As the roll fail LDR increase was greater than that of the speed brk fail, the crew used an LDR increase of 65% which the co-pilot equated to 5,950 ft. Runway 10 at Blackpool has an LDA of 6,131 ft, therefore they elected to continue to Blackpool. The roll fail checklist stated that a ‘FLAPS UP’ landing was required. The co-pilot then calculated the VREF of 132 kt, including a 20 kt increment, as stipulated by the ‘FLAPS UP, 10, OR 20 APPROACH AND LANDING’ checklist. The commander then continued with the approach. At about 4 nm on final approach the co-pilot lowered the landing gear, in response to the commander’s request. About 8 seconds later the commander said “just lost it all”; referring to the general state of the aircraft. This was followed almost immediately by the landing gear unsafe aural warning, as the main landing gear was not indicating down and locked. Whilst descending through 1,000 ft, at just over 3 nm from the threshold, the commander asked the co-pilot to action the ‘ALTERNATE GEAR EXTENSION’ checklist. The commander then discontinued the approach by selecting ALT HOLD, increased engine thrust and selected a 500 ft/min rate of climb on the autopilot. However, a few seconds later, before the co-pilot could action the checklist, the main gear indicated down and locked. The commander disconnected the autopilot and continued the approach. The crew did not consider reviewing the ‘HYDRAULIC SYSTEM - HYDRAULIC PUMP FAILURE’ checklist as they had not recognised the symptoms of loss of hydraulic pressure. When ATC issued the aircraft its landing clearance the wind was from 140° at 17 kt. This equated to a headwind component of about 10 kt and a crosswind of about 12 kt. As the aircraft descended through 500 ft (the Minimum Descent Altitude (MDA) for the approach) at 1.5 nm from the threshold, the commander instructed the co-pilot to advise ATC that they had a hydraulic problem and to request the RFFS to be put on standby. There was a slight delay in transmitting this request, due to another aircraft on frequency, but the request was acknowledged by ATC. The aircraft touched down about 1,500 ft from the start of the paved surface at an airspeed of 132 kt and a groundspeed of 124 kt. When the commander applied the toe (power) brakes he felt no significant retardation. During the landing roll no attempt was made to apply the emergency brakes, as required in the event of a power brake failure. The co-pilot asked if he should try to operate the lift dump, but it failed to function, due to the lack of hydraulic pressure. At some point, while the aircraft was on the runway, the co-pilot transmitted a MAYDAY call to ATC. When an overrun appeared likely, the commander shut down the engines. The aircraft subsequently overran the end of the runway at a groundspeed of about 80 kt. The commander later commented that he was in a “state of panic” during the landing roll and was unsure whether or not he had applied the emergency brake. As the aircraft left the paved surface the commander steered the aircraft slightly right to avoid a shallow downslope to the left of runway’s extended centreline. The aircraft continued across the rough, uneven ground, during which the nose gear collapsed and the wing to fuselage attachments were severely damaged (Figure 1). Once it had come to a stop, he shut down the remaining aircraft systems. The passengers and crew, who were uninjured, vacated the aircraft via the entry/exit door and moved upwind to a safe distance. The RRFS arrived shortly thereafter.
Probable cause:
The crew carried out the reservoir level check procedure in accordance with the checklist prior to the flight and found it to be correct, as indicated by the test light not illuminating. This meant that there was at least 1.2 gals (4.5 litres) of fluid within the reservoir. Evidence of hydraulic leakage was only visible within the left engine nacelle. The crew reported fluctuating hydraulic pressure in the latter stages of the flight and intermittent l hyd press lo then r hyd press lo captions on the annunciator panel, the left more than the right. After they had selected the landing gear down the hydraulic pressure dropped completely. The pressure fluctuations suggest that the left pump in particular was struggling to maintain pressure due to cavitation and leakage. As the fluid in the system was gradually depleting, later shown by the fluid accumulation in the engine bay, the right hydraulic pump was also suffering cavitation, as indicated by the r hyd press lo indications. When the MLG was lowered the fluid taken in by the retraction jacks, which is estimated to be at least 4 pints (2.27 litres), further reduced the volume of hydraulic fluid. This resulted in more severe pump cavitation such that the pumps were not able to produce or maintain useable hydraulic pressure. It is likely that the fluid quantity became unviable as the landing gear reached the full extent of its travel, manifesting itself in a delay in getting the gear down and locked indication and the inboard doors not being able to complete their sequence and remaining open. The parking/emergency brake was not affected by the hydraulic system loss. Had a demand been made on the emergency brakes system during the landing it would have worked normally, albeit without anti-skid and a reduced retardation capability. Pump port cap failure The multiple-origin cracking found in the port cap by the laboratory testing had propagated from a thread root in the bore to the outer surface of the cap. It is not known how long the crack had been propagating for, but it is likely that the crack broke the surface of the cap relatively recently, allowing the leakage of fluid outwards under pressure from within the pump. The excessive pitting at the root of the thread is likely to have initiated the fatigue crack, with the thread root radius as a contributory factor. The load imparted into the thread by the compensator plug fitting places the thread under a constant tensile stress when the pump is operating, leading to the eventual fatigue failure.
Final Report: