Crash of a Boeing 737-406 in Barcelona

Date & Time: Nov 28, 2004 at 1850 LT
Type of aircraft:
Operator:
Registration:
PH-BTC
Survivors:
Yes
Schedule:
Amsterdam – Barcelona
MSN:
25424
YOM:
1992
Flight number:
KL1673
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
140
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5414
Captain / Total hours on type:
5414.00
Copilot / Total flying hours:
5117
Copilot / Total hours on type:
1543
Aircraft flight hours:
31756
Aircraft flight cycles:
22156
Circumstances:
At 16:46 KLM Flight 1673 departed Amsterdam for Barcelona. Upon rotation from runway 18L the aircraft suffered a bird strike. A bird collided with the nose gear. The gear was retracted normally and there was no abnormal indication in the cockpit. The crew reported the impact to the ATC and the flight to Barcelona continued normally. The aircraft touched down on Barcelona's runway 25R. After touchdown of the nose landing gear, the aircraft started deviating to the left of the runway centreline. The veering to the left continued and the aircraft left the paved surface of the runway and went through an area of soft sand where some construction works were being carried out. The nose landing gear leg collapsed rearwards and the left main landing gear leg detached from its fittings shortly before the aircraft came to a stop close to the edge of a rain drainage canal. The final position of the aircraft was at a longitudinal distance of approximately 1606 m from runway 25R threshold, and at a lateral distance of approximately 84 m from the runway centreline.
Probable cause:
It is considered that the accident probably happened because during the takeoff a bird strike broke one of the cables of the nose wheel steering system of the aircraft and jammed the other, which made that the nose wheels were rotated to the left during landing, causing a veering to the left that could not be arrested by full rudder deflection as the aircraft decelerated. The subsequent application of brakes and other actions by the crew could not avoid that the aircraft went outside the runway surface. The damages to the aircraft were increased by the condition of the runway strip due to the airport construction works. Contributing to the breaking of the cable was the fact that it was severely worn locally. The wear could be traced back to the incorrect application of grease to the cable system during maintenance. Despite the training and experience of the flight crew, they were unable to quickly recognize the possible cause of the deviation of the aircraft and to keep the aircraft on the runway.
Final Report:

Crash of a Gulfstream GIII in Houston: 3 killed

Date & Time: Nov 22, 2004 at 0615 LT
Type of aircraft:
Registration:
N85VT
Flight Type:
Survivors:
No
Schedule:
Dallas - Houston
MSN:
449
YOM:
1985
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
19000
Captain / Total hours on type:
1000.00
Copilot / Total flying hours:
19100
Copilot / Total hours on type:
1700
Aircraft flight hours:
8566
Circumstances:
On November 22, 2004, about 0615 central standard time, a Gulfstream G-1159A, N85VT, operated by Business Jet Services Ltd., struck a light pole and crashed about 3 miles southwest of William P. Hobby Airport, Houston, Texas, while on an instrument landing system approach to runway 4. The two pilots and the flight attendant were killed, an individual in a vehicle near the airport received minor injuries, and the airplane was destroyed by impact forces. The airplane was being operated under the provisions of 14 Code of Federal Regulations Part 91 on an instrument flight rules flight plan. Instrument meteorological conditions prevailed at the time of the accident.
Probable cause:
The flight crew's failure to adequately monitor and cross check the flight instruments during the approach. Contributing to the accident was the flight crew's failure to select the instrument landing system frequency in a timely manner and to adhere to approved company approach procedures, including the stabilized approach criteria.
Final Report:

Crash of an Avro 748-208-2A in Bangkok

Date & Time: Nov 22, 2004
Type of aircraft:
Operator:
Registration:
99-999
Flight Type:
Survivors:
Yes
MSN:
1715
YOM:
1972
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Upon landing, the nose gear collapsed. The aircraft slid for few dozen metres before coming to rest. All occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Failure of the nose gear on landing for unknown reasons.

Crash of a BAe 3101 Jetstream 31 in Caracas: 3 killed

