Crash of a Piper PA-31-350 Navajo Chieftain in Las Primaveras

Date & Time: Mar 12, 2003 at 1940 LT
Registration:
LV-MML
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Mendoza – Buenos Aires
MSN:
31-7852133
YOM:
1978
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4364
Captain / Total hours on type:
52.00
Copilot / Total flying hours:
1109
Copilot / Total hours on type:
142
Circumstances:
The twin engine airplane departed Mendoza-El Plumerillo on a ferry flight to Buenos Aires-Aeroparque-Jorge Newbury Airport with two pilots on board. After takeoff, the crew was cleared to climb to 7,000 feet then to proceed to the east via airway W9. About 20 minutes into the flight, after being cleared to descend to FL55, the crew noticed smoke in the cabin. Assuming the smoke was coming from under the panel instruments, the crew used the fire extinguisher put smoke continued to spread in the cabin. The crew informed ATC about his situation, reduced his altitude and attempted an emergency landing. The crew lowered the landing gear but completed a flapless landing in an open field. The aircraft rolled for few dozen metres before coming to a halt, bursting into flames. Both pilots evacuated safely while the aircraft was consumed by fire.
Probable cause:
A fire broke out in flight, probably in the electrical wiring, for reasons that investigations were unable to determine.
Final Report:

Crash of a Cessna 208B Grand Caravan in Kotzebue

Date & Time: Mar 2, 2003 at 1504 LT
Type of aircraft:
Operator:
Registration:
N205BA
Flight Type:
Survivors:
Yes
Schedule:
Shungnak - Kotzebue
MSN:
208B-0890
YOM:
2001
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
25600
Captain / Total hours on type:
4200.00
Aircraft flight hours:
2082
Circumstances:
Prior to departing on an air taxi flight, the airline transport certificated pilot obtained a weather briefing and filed a VFR flight plan for a trip from his home base, to several remote villages, and return. The area forecast contained an AIRMET for IFR conditions and mountain obscuration due to clouds and light snow. The terminal forecast contained expected conditions that included visibilities ranging from 3 to 3/4 mile in blowing snow, a vertical visibility of 500 feet, and wind speeds from 14 to 22 knots. During the filling of the flight plan, an FAA flight service station specialist advised that VFR flight was not recommended. The pilot acknowledged the weather information and departed. When the pilot took off on the return flight from an airport 128 miles east of his home base, the pilot reported that the visibility at his base was greater than 6 miles. As he neared his home base, the visibility had decreased and other pilots in the area were requesting special VFR clearances into the Class E surface area. The pilot requested a special VFR clearance at 1441, but had to hold outside the surface area for other VFR and IFR traffic. At 1453, a METAR at the airport included a wind 080 of 26 knots, and a visibility of 1 mile in blowing snow. While holding about 7 miles north of the airport, the pilot provided a pilot report that included deteriorating weather conditions east of the airport. Once the pilot was cleared to enter the surface area at 1458, he was provided with an airport advisory that included wind conditions of 25 knots, gusting to 33 knots. While the pilot was maneuvering for the approach, a special aviation weather observation at 1501 included a wind condition of 26 knots, and a visibility of 3/4 mile in blowing snow. The pilot said he established a GPS waypoint 4 miles from the runway and descended to 1,000 feet. He continued inbound and descended to 300 feet. At 1 mile from the airport, the pilot said he looked up from the instrument panel but could not see the airport. He also stated that he was in a whiteout condition. The airplane collided with the snow-covered sea ice, about 1 mile from the approach end of the runway threshold at 1504.
Probable cause:
The pilot's continued VFR flight into instrument meteorological conditions, and his failure to maintain altitude/clearance above the ground, resulting in a collision with snow and ice covered terrain during the final approach phase of a VFR landing. Factors in the accident were whiteout conditions and snow-covered terrain.
Final Report:

Crash of a Cessna 402B off Marathon

