Crash of an Antonov AN-26B in Ust-Kuyga

Date & Time: Dec 27, 2002
Type of aircraft:
Operator:
Registration:
RA-26053
Flight Type:
Survivors:
Yes
Schedule:
Yakutsk - Ust-Kuyga
MSN:
109 09
YOM:
1981
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
17609
Aircraft flight cycles:
9649
Circumstances:
Following an uneventful cargo flight from Yakutsk, the crew started the approach to Ust-Kuyga on a polar night with an OAT of -51° C. On final approach, at a distance of 1,150 metres from the runway threshold, the aircraft deviated to the right by 150 metres. The captain was instructed by ATC to initiate a go-around but he decided to continue the approach. Unstable, the aircraft's speed dropped to 210 km/h and on the last segment, it lost height, causing the right main gear to struck the runway surface. On impact, the right main gear was torn off, followed shortly later by the nose gear. Out of control, the aircraft slid for few dozen metres before coming to rest. All six occupants escaped uninjured and the aircraft was damaged beyond repair.
Probable cause:
The following findings were identified:
- Wrong approach configuration on part of the crew,
- The aircraft was unstable on approach,
- The approach' speed of 210 km/h was insufficient (20 km/h below the prescribed speed),
- On the last segment, the aircraft rolled to the right following improper actions from the crew,
- The crew failed to initiate a go-around and ignored ATC instructions,
- The configuration adopted by the crew resulted in the aircraft making a deliberate descent to the right of the approach pattern.

Crash of an Embraer C-95A Bandeirante in Curitiba: 3 killed

Date & Time: Dec 26, 2002 at 1120 LT
Type of aircraft:
Operator:
Registration:
2292
Flight Type:
Survivors:
Yes
Schedule:
São Paulo – Florianópolis – Porto Alegre
MSN:
110-174
YOM:
1978
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
13
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The twin engine aircraft departed Campo de Marte AFB near São Paulo on a flight to Porto Alegre with an intermediate stop in Florianópolis, carrying 13 passengers and three crew members. En route to Florianópolis, while in cruising altitude, the crew encountered technical problems, declared an emergency and was cleared to divert to Curitiba-Afonso Pena Airport. On final approach to runway 33, the aircraft stalled and crashed in a grassy area located 3,600 metres short of runway. Two passengers and one pilot were killed while 13 other occupants were injured.
Probable cause:
Double engine failure caused by a fuel exhaustion. It was determined that the crew did not prepare the flight according to procedures and took off with an insufficient fuel quantity on board.

Crash of a Cessna 421A Golden Eagle I in Akron: 2 killed

Date & Time: Dec 25, 2002 at 1006 LT
Type of aircraft:
Registration:
N421D
Flight Type:
Survivors:
No
Schedule:
Denver - Mitchell
MSN:
421A-0045
YOM:
1967
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1230
Captain / Total hours on type:
22.00
Aircraft flight hours:
3564
Circumstances:
The pilot reported to Denver Air Route Traffic Control Center (ZDV) that his left engine had an oil leak and he requested to land at the nearest airport. ZDV informed the pilot that Akron (AKO) was the closest airport and subsequently cleared the pilot to AKO. On reporting having the airport in sight ZDV terminated radar service, told the pilot to change to the advisory frequency, and reminded him to close his flight plan. Approximately 17 minutes later, ZDV contacted Denver FSS to inquire if the airplane had landed at AKO. Flight Service had not heard from the pilot, and began a search. Approximately 13 minutes later, the local sheriff found the airplane off of the airport. Witnesses on the ground reported seeing the airplane flying westbound. They then saw the airplane suddenly pitch nose down, "spiral two times, and crash." The airplane exploded on impact and was consumed by fire. An examination of the airplane's left engine showed the number 2 and 3 rods were fractured at the journals. The number 2 and 3 pistons were heavily spalded. The engine case halves were fretted at the seam and through bolts. All 6 cylinders showed fretting between the bases and the case at the connecting bolts. The outside of the engine case showed heat and oil discoloration. The airplane's right engine showed similar fretting at the case halves and cylinder bases, and evidence of oil seepage around the seals. It also showed heat and oil discoloration. An examination of the propellers showed that both propellers were at or near low pitch at the time of the accident. The examination also showed evidence the right propeller was being operated under power at impact, and the left propeller was operating under conditions of low or no power at impact. According to the propeller manufacturer, in a sudden engine seizure event, the propeller is below the propeller lock latch rpm. In this situation, the propeller cannot be feathered. Repair station records showed the airplane had been brought in several times for left engine oil leaks. One record showed a 3/4 inch crack found at one of the case half bolts beneath the induction manifold, was repaired by retorquing the case halves and sealing the seam with an unapproved resin. Records also showed the station washed the engine and cowling as the repair action for another oil leak.
Probable cause:
The fractured connecting rods and the pilot not maintaining aircraft control following the engine failure. Factors contributing to the accident were the low altitude, the pilot not maintaining minimum controllable airspeed following the engine failure, the pilot's inability to feather the propeller following the engine failure, oil exhaustion, the seized pistons, and the repair station's improper maintenance on the airplane's engines.
Final Report:

Crash of a Swearingen SA227AC Metro III in Aberdeen

Date & Time: Dec 24, 2002 at 0745 LT
Type of aircraft:
Operator:
Registration:
OY-BPH
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Aberdeen - Aalborg
MSN:
AC-580B
YOM:
1984
Flight number:
NFA924
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4600
Captain / Total hours on type:
2800.00
Circumstances:
At approximately 0630 hrs on 24 December 2002, the pilots arrived by car at Aberdeen Airport. With no requirement for their aircraft to transport mail on this occasion, it was decided to fly directly to their home airport in Denmark. The aircraft had been refuelled the previous day and the total fuel on board of 2,200 lb was sufficient for the flight; with no cargo on board, take-off weight was calculated as 12,000 lb (maximum take-off weight: 16,000 lb). The commander carried out an external inspection on OY-BPH while the co-pilot, who was the designated handling pilot for the flight to Denmark, submitted a flight plan. The weather at 0720 hrs was reported as follows: Surface wind 150°M/ 12 kt; visibility 2,500 metres in mist; cloud scattered 100 feet agl, overcast at 200 feet agl; air temperature +9°C; QNH 994 hPa. The runway was reported as wet and Low Visibility Procedures (LVP) had been in force at Aberdeen since 0633 hrs. OY-BPH, callsign 'Birdie Nine Two Four', was parked on Taxiway Bravo and the crew called for, and were given, start clearance at 0736 hrs by 'Ground Movement Control' on frequency 121.7 MHz. Then, following their after-start checks, the crew were cleared to taxi to 'Whiskey Five' for Runway 16 at 0740 hrs. During taxi, the crew were passed and correctly acknowledged the following clearance: "LEAVE CONTROLLED AIRSPACE CLIMBING FLIGHT LEVEL ONE FIVE FIVE SQUAWK SIX TWO FOUR ZERO". Then, at 0742 hrs as the aircraft approached 'Whiskey Five', the crew were transferred to 'Aberdeen Tower' on frequency 118.1 MHz. On the 'Tower' frequency, they were given line-up clearance for Runway 16. At 0743 hrs, the controller transmitted: "BIRDIE NINE TWO FOUR WITH A LEFT TURN DIRECT KARLI CLEAR TAKE OFF ONE SIX SURFACE WIND ONE SIX ZERO ONE TWO KNOTS". The crew correctly acknowledged this clearance. The controller watched the initial movement of the aircraft along the runway before transferring her attention to another aircraft, which was lining up. Shortly after, at 0746 hrs, she transmitted: "OY-BPH REPORT TURNING LEFT" but received no reply. About this time, a telephone message was received in the 'Tower' from a witness in front of the Terminal Building to the effect that an aircraft appeared to have crashed just south of the airfield. This witness had heard a "change in pitch" from the aircraft but had seen no flames prior to it disappearing from his sight: ATC personnel immediately activated their emergency procedures. For the reduced power take-off roll, with the flaps at ¼, the power was set by the commander. The crew considered that the performance of the aircraft was normal, with no unusual instrument indications. The calculated V1 and VR speeds (co-incident at 100 kt) were achieved and called by the commander and, at VR, the co-pilot rotated the aircraft to a pitch attitude of about 12° to 15° nose-up. As the aircraft left the ground, the co-pilot detected the aircraft 'yawing' to the right; almost immediately, he was also aware of a distinct smell of smoke. He called to the commander that he had an engine failure, called for maximum power and tried to maintain control by corrective aileron and rudder inputs. The commander felt the aircraft roll about 15° to the right and realised that there was a problem with the right (No 2) engine. He reached for both power levers and moved them forward. There were no audio or visual warnings associated with the apparent problem. The commander looked at the EGT gauges with the power levers fully forward and noted that the No 2 engine indicated about 600°C EGT, whereas the left (No 1) engine indicated greater than 650°C EGT (the normal maximum) and that its fuel 'Bypass' light was on. He retarded the No 1 power lever until the 'Bypass' light extinguished and noted the resultant EGT at about 630°C. He did not recall any other abnormal indications on the engine instruments but, later in the investigation, the commander recalled hearing a sound "like a compressor stall from the right engine". About this time, the co-pilot heard the automatic "Bank Angle" voice activate. As the aircraft continued to turn to the right, the co-pilot called that he "couldn't control the aircraft". The commander reached for and pulled No 2 engine 'Stop and Feather Control' but, almost immediately, OY-BPH struck the ground initially with the right wing. The aircraft slid along the surface of a field, through a fence and onto a road, before coming to rest. As it did so, the co-pilot was aware that the aircraft had struck a car, which was now at rest outside the right forward side of the cockpit. The co-pilot saw that the whole of the right wing was on fire and called this to the commander before evacuating out of the left door of the aircraft. As the copilot left, the commander pulled No 1 engine 'Stop and Feather Control' and activated both engine fire extinguishers before leaving the aircraft. Outside OY-BPH, the co-pilot went to the car to check if anyone was still inside; as he did so, he saw someone running away. With the intense fire and the car apparently empty, both pilots moved well away from the aircraft. At 0748 hrs, the co-pilot used his mobile phone to advise ATC of the accident and to request assistance. The local emergency services had been alerted at 0745 hrs by a member of the public, who reported a road accident; by 0753 hrs, the local fire service was on the scene. By 0754 hrs, the first AFS vehicle was on the scene and three further AFS vehicles arrived one minute later. A fifth vehicle arrived at 0800 hrs. The fire was quickly extinguished and the Fire Officer confirmed that all the aircraft and vehicle occupants had been located and that there had been no serious injuries. Following runway and taxiway inspections, the airport was re-opened at 0954 hrs.
Probable cause:
Although the investigation was hampered by the lack of FDR data, which might have provided information on engine handling and behaviour, the available evidence from the crew and the initial examination of the aircraft at the accident site, pointed to a major loss of power in the right engine. As a result of the discovery of dead birds close to the point of lift-off on the runway, and a section of braided wire found near the start of the take-off roll, consideration was given as to whether the these had been factors in the accident. The braided wire was not identified as having originated from OY-BPH. There was conclusive evidence that the left engine, which had continued to run, had ingested parts of birds, but no such evidence was found with the right engine. Nevertheless, the crew were adamant that there was a power loss from the right engine and were not conscious of any power reduction from the left engine. The technical examination of the left engine and its propeller assembly revealed evidence of damage consistent with this unit delivering a high level of power at impact. The examination of the right engine and propeller revealed all damage to be consistent with a low, or no, power condition at impact, consistent with either a genuine loss of power or as a consequence of the commander pulling the 'Stop and Feather' control immediately before impact. However, an exhaustive examination of the right engine revealed no evidence of anything that could have caused a failure. Therefore, the items found on the runway were not considered to have been causal or contributory factors in the accident. The crew's recollection of the event included a low EGT indication, at 600°C. This suggested that either the engine might have flamed out, should they have only momentarily looked at the indication as the engine was cooling down, or that the engine was operating at reduced power for an undetermined reason. Flame out could have occurred due to a number of reasons, including, for example, water contamination of the fuel. However, analysis of the bulk supply samples proved negative and, moreover, there were no reports of contaminated fuel from other operators at Aberdeen Airport. Ingestion of ice or water could also have resulted in a flame-out, although this is considered unlikely due to the conditions not being conducive to the formation of engine icing, the lack of significant standing water on the runway, and the absence of heavy precipitation. However, it could not be completely discounted and, if flame-out had occurred, the non-incorporation of the FAA mandated auto-relight system would have reduced the possibility of an immediate relight. Approximately six months before the accident, the left engine had failed during a landing roll-out whilst the aircraft was being operated in Spain. This failure was never satisfactorily explained although, at one stage, the fuel cut-off valve came under suspicion. The valves were interchanged, according to the records, so that the unit that had been fitted to the left engine was installed on the right engine, at the time of the accident. Whilst a stray electrical signal causing the valve to close would certainly result in the engine flaming out, rumours that such events had occurred were not substantiated by the engine manufacturer. In summary, the left engine experienced a bird strike, but with no apparent power loss, and the extensive technical examination could not identify any reason for a loss of power on the right engine. Although an engine failure during takeoff after V1 is a serious emergency, the aircraft was at a relatively light weight and, even with an such a failure, the crew should have been able to fly OYBPH safely away. However, if other factors had been involved, the margins for safe flight would have become more critical. These other factors could have included incorrect operation of the NTS system and/or a failure of the feathering system on the right engine, a concurrent power loss from the left engine, or the crew not handling the emergency effectively. There is no doubt that the left engine had been producing power at impact, but a definite conclusion could not be made as to the blade pitch angles of the right propeller. From the evidence of the commander and the propeller examination by the manufacturer, it is probable that the right propeller was close to the feather position at ground impact. The functionality of the NTS and feathering system could not be determined but, as noted earlier, the pre-flight NTS check actually only ensured that oil pressure was available for this system, and did not check the operation of the whole system. With the evidence that only the left engine had ingested birds, there was a possibility that the left engine was not producing maximum power, although the crew considered it was operating normally. The commander could remember that he compared the engine EGT indications, once he had pushed both power levers forward, and recalled that the left EGT was indicating greater than 650°C with the 'Bypass' light on. He then retarded the left power lever until the 'Bypass' light went out, following which the EGT indicated about 630°C. This retardation of the power lever was not required, as the function of the 'Bypass' system is to reduce the fuel flow in order to keep the engine parameters within limits. This reported retardation could, however, have resulted in a lower engine power than was possible within the available limits, possibly with an associated reduction in EGT. While it remains a possibility that the left engine may have experienced a transient power reduction as a result of the bird ingestion, it is likely that the commander's action in retarding the left power lever resulted in a more significant reduction of power. To maintain straight flight, following an engine failure, it is vital to apply sufficient corrective rudder input to maintain the wings essentially level and minimise the drag due to sideslip. In the case of OYBPH, there was a constant turn to the right before ground impact. The commander's recollection was that left rudder had been applied by the co-pilot, but not to full deflection. The amount of rudder deflection required depends mainly on the airspeed and the difference in engine power but, with the wings not level, more deflection was obviously required, and was available. Greater use of rudder would have reduced the overall drag of the aircraft, with consequent improvement in the aircraft's performance. Furthermore, following an engine failure, the second segment climb requirement is to climb from 35 feet to 400 feet at V2 with the landing gear selected to up. The commander did not raise the gear because he did not observe a positive rate of climb. However, evidence from the FDR was that a maximum airspeed of 128 kt was achieved and, as this was some 19 kt higher than the V2 speed, it indicated that the aircraft had a capability to climb which was not being used. These last three factors may have combined to reduce the climb capability of the aircraft to zero and, in that situation, the decision to not raise the gear was correct. However, all these factors were influenced by inappropriate crew actions. Although both pilots had flown together before, the lack of adherence to JAR-OPS conversion requirements may have been partly responsible for their actions during the emergency.
Final Report:

Crash of a Cessna 208B Super Cargomaster in Rockford: 1 killed

Date & Time: Dec 17, 2002 at 2251 LT
Type of aircraft:
Operator:
Registration:
N277PM
Flight Type:
Survivors:
No
Schedule:
Decatur – Rockford
MSN:
208B-0143
YOM:
1988
Flight number:
PMS1627
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1872
Captain / Total hours on type:
1525.00
Aircraft flight hours:
10120
Circumstances:
The airplane collided with trees and terrain following a loss of control during an Instrument Landing System (ILS) approach at night. The impact occurred approximately 2.1 miles from the approach end of the runway. A witness reported hearing the airplane at "mid-throttle" as it flew over. He then heard the power increase followed by the impact. The witness stated there was no precipitation at the time of the accident and there were "severe winds, mostly from the south, shifting volatile directly from the east." He also stated the visibility was "extremely poor." Statements were received from five pilots who landed in transport category airplanes around the time of the accident. Three of these pilots reported experiencing a crosswind that varied from 15 to 50 knots during the approach. Four of the pilots reported airspeed fluctuations that varied between +/- 8 knots to +/- 10 knots during the approach. Three of the pilots reported breaking out of the clouds between 200 and 300 feet agl. Radar data indicates the airplane was high on the glideslope until it entered a rapid descent from an altitude of about 2,300 feet. Examination of the airframe, engine, and propeller governors failed to reveal any failures/malfunctions that would have resulted in the loss of control.
Probable cause:
The pilot's failure to maintain control of the airplane during the ILS approach. Factors associated with the accident were the low ceilings, high winds, crosswind, and wind shear conditions that existed.
Final Report:

Crash of a Piper PA-31-325 Navajo in Feilding: 3 killed

Date & Time: Dec 17, 2002 at 2041 LT
Type of aircraft:
Operator:
Registration:
ZK-TZC
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Feilding – Paraparaumu
MSN:
31-7812129
YOM:
1978
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1080
Captain / Total hours on type:
70.00
Aircraft flight hours:
1806
Circumstances:
The aircraft took off from Feilding Aerodrome on a visual flight rules flight to Paraparaumu. The normal flight time was about 17 minutes. The pilot and his 2 sons, aged 7 years and 5 years, were on board. Earlier that evening the pilot, his wife and 4 children had attended the pilotís farewell work function in Palmerston North. After the function they all went to Feilding Aerodrome where he prepared ZK-TZC for the flight. The pilotís wife saw him carry out a pre-flight inspection of the aeroplane, including checking the fuel. The pilot seemed to her to be his normal self and he gave her no indication that anything was amiss either with himself or ZK-TZC. She did not see the aeroplane taxi but did see it take off on runway 10 and then turn right. She thought the take-off and the departure were normal and saw nothing untoward. She then drove to Paraparaumu with her 2 younger children, the 2 older boys having left in ZK-TZC with their father. An aviation enthusiast, who lived by the aerodrome boundary, watched ZK-TZC taxi and take off, but he did not see or hear the pilot complete a ground run. He saw the aeroplane take off on runway 10 immediately after it taxied and thought the take-off and departure were normal. He did not notice anything untoward with the aeroplane. A radar data plot provided the time, track and altitude details for ZK-TZC. No radio transmissions from the pilot were heard or recorded by Palmerston North or Ohakea air traffic control. Palmerston North Control Tower was unattended from 2030 on the evening of the accident. The radar data plot showed that after take-off ZK-TZC turned right, climbed to 1000 feet above mean sea level (amsl) and headed for Paraparaumu. When the aeroplane was about 2.7 nautical miles (nm) (5 km) from Feilding Aerodrome and tracking approximately 1.3 nm (2.4 km) northwest of Palmerston North Aerodrome it turned to the left, descended and headed back to Feilding Aerodrome. The aeroplane descended at about 500 feet per minute rate of descent to 400 feet amsl. At 400 feet amsl (about 200 feet above the ground) the aeroplane passed about 0.5 nm (900 m) east of the aerodrome and threshold for runway 28, and joined left downwind for runway 10. In the downwind position the aeroplane was spaced about 0.3 nm (500 m) laterally from the runway at an initial height of 400 feet amsl, or about 200 feet above the ground. ZK-TZC departed from controlled flight when it was turning left at a low height during an apparent approach to land on runway 10, with its undercarriage and flaps extended. ZK-TZC first rotated to face away from the aerodrome before striking the ground in a nose down attitude. The 3 occupants were killed in the impact. Two witnesses, who were about 3.5 km southeast of Palmerston North Aerodrome and about 6 km from the aeroplane, saw the aeroplane at a normal height shortly before it turned back towards Feilding. They described what they thought was some darkish grey smoke behind the aeroplane shortly before it turned around. A witness near Palmerston North recalled seeing the aeroplane in level flight at about 1000 feet before it rolled quickly into a steep left turn and then headed back toward Feilding Aerodrome. After the steep turn the aeroplane descended. He thought that one or both engines were running unevenly. He did not see any smoke or anything unusual coming from the aeroplane. He lost sight of the aeroplane when it was in the vicinity of Feilding. He remembered that at the time it was getting on toward dark and that there was a high cloud base with gusty winds. Another witness travelling on a road from Feilding Aerodrome to Palmerston North saw the aeroplane fly low over his car. He saw the undercarriage extend then retract and that the left propeller was stationary. He believed the other engine sounded normal. He then saw the aeroplane continue toward Feilding Aerodrome and cross the eastern end of the runway. He thought the aeroplane was trying to turn and said it seemed to be quite low and slow. He did not see any smoke coming from the aeroplane. He was not overly concerned because he thought it was a training aeroplane. He said the weather at the time was clear with a high overcast. The aviation enthusiast saw ZK-TZC return for a landing and fly to a left downwind position for runway 10. He thought the aeroplane was quite low. He said the left propeller was feathered and was not turning and believed the right engine sounded normal. He did not see any smoke coming from the aeroplane. He could not recall the position of the undercarriage or flaps. After a while he became concerned when he had not seen the aeroplane land. He described the weather at the time as being fine with good visibility but that it was getting on toward dark. A further witness living near Feilding Aerodrome by the threshold to runway 10 heard the aeroplane coming and then fly overhead. He said the aeroplane sounded very low and very loud, as though its engine was at maximum speed (power). The engine sounded normal, except that it sounded as though it was under high power. He said there was a slight breeze, clear conditions and a high overcast at the time. A couple living by Feilding Aerodrome on the approach path to runway 10 heard the aeroplane coming from a northerly direction. They thought its engine sounded as though it was under a heavy load and said it was making a very loud noise like a topdressing aeroplane. The engine was making a steady sound and was not intermittent or running rough. The steady loud engine noise continued until they heard a loud thump, when the engine noise stopped abruptly. They said that at the time it was getting on toward dark but the weather was clear with good visibility. An eyewitness to the accident saw the aeroplane at a very low height, about the height of some nearby treetops, when it turned left to land. The aeroplane was turning left when she saw it nose up sharply and then suddenly turn back in the opposite direction, before nosing down and hitting the ground nose first. She said the aeroplane seemed to snap in half after it hit the ground.
Probable cause:
The following findings were identified:
- The aircraft records showed ZK-TZC had been properly maintained and was airworthy before the accident.
- No conclusive reason could be found to explain why the left propeller was feathered.
- The pilot chose an improper course of action and flew an improbable circuit in attempting to land ZK-TZC back at the departure aerodrome with one engine inoperative, which led to the accident.
- The pilot's handling of the emergency was unaccountable.
- There was no indication that the training the 2 instructors gave the pilot was anything other than of a proper standard and above the minimum requirements.
- Had the pilot applied the techniques that both instructors said they taught him for a one-engine-inoperative approach and landing, and chosen any of a number of safer options readily available to him, the accident would probably not have occurred.
Final Report:

Crash of a BAe 125-1A-731 in Seattle

Date & Time: Dec 16, 2002 at 1907 LT
Type of aircraft:
Registration:
N55RF
Survivors:
Yes
Schedule:
Sacramento – Seattle
MSN:
25020
YOM:
1964
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13497
Captain / Total hours on type:
1713.00
Aircraft flight hours:
14162
Circumstances:
The Co-Pilot was the flying pilot with the Captain giving directions throughout the approach phase. The Captain stated that he extended the flaps and the landing gear. When the aircraft touched down, the landing gear was not extended. The Co-Pilot reported that she did look down at the landing gear lever and at "three green lights" on the approach. The CVR was read out which indicated that the Co-Pilot directed the Captain to call inbound. The Captain acknowledged this and stated "fifteen flaps." The Co-Pilot then stated "fifteen flaps, before landing." The Captain did not respond to the Co-Pilot but instead made a radio transmission. The Captain shortly thereafter, stated that he was extending the flaps to 25 degrees. The Captain made another radio transmission to the tower when the Co-Pilot stated "final, sync, ignitions." The Captain responded "ignitions on." Full flaps were then extended. The Captain gave the Co-Pilot continued directions while on the approach for heading, speed and altitude. At approximately 300 feet, the Captain stated, "yaw damper's off, air valves are off, ready to land." The Captain reported that it was obvious that touchdown was on the flaps and keel. The Captain stated that he raised the flaps, shutdown the engines, and confirmed that the landing gear handle was down. During the gear swing test the landing gear cycled several times with no difficulties. All red and green lights illuminated at the proper positions. During the test, it was found that the gear not extended horn did not function with the gear retracted, the flaps fully extended and the power levers at idle. Later a bad set of contacts to the relay was found. When the relay was jumped, the horn sounded. Inspection of the damage to the aircraft revealed that the outer rims of both outer tires displayed scrape marks around the circumference of the rim. The outer surface of the gear door fairings were scraped and the flap hinge fairings was ground down.
Probable cause:
The landing gear down and locked was not verified prior to landing. The checklist was not followed, and an inoperative landing gear warning horn were factors.
Final Report:

Crash of a Douglas DC-8-62F in Singapore

Date & Time: Dec 13, 2002 at 1743 LT
Type of aircraft:
Operator:
Registration:
N1804
Flight Type:
Survivors:
Yes
Schedule:
Yokota - Singapore
MSN:
45896/303
YOM:
1967
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11800
Captain / Total hours on type:
7200.00
Copilot / Total flying hours:
6200
Copilot / Total hours on type:
1900
Aircraft flight hours:
73500
Aircraft flight cycles:
29900
Circumstances:
The crew started their duty for the flight from Yokota, near Tokyo, Japan to Singapore at 1000 hours local time (0900 hours Singapore time) on 13 December 2002. The aircraft departed Yokota at 1125 hours local time (1025 hours Singapore time). The FO was the handling pilot for the flight. The expected flight time was about 7 hours. The departure and en route segments of the flight proceeded normally. The crew was aware of Changi Airport’s ATIS ‘Y’ weather information provided at about 1640 hours through Changi Airport’s there were thunderstorm activity, low level windshear and heavy rain in Singapore. The aircraft was given clearance to land on Runway 20R. The FO briefed the other crew members on landing on 20R. At about 7 miles from the airport, Changi Tower advised the aircraft that the wind was from 350 degrees at 5 knots, that the runway surface was wet, that the visibility from the Tower was about 1,000 metres and that landing traffic had reported the braking action at the end of Runway 20R to be from medium to poor. The approach and landing was carried out in heavy rain. The approach was stabilized and normal. Approach speed was about 148 knots. Flaps 35 were used. At about 300 feet above ground, the PIC reported having the approach lights and runway lights in sight while the FO still could not see the lights as the rain removal for the windshield on the FO’s side was not effective. According to the FO, he felt the PIC was putting his hands on the controls of the aircraft. The PIC noticed that the aircraft had drifted slightly left of the runway centreline and told the FO to make the correction back to the centerline. Although the FO made the correction, he was still unable to see the approach lights clearly at about 200 feet. The FO indicated he felt the PIC was in control of the aircraft and making corrections and so he let go of the controls. The CVR recording suggested that the PIC was aware the aircraft was floating down the runway and that the PIC informed the crew that “We are floating way down the runway.” The PIC subsequently moved the control column forward to make a positive landing. The aircraft landed at 1743 hours. The aircraft was observed by an air traffic controller to have touched down on the runway at a point roughly abeam the Control Tower and just before the turn-off for Taxiway W6, which was about 1,500 metres from the end of the runway. Two Airport Emergency Service officers of the Civil Aviation Authority of Singapore also observed that while most aircraft landing on Runway 20R would touch down at a point between the turn-offs for Taxiways W3 and W4, the Arrow Air aircraft floated way beyond the normal touchdown zone. The aircraft’s speed at the time of touchdown was estimated from flight data recorder data to be about 135 knots. Upon touchdown, the PIC deployed spoilers and thrust reversers. The thrust reversers for Engines Nos. 1, 2 and 3 deployed almost immediately while that of Engine No. 4 was reportedly slow in deployment. The PIC and FO also pushed hard on the brake pedals, but they felt that there was no braking response. The aircraft did not stop before reaching the end of the runway. It veered slightly to the right as it exited the runway. The speed of the aircraft when it left the runway was about 60 knots. The aircraft rolled in mud during the overrun. The nose landing gear broke off half way during the overrun and the aircraft came to rest in a grass and soggy area at about 300 metres from the end of the runway. There was no fire. After the aircraft had come to a complete stop, the PIC stowed the thrust reversers. The crew completed the evacuation checklist and exited the aircraft from Door L1 with the assistance of the Airport Emergency Service personnel who had already arrived by then.
Probable cause:
The following significant factors were identified:
- The FO, the pilot flying the approach and landing, did not elect to go around even though he did not have the runway lights and approach lights in sight at 300 feet above ground.
- The PIC could have taken over control from the FO when the latter still could not see the approach lights and runway lights at 300 feet above ground.
- The crew landed long by about 1,300 metres on the runway.
- The crew had not made a determination of the landing distance required for the landing on Runway 20R. They had just verified using the Runway Analysis Manual that the aircraft landing weight was within limit for the landing.
Final Report:

Ground accident of a De Havilland DHC-8-402Q Dash-8 in Xi'an

Date & Time: Dec 7, 2002
Operator:
Registration:
B-3567
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
4005
YOM:
2000
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Two engineers took over the airplane for an engine test run at Xi'an Airport. While parked on the apron, the aircraft started to roll on a slippery ground and eventually collided with the main terminal. Both occupants escaped uninjured while the aircraft was damaged beyond repair. It was reported that snow fell during the preceding days and that the tarmac was slippery.

Crash of an Embraer EMB-110P Bandeirante in Havana

Date & Time: Dec 6, 2002
Operator:
Registration:
CU-T1110
Survivors:
Yes
Schedule:
Holguin - Havana
MSN:
110-098
YOM:
1976
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Havana-José Marti-Rancho Boyeros Airport by night, the crew encountered poor weather conditions with heavy rain falls. In limited visibility, the aircraft descended too low when it impacted the ground and crashed in a wasteland located less than one km from the runway threshold. All 10 occupants were injured and the aircraft was destroyed.