Date & Time: Nov 18, 2004 at 1302 LT
Type of aircraft:
Operator:
Registration:
YV-1083C
Survivors:
Yes
Schedule:
El Vigía – Caracas
MSN:
762
YOM:
1987
Flight number:
VNE213
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
After landing on runway 09, the twin engine aircraft went out of control, veered off runway to the right and eventually collided with the fire station located between both runways 08 and 09 at Caracas-Maiquetía-Simón Bolívar Airport. Two female passengers were killed while 19 other occupants suffered injuries of various degrees. Few hours later, a third passenger died from his injuries. Weather conditions were poor at the time of the accident with heavy rain falls, and the runway surface was wet.

Crash of a Let L-410UVP-E20 in Kilimanjaro

Date & Time: Nov 17, 2004 at 0809 LT
Type of aircraft:
Operator:
Registration:
5H-PAC
Flight Type:
Survivors:
Yes
Schedule:
Kilimanjaro - Kilimanjaro
MSN:
92 27 11
YOM:
1992
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
14000
Captain / Total hours on type:
4000.00
Circumstances:
The aircraft was on a base training flight at Kilimanjaro International Airport. At 0410 hrs it was cleared to the local flying area for upper air works, followed by VOR/ILS approaches to runway 09 via NDB KB. 5H-PAC took off and proceeded to the local flying area where the crew members did upper air works for about 30 minutes. According to the commander, these included clean and dirty stalls, level flights at different speeds, 45 degree turns left and right and exercises on unusual attitudes. Subsequent to these they returned to the airport via NDB KB for ILS approach to runway 09. They carried out a missed approach and proceeded to join RH circuits for touch-and-go operations on runway 09. The last operations before the accident was simulated engine failure after take off followed by single engine overshoot, this time using runway 27. This was approved and the commander was reminded that the surface wind was 090 degrees 08 knots. The aircraft turned left and positioned on right base for runway 27. It was subsequently given a landing clearance. The weather at the material time was fine with temperature 23 degrees Celsius. The controller, who was handling the flight, said that the final approach was perfect. The landing gear was down. The aircraft passed the threshold of runway 27 at about 70 feet above the ground and continued to flare on a straight and level attitude with the landing gear retracted. It continued in this attitude for a distance of about one and a half kilometers down the runway subsequent to which it drifted off the runway to the right. The controller asked the pilot to explain his intentions. There was no reply. Instead, the aircraft was observed to yaw violently as it drifted further to the right. Moments later, it impacted the ground on a grass hedge and skidded along the width of taxiway Y before it came to rest. The commander said that he repossessed the controls immediately when the aircraft started yawing but there was no time effect recovery. There was fuel spillage but fire did not break out. The two pilots, who had not put on their shoulder straps, sustained facial injuries.
Probable cause:
Given that the aircraft was practicing a single engine overshoot, the pilot appears to have descended too low for safe recovery. The landing gear should also have been retracted after power had been applied and positive climb achieved. The standard single engine overshoot procedure was not applied.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in San Antonio: 5 killed

