Crash of a Britten-Norman BN-2A-21 Islander in Tuguegarao: 3 killed

Date & Time: Dec 12, 2003 at 1500 LT
Type of aircraft:
Operator:
Registration:
RP-C868
Flight Type:
Survivors:
No
Schedule:
Maconacon – Tuguegarao
MSN:
725
YOM:
1974
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
On approach to Tuguegarao Airport, the twin engine aircraft entered clouds and the crew lost visual contact with the runway. The aircraft struck a hill top and crashed in a wooded area located 3 km short of runway. All three occupants were killed.

Crash of a Cessna 414 Chancellor in Greeneville: 4 killed

Date & Time: Dec 11, 2003 at 1047 LT
Type of aircraft:
Operator:
Registration:
N1592T
Survivors:
Yes
Schedule:
Columbus – Greeneville
MSN:
414-0372
YOM:
1972
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
4845
Captain / Total hours on type:
160.00
Aircraft flight hours:
4989
Circumstances:
The pilot was on a circling approach for landing in instrument icing conditions. The landing gear were extended and the flaps were lowered to 15°. The alternate air induction system was not activated. The surviving passenger stated when the airplane came out of the clouds and the airplane started to buffet and shake. The pilot was heard to state on the UNICOM frequency by the fixed base operator and a lineman, "Emergency engine ice." The airplane was observed to make a 60-degree angle of bank and collided with trees and terrain. The Pilot's Operating Handbook states the airplane will stall at 129 miles per hour with the landing gear and flaps down at 15-degrees. The maximum landing weight for the Cessna 414 is 6,430 pounds. The total aircraft weight at the crash site was 6,568.52 pounds. Witnesses who knew the pilot stated the pilot had flown one other known flight in icing conditions before the accident flight.
Probable cause:
The pilot's failure to maintain airspeed while maneuvering in icing conditions on a circling approach for landing resulting in an inadvertent stall and collision with trees and terrain. A factor in the accident was a partial loss of engine power due to the pilot's failure to activate the alternate induction air system, and exceeding the maximum landing weight of the airplane.
Final Report:

Crash of a Fokker F28 Fellowship 4000 in Lokichoggio

Date & Time: Dec 7, 2003 at 1337 LT
Type of aircraft:
Operator:
Registration:
5Y-NNN
Survivors:
Yes
Schedule:
Nairobi – Lokichogio
MSN:
11231
YOM:
1986
Flight number:
HSA812
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
23
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After touchdown at Lokichogio Airport, the crew started the braking procedure when the tyre n°1 on the nose gear burst. Unable to stop within the remaining distance, the airplane overran, collided with a fence and came to rest in a ditch with its nose gear torn off. All 27 occupants evacuated safely while the aircraft was damaged beyond repair.

Crash of a Socata TBM-700 in Oxford: 3 killed

Date & Time: Dec 6, 2003 at 1124 LT
Type of aircraft:
Operator:
Registration:
N30LT
Flight Type:
Survivors:
No
Schedule:
Brussels - Oxford
MSN:
201
YOM:
2001
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1573
Captain / Total hours on type:
500.00
Circumstances:
Towards the end of a flight from Brussels to Oxford (Kidlington), the pilot was cleared to land from a visual straight-in approach to Runway 01. The surface wind was reported as 030°/15 kt. As the aircraft crossed the airfield boundary, it started to roll to the left. Shortly after, it struck the ground to the west of the runway threshold. Despite an extensive investigation, no technical malfunction was identified which could have caused the apparent uncontrolled roll to the left. Although there was no other conclusive evidence which would explain the manoeuvre, it is possible that control of the aircraft was lost during application of power to adjust the flight path or in an attempted late go-around, or as a result of an unknown distraction. The passengers was the French businessman Paul-Louis Halley, CEO of Carrefour, accompanied by his wife. They were en route to England to take part to a wedding.
Probable cause:
Despite an extensive investigation, no definite conclusion could be reached as to why N30LT crashed on a visual approach to Oxford (Kidlington) Airport. No technical evidence was found which would explain the uncontrolled roll but there were certain operational possibilities. Without hard evidence, however, none could be fully supported, but loss of control resulting from an unknown distraction, or during the application of power for flight path adjustment or an attempted late go-around, must be considered as possibilities. The lack of a crash protected data, voice or image recording system on N30LT made it impossible to successfully determine a specific cause or causes of this accident.
Final Report:

Crash of a Beechcraft B200 Super King Air in Newnan: 2 killed

Date & Time: Dec 4, 2003 at 1940 LT
Registration:
N85BK
Flight Type:
Survivors:
No
Schedule:
Douglas – Newnan
MSN:
BB-734
YOM:
1981
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1248
Aircraft flight hours:
9864
Circumstances:
Upon arriving at the destination airport, the controller cleared the flight for localizer 32 approach and informed the pilot that radar service was terminated and a frequency change was approved, report canceling IFR this frequency. The pilot acknowledged the clearance. A review of radar data revealed that the airplane was on course and lined up with the runway when the airplane collided with trees and the ground one mile south of runway 32. A review of information on file with Southeastern Air Charter, Inc., the operator of the accident airplane, found that the pilot's most recent Airman Competency/Proficiency Check was conducted in a Cessna 210. There were no records to indicate the pilot had undergone a flight-check in the Beech 200, as outlined in the Corporations FAA Approved Operational Specifications. Examination of the airframe and engines found no pre-existing discrepancies that would have precluded the airplane from operating properly prior to impact. Surface Weather Observations reported near the time of the accident. was visibility 1 to 1¼ miles; ceiling 200 feet overcast. A review of the approach plate found the minimum descent altitude for the approach to be 325 AGL and visibility 1 mile.
Probable cause:
The pilot's inadequate in-flight planning/decision when he continued the flight below the decision height and collided with trees. A related factor was the low ceiling.
Final Report:

Crash of a Dornier DO228-202 in Bodø

Date & Time: Dec 4, 2003 at 0909 LT
Type of aircraft:
Operator:
Registration:
LN-HTA
Survivors:
Yes
Schedule:
Røst – Bodø
MSN:
8127
YOM:
1987
Flight number:
KAT603
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6400
Captain / Total hours on type:
700.00
Copilot / Total flying hours:
1450
Copilot / Total hours on type:
260
Aircraft flight hours:
11069
Circumstances:
Kato Airline flight KAT603, an aircraft of the type Dornier 228-202 with registration LN-HTA, was to fly a regular scheduled flight from Røst airport (ENRS) to Bodø airport (ENBO). There were two passengers and two pilots on board. There was a strong westerly wind, and when the plane approached Bodø extensive lightning activity developed quickly. The aircraft was struck by a very powerful lightning. The lightning struck the aircraft’s nose area and passed to the tail. Boundings between the fuselage and tail surface and a wire between the tail surface and the elevator were burned off. A powerful electric energy passed through the elevator rod in the tail section. A rod end came loose, resulting in a breach in the control rod. Thus the only connection between the control column in the cockpit and the elevator was lost. This aircraft type has electric pitch trim which adjusts the tail surface angle of attack and after a period the pilots regained limited control of the aircraft’s nose position by using this. When the lightning struck the aircraft, the pilots were blinded for approximately 30 seconds. They lost control of the aircraft for a period and the aircraft came very close to stalling. The pilots declared an emergency. The aircraft’s remaining systems were intact and the pilots succeeded in bringing the plane in for landing. During the first landing attempt the airspeed was somewhat high. The aircraft hit the ground in an approximate three-point position and bounced into the air. The pilots concluded that the landing was uncontrollable because the elevator was not working. The landing was aborted and the aircraft circled for a new attempt. Wind conditions were difficult and the next attempt was also unstable in terms of height and speed. At short final the aircraft nosed down and the pilots barely managed to flare a little before the aircraft hit the ground. The point of impact was a few metres before the runway and the aircraft slid onto the runway. Emergency services quickly arrived at the scene. The two pilots were seriously injured while both passengers suffered only minor physical injuries. No fuel leakage or fire occurred. The aircraft was written off.
Probable cause:
Significant investigation results:
a) The air traffic control service did not have equipment for integrated weather presentation on the radar display.
b) The aircraft’s weather radar did not indicate precipitation cells and was therefore not functioning correctly.
c) Up to 30% of the wires on individual bondings between the fuselage, horizontal stabilizer and elevator may have been broken before the lightning struck.
d) The aircraft was hit by lightning containing a very large amount of energy. The aircraft’s bondings were not able to conduct the electric energy from the lightning and the transfer rod from the cockpit to the elevator was broken.
e) As a result of the reduced control of the aircraft’s pitch and difficult wind conditions, the sink rate was not sufficiently stabilized on short final. The crew were unable to prevent the aircraft from hitting the ground.
Final Report:

Ground accident of a Swearingen SA226AC Metro II in Denver

Date & Time: Dec 3, 2003 at 0555 LT
Type of aircraft:
Operator:
Registration:
N60U
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Denver - Garden City
MSN:
TC-232
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13285
Aircraft flight hours:
25932
Circumstances:
The accident involved 2 Swearingen airplanes. The pilot of the first airplane reported that he had taxied north for departure. There were several company aircraft in front of him in line for departure so he came to a complete stop. The pilot of the second airplane reported that he was also taxiing north for departure. He had seen the lights from an aircraft holding short of runway 17R; however, he did not see the lights of the first airplane until it was too late. The pilot of the second airplane reported he applied full brakes and used reverse thrust but was unable to avoid hitting the first airplane. Both airplanes were substantially damaged.
Probable cause:
The failure of the pilot of the taxiing aircraft to maintain clearance and adequate visual lookout for the stopped aircraft.
Final Report:

Crash of a Swearingen SA227AT Merlin IVC in Spokane: 1 killed

Date & Time: Nov 29, 2003 at 0801 LT
Operator:
Registration:
N439AF
Flight Type:
Survivors:
No
Schedule:
Seattle – Spokane
MSN:
AT-439B
YOM:
1981
Flight number:
AMF1996
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
6253
Captain / Total hours on type:
4406.00
Aircraft flight hours:
15126
Circumstances:
The pilot, who had more than 3,340 hours of pilot-in-command time in the make/model of the accident aircraft, and was very familiar with the destination airport and its ILS approach procedure, departed on a cargo flight in the SA227 turboprop aircraft. The aircraft was dispatched with the primary (NAV 1) ILS receiver having been deferred (out of service) due to unreliable performance the evening before the accident, thus leaving the aircraft with the secondary (NAV 2) ILS receiver for ILS use. The pilot arrived in the destination terminal area and was given vectors to intercept the ILS localizer, and radar data showed the aircraft intercepting and tracking the localizer accurately throughout the approach. Mode C altitude readouts showed the aircraft approaching from below the glideslope at the required intercept altitude of 4,100 feet, passing through and above the glideslope and then initiating a relatively constant descent, the angle of which exceeded the glideslope angle of -3.5 degrees. Weather at the destination airport was 400 foot overcast and the decision height for the ILS/DME runway 21R approach was 270 feet. The aircraft passed through the tops of trees in level flight about 530 feet above the airport elevation and slightly under 3 nautical miles from the runway threshold. The pilot was given a low altitude alert by the tower and acknowledged, reporting that he was descending through 2,800 feet, which was confirmed on the mode C radar readout. At that point the aircraft was well below the ILS glideslope and about 13 seconds from impacting the trees. Post crash examination of information captured from the left and right HSI units and an RMI revealed that the NAV 1 receiver was most likely set on the ILS frequency, and the NAV 2 receiver was most likely set on Spokane VORTAC, a terminal navigation facility located very slightly right of the nose of the aircraft and 14 nautical miles southwest of the destination airport.
Probable cause:
The pilot-in-command's failure to maintain proper glidepath alignment during an ILS approach in poor weather resulting in collision with trees and terrain. Contributing factors were the unreliable status of the primary (NAV 1) ILS receiver (leaving the pilot with only the secondary (NAV 2) ILS receiver), the low ceilings and trees.
Final Report:

Crash of a Boeing 747-258C in Lagos

Date & Time: Nov 29, 2003 at 0235 LT
Type of aircraft:
Operator:
Registration:
ZS-OOS
Flight Type:
Survivors:
Yes
Schedule:
Brussels – Lagos – Johannesburg
MSN:
21190
YOM:
1975
Flight number:
HYC501
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew departed Brussels on a cargo flight to Johannesburg with an intermediate stop in Lagos. On approach by night, the crew was cleared to land on runway 19R that was closed to traffic due to resurfacing process. After touchdown, the aircraft collided with several equipments then veered off runway to the left and came to rest. All nine occupants escaped uninjured while the aircraft was damaged beyond repair. ATC cleared the crew to land on runway 19R while the runway 19L was the one in service at the time of the accident.
Probable cause:
The AIPB reported that the Nigerian Civil Aviation Authority did not know of the closure of the runway, nor that it was aware of the NOTAM until the accident occurred. Runway 19R was not properly closed in accordance with standard practice, as the runway lights were all switched on indicating runway serviceability.

Crash of a Swearingen SA26AT Merlin IIB in Jacksonville: 1 killed

Date & Time: Nov 27, 2003 at 0752 LT
Type of aircraft:
Registration:
N698X
Flight Type:
Survivors:
Yes
Schedule:
Beaumont – Jacksonville
MSN:
T26-137
YOM:
1969
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4500
Aircraft flight hours:
8263
Circumstances:
The pilot was on an instrument flight from Beaumont, Texas, to Craig Airport, Jacksonville, Florida. According to the pilot's children who were passengers on the airplane, the pilot knew the destination airport was forecast to have fog upon their arrival. Air traffic controllers informed the pilot east of Tallahassee, Florida, the fog at his destination airport would not lift for at least an hour and a half. The pilot was informed the weather at Saint Augustine, Florida, was clear skies with two miles visibility. The pilot informed the controller that he would slow the airplane and continue to Craig. The pilot was subsequently cleared to descend and provided vectors for the ILS Runway 32 approach at Craig. The pilot informed the controller that he had the current automatic terminal information service (ATIS) information. The ATIS for Craig reported an indefinite ceiling with a vertical visibility of 100 feet, and one-quarter of a mile visibility. The weather minimums for the ILS runway 32 approach is a decision height of 241 feet, and one-half mile visibility. The controller informed the pilot to contact Craig Tower. The pilot contacted Craig Tower, and was instructed to report passing the final approach fix. The controller informed the pilot that Jacksonville International Airport had a runway visual range of more than 6,000 feet, and that airplanes were making it in. The controller asked the pilot what his intentions were in the event he made a missed approach. The pilot replied, "I got my brother bringing my mom there into your airfield, so I do not know, what do you think is best, what's closest." The controller replied Jacksonville was closer than Saint Augustine. The pilot informed the controller that he would go to Jacksonville in the event of a missed approach. The pilot was cleared to land, and there was no further radio contact between the pilot and Craig Tower. The airplane was located a short time later in a wooded area, 1.8 miles from the airport. Postaccident examination of the airplane revealed no preimpact mechanical anomalies.
Probable cause:
The pilot's descent below decision height while performing an ILS approach with low ceilings and fog, resulting in an in-flight collision with trees and the ground. A factor associated with the accident was the pilot's decision to attempt the instrument approach with weather below the prescribed minimums.
Final Report: