Crash of a Britten-Norman BN-2A-26 Islander in Pattaya

Date & Time: Jan 14, 2003 at 1300 LT
Type of aircraft:
Registration:
HS-RON
Flight Phase:
Survivors:
Yes
Schedule:
Pattaya - Pattaya
MSN:
156
YOM:
1970
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft departed Pattaya Airpark runway 10 for a local flight with 6 skydivers and one pilot on board. During initial climb, at a height of about 200-300 feet, the aircraft stalled and crashed in a cassava field located 1,500 metres from the runway end, near the village of Chak Ngaeo. All seven occupants were injured and the aircraft was damaged beyond repair.
Probable cause:
It is believed that the aircraft stalled following an engine failure while the flaps were still in the full down position.

Crash of a Beechcraft 1900D in Charlotte: 21 killed

Date & Time: Jan 8, 2003 at 0849 LT
Type of aircraft:
Operator:
Registration:
N233YV
Flight Phase:
Survivors:
No
Schedule:
Charlotte - Greenville
MSN:
UE-233
YOM:
1996
Flight number:
US5481
Crew on board:
2
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
21
Captain / Total flying hours:
2790
Captain / Total hours on type:
1100.00
Copilot / Total flying hours:
706
Copilot / Total hours on type:
706
Aircraft flight hours:
15003
Aircraft flight cycles:
21332
Circumstances:
On January 8, 2003, about 0847:28 eastern standard time, Air Midwest (doing business as US Airways Express) flight 5481, a Raytheon (Beechcraft) 1900D, N233YV, crashed shortly after takeoff from runway 18R at Charlotte-Douglas International Airport, Charlotte, North Carolina. The 2 flight crewmembers and 19 passengers aboard the airplane were killed, 1 person on the ground received minor injuries, and the airplane was destroyed by impact forces and a post crash fire. Flight 5481 was a regularly scheduled passenger flight to Greenville-Spartanburg International Airport, Greer, South Carolina, and was operating under the provisions of 14 Code of Federal Regulations Part 121 on an instrument flight rules flight plan. Visual meteorological conditions prevailed at the time of the accident.
Probable cause:
The airplane’s loss of pitch control during takeoff. The loss of pitch control resulted from the incorrect rigging of the elevator control system compounded by the airplane’s aft center of gravity, which was substantially aft of the certified aft limit.
Contributing to the cause of the accident was:
1) Air Midwest’s lack of oversight of the work being performed at the Huntington, West Virginia, maintenance station,
2) Air Midwest’s maintenance procedures and documentation,
3) Air Midwest’s weight and balance program at the time of the accident,
4) the Raytheon Aerospace quality assurance inspector’s failure to detect the incorrect rigging of the elevator system,
5) the FAA’s average weight assumptions in its weight and balance program guidance at the time of the accident, and
6) the FAA’s lack of oversight of Air Midwest’s maintenance program and its weight and balance program.
Final Report:

Crash of a Beechcraft B60 Duke off Santo Domingo: 1 killed

Date & Time: Jan 3, 2003 at 2030 LT
Type of aircraft:
Operator:
Registration:
HI-774CT
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Santo Domingo - Santo Domingo
MSN:
P-445
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The twin engine airplane departed Santo Domingo-Las Américas International Airport on a short flight to the Santo Domingo-Herrera Airport located downtown. Following a night takeoff, the pilot encountered a loss of power on the right engine and was unable to feather its propeller. As the propeller was windmilling, he was unable to maintain a safe altitude and elected to ditch the aircraft that crashed in the sea about 800 metres offshore. The pilot was seriously injured and the passenger was killed.

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 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 Britten-Norman BN-2A-26 Islander in Tep Tep: 8 killed

Date & Time: Dec 13, 2002
Type of aircraft:
Operator:
Registration:
P2-CBB
Flight Phase:
Survivors:
No
Site:
Schedule:
Tep Tep – Madang
MSN:
140
YOM:
1969
Location:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
After takeoff from Tep Tep Airstrip, the twin engine aircraft collided with a cliff located in the Finisterre Mountain Range. The aircraft was destroyed and all eight occupants were killed. This was the inaugural flight from the newly constructed Tep Tep Airstrip.

Crash of a Cessna 402C in Lewisville: 1 killed