Date & Time: Nov 14, 2004 at 1718 LT
Registration:
N40731
Flight Type:
Survivors:
No
Schedule:
Dodge City – San Antonio
MSN:
31-8152003
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
8590
Aircraft flight hours:
2248
Circumstances:
The twin-engine airplane collided with a residential structure and terrain following a loss of control after the pilot experienced difficulties maintaining course during an Instrument Landing System (ILS) approach while on instrument meteorological conditions. The impact occurred approximately 3.7 miles short of the approach end of the runway. Radar data depicted that after the 8,700-hour commercial pilot was vectored to the ILS Runway 3 approach, the airplane remained left throughout the approach before turning right of the localizer approximately 2 miles before the final approach fix (FAF). Radar then showed the aircraft turn to the left of course line. When the aircraft was abeam the FAF, it was approximately 1 mile left of the course line. As the aircraft closed to approximately 1.5 miles from the runway threshold, the aircraft had veered about 1.3 miles left of the course line (at which time air traffic control instructed the pilot to turn left to a heading of 270 degrees). The aircraft continued to turn left through the assigned heading and appeared to be heading back to the ILS course line. According to the radar, another aircraft was inbound on the ILS course line and Air Traffic Control Tower (ATCT) instructed the pilot to turn left immediately. Thereafter, the aircraft went below radar coverage. A witness, located approximately 1.25 miles northwest of the accident site, reported that he heard a very loud noise, and then observed an airplane flying toward a building, approximately 60 feet in height. The airplane was observed to have pitched-up approximately 45 - 90 degrees just before the building and disappeared into the clouds. A second witness located approximately 1 mile northwest of the accident site reported that he heard a low flying aircraft, and then observed a white twin engine airplane banking left out of the clouds. The airplane leveled out, and flew into the clouds again a few seconds later. The witness stated that the airplane was at an altitude of 100- 200 feet above the ground. A third witness located adjacent to the accident site reported that they heard the sound of a low flying airplane in the distance. As the sound became louder and louder, they looked up and observed the airplane in a near vertical attitude as it impacted trees and the side of an apartment complex. Examination of the airplane did not reveal any preimpact mechanical anomalies. A weather observation taken approximately 15 minutes after the accident included a visibility 4 status miles, light drizzle and mist, and an overcast ceiling at 400 feet.
Probable cause:
The pilot's failure to maintain control during an ILS approach. Contributing factors were the prevailing instrument meteorological conditions( clouds, low ceiling and drizzle/mist), and the pilot's spatial disorientation.
Final Report:

Crash of a Beechcraft 200 Super King Air on Mt Bull: 10 killed

Date & Time: Oct 24, 2004 at 1235 LT
Operator:
Registration:
N501RH
Survivors:
No
Site:
Schedule:
Concord – Martinsville
MSN:
BB-805
YOM:
1981
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
10733
Captain / Total hours on type:
210.00
Copilot / Total flying hours:
2090
Copilot / Total hours on type:
121
Aircraft flight hours:
8078
Circumstances:
On October 24, 2004, about 1235 eastern daylight time (all times in this brief are eastern daylight time based on a 24-hour clock), a Beech King Air 200, N501RH, operated by Hendrick Motorsports, Inc., crashed into mountainous terrain in Stuart, Virginia, during a missed approach to Martinsville/Blue Ridge Airport (MTV), Martinsville, Virginia. The flight was transporting Hendrick Motorsports employees and others to an automobile race in Martinsville, Virginia. The two flight crewmembers and eight passengers were killed, and the airplane was destroyed by impact forces and post crash fire. The flight was operating under the provisions of 14 Code of Federal Regulations (CFR) Part 91 on an instrument flight rules (IFR) flight plan. Instrument meteorological conditions (IMC) prevailed at the time of the accident.
Probable cause:
The flight crew's failure to properly execute the published instrument approach procedure, including the published missed approach procedure, which resulted in controlled flight into terrain. Contributing to the cause of the accident was the flight crew's failure to use all available navigational aids to confirm and monitor the airplane's position during the approach.
Final Report:

Crash of a Beechcraft 1900C off Nassau