Date & Time: Feb 20, 2003 at 1220 LT
Type of aircraft:
Registration:
N554AE
Flight Type:
Survivors:
Yes
Schedule:
Havana – Marathon – Miami
MSN:
402B-1308
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4000
Captain / Total hours on type:
817.00
Aircraft flight hours:
11303
Circumstances:
The fuel tanks were filled the day before the accident date, and on the day of the accident, the airplane was flown from that airport to the Miami International Airport, where the pilot picked up 2 passengers and flew uneventfully to Cuba. He performed a preflight inspection of the airplane in Cuba and noted both auxiliary fuel tanks were more than half full and both main tanks were half full. The flight departed, climbed to 8,000 feet; and was normal while in Cuban airspace. When the flight arrived at TADPO intersection, he smelled strong/fumes of fuel in the cabin. The engine instruments were OK at that time. The flight continued and when it was 10-12 miles from Marathon, he smelled something burning in the cabin like plastic material/paper; engine indications at that time were normal. He declared "PAN" three times with the controller, and shortly thereafter the right engine began missing and surging. He then observed fire on top of the right engine cowling near the louvers. He secured the right engine however the odor of fuel and fumes got worse to the point of irritating his eyes. He declared an emergency with the controller, began descending at blue line airspeed, and the fumes/odor got worse. Approximately 5 minutes after the right engine began missing and surging, the left engine began acting the same way. He secured the left engine but the propeller did not completely feather. At 400 feet he lowered full flaps and (contrary to the Pilot's Operating Handbook and FAA Approved Airplane Flight Manual) the landing gear in preparation for ditching. He intentionally stalled the airplane when it was 5-7 feet above the water, evacuated the airplane with a life vest, donned then inflated it. The airplane sank within seconds and he was rescued approximately 20 minutes later. The pilot first reported 4 months and 19 days after the accident that his passport which was in the airplane at the time of the accident had burned pages. He was repeatedly asked for a signed, dated statement that explained where it was specifically located in the airplane, and that it was not burned before the accident flight; he did not provide a statement. Examination of the airplane by FAA and NTSB revealed no evidence of an in-flight fire to any portion of the airplane, including the right engine or engine compartment area, or upper right engine cowling. Examination of the left engine revealed no evidence of preimpact failure or malfunction. The left magneto operated satisfactorily on a test bench, while the right magneto had a broken distributor block; and the electrode tang which fits in a hole of the distributor gear; no determination was made as to when the distributor block fractured or the electrode tang became bent. The left propeller blades were in the feathered position. Examination of the right engine revealed no evidence or preimpact failure or malfunction. The right hand stack assembly was fractured due to overload; no fatigue or through wall thickness erosion was noted. Both magnetos operated satisfactorily on a test bench. The right propeller was in the feathered position. An aluminum fuel line that was located in the cockpit that had been replaced the day before the accident was examined with no evidence or failure or malfunction; no fuel leakage was noted.
Probable cause:
The loss of engine power to both engines for undetermined reasons.
Final Report:

Crash of a Britten-Norman BN-2A-27 Islander in Panama: 1 killed

Date & Time: Dec 29, 2002 at 1606 LT
Type of aircraft:
Operator:
Registration:
HP-1016PS
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Bocas del Toro – Panama City
MSN:
628
YOM:
1971
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The pilot, sole on board, was returning to his base at Panama City-Albrook Marcos A. Gelabert Airport after he dropped seven passengers in Bocas del Toro. En route, the twin engine aircraft was lost without trace. SAR operations were initiated but eventually suspended on January 8, 2003, as no trace of the aircraft nor the pilot was found.

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 Beechcraft 1900C in Eagleton: 3 killed

Date & Time: Dec 9, 2002 at 1140 LT
Type of aircraft:
Operator:
Registration:
N127YV
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Wichita - Mena
MSN:
UC-127
YOM:
1990
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
10200
Aircraft flight hours:
12473
Circumstances:
The aircraft collided with mountainous terrain in a level descent during a visual approach to the destination airport. According to recorded radar data, 10 minutes after descending from 15,000 feet, the flight impacted about 200 feet below the top of the partially obscured ridgeline (elevation of 2550 feet), and 8 miles from the destination. The data indicates the flight path was similar to the global positioning satellite (GPS) approach to the airport. Six minutes before the accident, and the pilot's last transmission to air traffic control, he was informed and acknowledged that radar service was terminated. The flight was 12.4 miles from the accident site when radar contact was lost. Reduced visibility due to fog hampered search & rescue efforts, and the aircraft wreckage was located the next day. The aircraft was equipped with a GPS navigation system; however the installation was incomplete, restricting its use to visual flight rules (VFR) only. The investigation did not determine if the GPS was being used at the time. A non-enhanced Ground Proximity Warning System was also installed. The maximum elevation figure listed on the sectional aeronautical chart covering the area of the accident site and destination airport was 3000 feet mean sea level. The chart also shows an advisory for the area to use caution due to rapidly rising.
Probable cause:
In-flight collision with terrain due to the pilot's failure to maintain clearance and altitude above rapidly rising terrain while on a VFR approach. Contributing factors were the obscuration of the terrain due to clouds.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Sanderson: 1 killed

Date & Time: Aug 16, 2002 at 1135 LT
Registration:
N680HP
Flight Type:
Survivors:
No
Site:
Schedule:
Charleston - Charleston
MSN:
31-8052205
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5720
Aircraft flight hours:
4493
Circumstances:
The pilot completed a flight without incident, and seemed in good spirits before departing, by himself, on the return flight. The second flight also progressed without a incident until cleared from 8,000 feet msl to 5,000 feet msl, which the pilot acknowledged. Visual meteorological conditions prevailed at the time, and radar data depicted the airplane initiate and maintain a 500-foot per-minute descent until radar contact was lost at approximately 400 feet agl. The pilot made no mention of difficulties while en route or during the descent. The airplane impacted trees at the top of a ridge in an approximate level attitude, and came to rest approximately 1,450 feet beyond, at the bottom of a ravine. Examination of the wreckage revealed no preimpact failures or malfunctions. The pilot had been diagnosed with Crohn's disease (a chronic recurrent gastrointestinal disease, with no clear surgical cure) for approximately 35 years, which required him to undergo several surgeries more than 20 years before the accident. The pilot received a letter from the FAA on June 11, 1998, stating he was eligible for a first-class medical certificate. In the letter there was no requirement for a follow up gastroenterological review, but the pilot was reminded he was prohibited from operating an aircraft if new symptoms or adverse changes occurred, or anytime medication was required. His condition seemed to be stable until approximately 5 months prior to the accident. During this time frame, he experienced weight loss and blood loss, was prescribed several different medications to include intravenous meperidine, received 3 units of blood, and had a peripherally inserted central catheter placed. On the pilot's airmen medical application dated the month prior to the accident, the pilot reported he did not currently use any medications, and did not note any changes to his health. A toxicological test conducted after the accident identified meperidine in the pilot's tissue.
Probable cause:
Physiological impairment or incapacitation likely related to the pilot's recent exacerbation of Crohn's disease. A factor in the accident was the pilot's decision to conduct the flight in his current medical condition.
Final Report:

Crash of an Ilyushin II-86 in Moscow: 14 killed

Date & Time: Jul 28, 2002 at 1525 LT
Type of aircraft:
Operator:
Registration:
RA-86060
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Moscow - Saint-Petersburg
MSN:
51483203027
YOM:
1983
Country:
Region:
Crew on board:
16
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
14
Aircraft flight hours:
18363
Circumstances:
The aircraft was leaving Moscow on a ferry flight to St Petersburg following a charter flight from Sochi. On board were 16 crew members, among them 10 employees of the company. Two seconds after takeoff from runway 07L, while climbing to a height of about 200 metres, the stabilizers trimmed to the full up position of 12°. The aircraft nosed up and reached a super critical angle of attack. The crew attempted to regain control by pushing the control column forward but the aircraft stalled and crashed in a huge explosion about 700 metres past the runway end. Two stewardesses were injured while 14 other occupants were killed.
Probable cause:
The cause could not be determined with certainty due to the almost complete destruction of the main and reserve stabilizer control system units as a result of the fire on the ground and lack of information on the primary and backup stabilizer control systems on the flight data recorder, and the lack of crew comments on the cockpit voice recorder. The accident of IL-86 RA-86060 could be caused by an electrical failure in the stabilizer control system, which led to the reverse control response when controlling the stabilizer from the main system or inadequate actions of one of the pilots, expressed in pressing and holding the "pitch up" stabilizer switch on the control column.

Crash of a Let L-410UVP near Calabar: 5 killed

Date & Time: May 21, 2002 at 1942 LT
Type of aircraft:
Registration:
9Q-CGX
Flight Type:
Survivors:
No
Schedule:
Abuja – Port Harcourt – Calabar
MSN:
85 14 02
YOM:
1985
Flight number:
SXC401
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
5
Aircraft flight hours:
8086
Circumstances:
On the day of the accident, the aircraft departed Abuja with the call Sign SXC401 en route Port Harcourt conveying 2 passengers on revenue basis. Before the commencement of the flight, the Chief Engineer was reported to have replaced the "Carbon brush" of the starboard starter generator. The source of this pair of carbon brushes is questionable. This flight was uneventful as the passengers disembarked and the aircraft picked up fuel for Port Harcourt. The aircraft departed Port Harcourt at 1750 hrs UTC with five souls on board (all crewmembers), estimating Calabar at 1827 hrs UTC. At 1800 hrs UTC, the aircraft was in contact with Calabar Tower at 5,000 feet, reporting 5 Souls-On-Board and an endurance of 3 hrs 30 minutes. The crew also requested for the hourly weather report and the control tower passed the 1700 hours weather report as "surface wind 140°/ 09 knots, visibility 10km, slight thunderstorm, cloud base scattered 300 metres, few CB N-SE 690 m broken at 9,000 m, QNH 1008 and temperature 27°C". The aircraft was also instructed to maintain the 5,000 feet level and to expect no delay for the VOR approach to runway 03. At 1809 hrs UTC, the aircraft was at 35 nautical miles to the station when the pilot requested for descent clearance and the controller gave him a clearance to 2,500 feet and to position for a straight-in approach to runway 03 and the crew acknowledged. At 1824 hrs UTC, the pilot reported having electrical problem and therefore declared emergency. Thereafter, the pilot requested for increase in the intensity of the approach lights, the controller informed him that the approach lights were, already, at their maximum intensity. The controller procedurally then requested for the aircraft's altitude but the response of the pilot was "we are coming to Calabar" and at 1830 hrs the aircraft reported 16 nautical miles to Calabar. The control tower at 1833 hrs UTC, wanted to establish the position of the aircraft by requesting repeatedly "Your position? Your position?" to which the response was "standby, standby". The verbal query continued until 1842 hrs and when there was no response from the aircraft, the controller alerted the airport fire services to be on the standby for further instructions. When the controller could no longer establish contact with the aircraft, he then contacted the relevant agencies for search and rescue operations. Meanwhile, the aircraft on descent impacted trees and crashed in a marshy area located 22 km from the airport. The aircraft was destroyed and all five occupants were killed.
Probable cause:
The probable cause of the accident was the premature departure of the aeroplane from the normal Minimum Safe Altitude of 2,500 feet without ATC clearance until it flew into the terrain. The contributory factor was the emergence of electrical problem on the aircraft on the commencement of its approach. The problem might have distracted the attention of the pilots from having undistorted focus on the instruments. Another contributory factor was the unfavourable weather conditions of low cloud base and thunderstorm, which impaired the visibility at the critical time of the descent.
Final Report:

Crash of a Let L-410UVP-E off Djibouti City: 4 killed

Date & Time: Mar 17, 2002 at 1802 LT
Type of aircraft:
Operator:
Registration:
J2-KBC
Flight Type:
Survivors:
No
Schedule:
Mogadishu – Djibouti City
MSN:
91 25 37
YOM:
1991
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
Following an uneventful flight from Mogadishu, the crew started the descent to Djibouti City-Ambouli Airport. While the runway 09 was in use, the crew was cleared for an approach to runway 27. While completing a last turn to the left to join the glide, the aircraft went out of control and crashed in the sea. All four occupants were killed.