Date & Time: Dec 4, 2002 at 0616 LT
Type of aircraft:
Registration:
N402ME
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Denton - Dallas
MSN:
402C-0010
YOM:
1979
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1290
Aircraft flight hours:
16464
Circumstances:
The twin-engine airplane impacted the ground during an uncontrolled descent while maneuvering in dark night instrument meteorological conditions in the vicinity of Lewisville, Texas. The commercial pilot contacted the approach controller and stated that his attitude indicator was "not helping" and needed "a little bit of help with trying to keep it straight." The pilot was instructed by approach control to maintain an altitude of 3,000 feet msl. The approach controller confirmed with the pilot that he could not fly headings, and instructed the pilot to turn right. Seconds afterwards, the pilot was instructed to turn left and the controller would tell him when to stop the turn. The pilot acknowledged. There were no further communications between the pilot and air traffic control. The airplane initially impacted in a near vertical attitude into a wooded area adjacent to a rural paved road, slid across the road, and impacted a residence. Radar data showed that the airplane's magnetic heading was erratic throughout the 5-minute flight. The gyro instruments found at the accident site were the copilot's direction gyro (vacuum), a turn and bank indicator (electric), and the pilot's attitude indicator (vacuum). The gyros were disassembled, and visually examined. The co-pilot's direction gyro examination revealed rotation signatures on the gyro and the gyro housing. The turn and bank indicator revealed a "faint" rotational signature on the gyro. The pilot's attitude indicator gyro had no rotational signatures, and exhibited blunt impressions corresponding to the gyro buckets on the inside of the gyro-housing wall. A maintenance repair data plate ("Functional Tested") was found on the attitude indicator's instrument housing dated 12/2/02. Due to the extent of the fire damage, no instrument readings could be obtained. Seven days prior to the accident flight, a company pilot who flew the accident airplane reported that the pilot's attitude indicator (part number 102-0041-04, serial number 92B0346) "rotated" and the flight was aborted. The next day, the attitude indicator was removed and bench checked, cleaned, and adjusted. The attitude indicator was reinstalled and an operational check on the ground was performed. Three days prior to the accident the pilot's attitude indicator was again removed for an overhaul. According to company maintenance personnel, the attitude indicator was reinstalled the night prior to the morning of the accident, and an operational check on the ground was performed. Radar data showed that the aircraft did not stabilize on a particular heading throughout the flight. Physical evidence showed that the pilot's attitude gyro was not "spooled" at the time of impact.
Probable cause:
The failure of the attitude indicator, and the pilot's failure to maintain aircraft control as a result of spatial disorientation following the failure of the attitude indicator. Contributing factors were a low ceiling, clouds, and dark night conditions.
Final Report:

Crash of a Learjet 36A in Astoria

Date & Time: Dec 3, 2002 at 0612 LT
Type of aircraft:
Operator:
Registration:
N546PA
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Astoria - Astoria
MSN:
36-045
YOM:
1980
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3350
Captain / Total hours on type:
2350.00
Copilot / Total flying hours:
1170
Copilot / Total hours on type:
920
Aircraft flight hours:
12335
Circumstances:
The pilot (PIC) reported that during acceleration for takeoff (approximately V1 [takeoff decision speed]) the airplane collided with an elk. The PIC reported that after the collision, he applied wheel brakes and deployed the airplane's drag chute, however, the airplane continued off the departure end of the runway. The airplane came to rest in a marshy bog approximately 50 feet beyond the departure threshold. Currently, approximately 15,000 feet of the airport's perimeter is bordered with animal control fence. The airport recently received a FAA Aviation Improvement Program (AIP) Grant that will provide funding for an additional 9,000-feet of fence. Airport officials stated that the fencing project should be completed by summer of 2003. At the completion of the project, game control fencing will encompass the entire airport perimeter. The U.S. Government Airport/Facilities Directory (A/FD) contains the following remarks for the Astoria Regional Airport: "Herds of elk on and in the vicinity of airport..."
Probable cause:
Collision with an elk during the takeoff roll. Factors include dark night VFR conditions.
Final Report:

Crash of a Fokker F27 Friendship 600 off Manila: 19 killed

Date & Time: Nov 11, 2002 at 0607 LT
Type of aircraft:
Registration:
RP-C6888
Flight Phase:
Survivors:
Yes
Schedule:
Manila - Laoag - Basco
MSN:
10571
YOM:
1978
Flight number:
LPN585
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
29
Pax fatalities:
Other fatalities:
Total fatalities:
19
Circumstances:
Shortly after takeoff from Manila-Ninoy Aquino Airport runway 31, while in initial climb, the captain reported technical problems and elected to return for an emergency landing. Finally, he attempted to ditch the aircraft off Manila. While contacting water, the aircraft lost its tail and sank by a depth of about 15 metres. Fifteen people were rescued while 19 others were killed, among them a crew member.
Probable cause:
Failure of the left engine during initial climb for unknown reasons. It was reported that thick black smoke was coming out from the left engine shortly after liftoff.

Crash of a PZL-Mielec AN-2TP in Sovetskiy

Date & Time: Nov 6, 2002
Type of aircraft:
Registration:
RA-70140
Flight Phase:
Survivors:
Yes
Schedule:
Sovetsky – Svetly
MSN:
1G137-14
YOM:
1972
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
13
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Some passengers were late and the crew apparently hurried the departure to avoid a night flight to Svetly. Doing so, the crew failed to prepare the flight properly and did not proceed to any engine runup prior to taxi and takeoff. During the taxi manoeuvre, the aircraft suffered controllability problems so the crew selected the propeller lever to the fine pitch position. The takeoff procedure was initiated without checks and the crew forgot that the propeller lever was not in the takeoff position. After liftoff, at a height of 3-5 metres, the aircraft encountered difficulties to gain height and speed. The crew attempted an emergency landing when the aircraft collided with trees and crashed in a wooded area. All 15 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Poor flight preparation on part of the crew who failed to follow the pre taxi and the pre takeoff checklist. The aircraft was unable to gain sufficient speed and height after takeoff because the propeller lever was not in the correct position.