Date & Time: Oct 22, 2004 at 1345 LT
Type of aircraft:
Operator:
Registration:
N79YV
Survivors:
Yes
Schedule:
Arthur’s Town – Nassau
MSN:
UB-41
YOM:
1985
Flight number:
SAC204
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8000
Captain / Total hours on type:
112.00
Copilot / Total flying hours:
568
Copilot / Total hours on type:
178
Aircraft flight hours:
26397
Circumstances:
The occurrence of this accident was notified to the Flight Standards Inspectorate by the Nassau Control Tower. On October 22, 2004 about 1328 eastern daylight time (1828Z) a Beechcraft 1900C, N79YV registered to JODA LLC of Chesterfield Missouri, and operated by Southern Air Charter Limited of Nassau, Bahamas, was ditched. The accident occurred in approximately four (4) feet of water, approximately 82 yards off the southern shoreline of New Providence Island (6.98 nautical miles southeast of the Nassau International Airport). The State of Manufacture of the airframe and engines (United States) was advised of the accident on that day and invited to participate in the investigation. The NTSB as well as the FAA were also notified and subsequently made party to the investigation, as the aircraft was a United States registered aircraft operating on an approved United States 129.14 maintenance program. Visual Meteorological Conditions prevailed at the time and an outbound visual flight plan was on file. N79YV operated as a schedule air commuter on a domestic transport flight. The flight originated from Arthur’s Town, Cat Island Bahamas enroute to Nassau International Airport, Nassau, Bahamas. The airplane sustained substantial damage. The occupants of the aircraft consisted of eight (8) passengers and a crew of two (2). The Pilot in Command held an Airline Transport Pilot rating and the First Officer held a Commercial Pilot rating. Both crews were certificated by the Federal Aviation Administration, (FAA). No serious injuries or fatalities were reported.
Probable cause:
Failure of the right engine due to fuel exhaustion. No fuel was found in left or right collector tanks. On October 22, 2004 at 6:35 am, a total of 386 gallons of fuel was uplifted, which brought fuel total to 2800 pounds. A total of 3 flights were conducted lasting 29 minutes, 11 minutes and then 21 minutes (for a total of 61 minutes chock to chock time and a usage of 700 pounds of fuel) which brought fuel total down to 2100 pounds. On October 22, 2004 at 8:42am a further 146 gallons of fuel was uplifted. This additional 146 gallons brought fuel total back to 2800 pounds. No additional fuel slips were produced to show any further uplift of fuel. A total of 8 flights including the fateful flight were conducted with this 2800 pounds of fuel.
Final Report:

Crash of a BAe 3201 Jetstream 32EP in Kirksville: 13 killed

Date & Time: Oct 19, 2004 at 1937 LT
Type of aircraft:
Operator:
Registration:
N875JX
Survivors:
Yes
Schedule:
Saint Louis – Kirksville
MSN:
875
YOM:
1990
Flight number:
AA5966
Crew on board:
2
Crew fatalities:
Pax on board:
13
Pax fatalities:
Other fatalities:
Total fatalities:
13
Captain / Total flying hours:
4234
Captain / Total hours on type:
2510.00
Copilot / Total flying hours:
2856
Copilot / Total hours on type:
107
Aircraft flight hours:
21979
Aircraft flight cycles:
28973
Circumstances:
On October 19, 2004, about 1937 central daylight time, Corporate Airlines (doing business as American Connection) flight 5966, a BAE Systems BAE-J3201, N875JX, struck trees on final approach and crashed short of runway 36 at Kirksville Regional Airport (IRK), Kirksville, Missouri. The flight was operating under the provisions of 14 Code of Federal Regulations Part 121 as a scheduled passenger flight from Lambert-St. Louis International Airport, in St. Louis, Missouri, to IRK. The captain, first officer, and 11 of the 13 passengers were fatally injured, and 2 passengers received serious injuries. The airplane was destroyed by impact and a post impact fire. Night instrument meteorological conditions (IMC) prevailed at the time of the accident, and the flight operated on an instrument flight rules flight plan.
Probable cause:
the pilots' failure to follow established procedures and properly conduct a non precision instrument approach at night in IMC, including their descent below the minimum descent altitude (MDA) before required visual cues were available (which continued unmoderated until the airplane struck the trees) and their failure to adhere to the established division of duties between the flying and non flying (monitoring) pilot.
Contributing to the accident was the pilots' failure to make standard callouts and the current Federal Aviation Regulations that allow pilots to descend below the MDA into a region in which safe obstacle clearance is not assured based upon seeing only the airport approach lights. The pilots' unprofessional behavior during the flight and their fatigue likely contributed to their degraded performance.
Final Report:

Crash of a Casa 212 Aviocar 100 in Lanzarote

Date & Time: Oct 19, 2004
Type of aircraft:
Operator:
Registration:
T.12B-54
Flight Type:
Survivors:
Yes
MSN:
98
YOM:
1979
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft suffered irreparable damages upon landing at Lanzarote Airport. There were no casualties.