Ground accident of a Boeing KC-135R Stratotanker in Bishkek

Date & Time: Sep 26, 2006 at 2010 LT
Type of aircraft:
Operator:
Registration:
63-8886
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Bishkek - Bishkek
MSN:
18734
YOM:
1964
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On Sept. 26, at approximately 8:03 p.m. local time, a KC-135R landed at Manas International Airport following a combat mission over Afghanistan. After landing, the KC-135R was parked at the intersection of the active runway and a taxiway while the crew awaited clarification on instructions from the air traffic control tower. The KC-135R was struck by a host nation TU-154 that was taking off. The TU-154's right wing struck the fairing of the KC-135R's No. 1 engine. The force of the impact nearly severed the No. 1 engine from KC-135R and destroyed a portion of the aircraft's left wing. The TU-154 lost approximately six feet of its right wingtip, but was able to get airborne and return to the airport for an emergency landing with no additional damage to the aircraft. The three aircrew members on board the KC-135R, as well as the nine aircrew members and 52 passengers aboard the TU-154, survived the accident. None of the aircrew or passengers on board the TU-154 sustained any injuries. One KC-135 crew member sustained minor abrasions while evacuating the aircraft.
Probable cause:
The collision between the TU-154 and KC-135R aircraft was clearly an accident and not the result of any intentional conduct. The Accident Investigation Board, convened by AMC, determined that the accident was caused by the Kyrgyzaeronavigation air traffic controller who cleared a civilian airliner for takeoff without verifying that the KC-135R was clear of the runway. In addition to the air traffic controller, the AIB found evidence of several contributing factors involving the KC-135R aircrew, conflicting published airport notices, and a tower liaison employed by the U.S. Government to facilitate communication between the tower and U.S. aircrews. Although the AIB found the air traffic controller primarily at fault, the U.S. KC-135R crew and tower liaison shared responsibility for ensuring the KC-135R cleared the runway to a safe location following landing. The accident might have been avoided had any of them exercised better awareness of their situation.
In conclusion, the AIB determined the principal cause of the mishap was the Kyrgyzaeronavigation controller clearing the TU-154 for takeoff without verifying that KC-135R was clear of the runway, there was evidence the following factors also contributed to the mishap:
- The Kyrgyz air traffic controller's instruction to vacate at taxiway Golf after dark conflicted with a published Notice to Airmen (NOTAM) that limited that taxiway's use to daylight hours. The contractor safety liaison (LNO) employed by the U.S. Air Force to facilitate communication between its aircrews and Kyrgyz controllers did not clarify the apparent discrepancy.
- After questioning the Kyrgyz controller's instruction to vacate the runway at taxiway Golf, the LNO instructed the KC-135R crew to hold short of Alpha. The mishap KC-135R crew misperceived the LNO's instructions and responded "holding short of Golf." The LNO failed to catch the read-back error.
- The Kyrgyz controller failed to maintain awareness of the KC-135R's location.
- The LNO failed to maintain situational awareness and intervene when the controller's actions endangered the KC-135R and aircrew.
The KC-135R is assigned to the 92nd Air Refueling Wing, Fairchild Air Force Base, Wash. While deployed at Manas AB, the KC-135R and its aircrew were assigned to U.S. Central Command's 376th Air Expeditionary Wing, flying missions supporting coalition aircraft over Afghanistan.
Final Report:

Ground accident of a Boeing 727-224F in Bogotá

Date & Time: Aug 17, 2006 at 0054 LT
Type of aircraft:
Operator:
Registration:
HK-3985
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Bogotá – Barranquilla
MSN:
20465/814
YOM:
1970
Flight number:
KRE192
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
71978
Circumstances:
While taxiing at Bogotá-El Dorado Airport, ready for a cargo flight to Barranquilla, the aircraft suffered a technical problem with the right main gear that collapsed. All three crew members escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Failure of the right main gear during taxi due to the presence of corrosion in the trunnion.

Ground accident of a Douglas DC-9-51 in Minneapolis

Date & Time: May 10, 2005 at 1936 LT
Type of aircraft:
Operator:
Registration:
N763NC
Flight Phase:
Survivors:
Yes
Schedule:
Columbus - Minneapolis
MSN:
47716/822
YOM:
1976
Flight number:
NW1495
Crew on board:
5
Crew fatalities:
Pax on board:
94
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
10811
Captain / Total hours on type:
6709.00
Copilot / Total flying hours:
3985
Copilot / Total hours on type:
3985
Aircraft flight hours:
67268
Aircraft flight cycles:
66998
Circumstances:
The DC-9 was taxiing to the gate area when it collided with a company A319 that was being pushed back from the gate. Prior to arriving at the destination airport, the DC-9 experienced a loss of hydraulic fluid from a fractured rudder shutoff valve located in the DC-9's right side hydraulic system. The left side hydraulic system had normal hydraulic pressure and quantity throughout the flight. The flightcrew elected to continue to the scheduled destination and declared an emergency while on approach to the destination airport. After landing, the emergency was negated by the flight crew and the airplane taxied to the gate. Flight data recorder information indicates the left engine, which provides power for the left hydraulic system, was shut down during taxi. The captain stated he did not remember shutting the left engine down, and that if he had, it would have been after clearing all runways. The first officer stated that he was unaware that the left engine was shut down. Upon arrival at the gate with the left engine shut down and no hydraulic pressure from the left system and a failure of the right hydraulic system, the airplane experienced a loss of steering and a loss of brakes. The flightcrew requested company maintenance to chock the airplane since they were unable to use brakes to stop the airplane. The crew said they were going to keep the "...engines running in case we have to use reversers..." The airplane began to roll forward and the captain applied reverse thrust but the reversers did not deploy. The airplane impacted the A319 with a speed of approximately 15.65 miles per hour to 16.34 miles per hour. Evacuation of the DC-9 was completed approximately 5:22 minutes after the collision and evacuation of the A319 occurred approximately 13:08 minutes after the collision. Examination of the left hydraulic system revealed no anomalies and examination of the right hydraulic system revealed a fractured rudder shutoff valve that displayed features consistent with fatigue. Following the accident, the airplane manufacturer issued a service letter pertaining to the replacement of the rudder shutoff valve based upon reliability information that was reported to them. The number of reports was greater than that of the Federal Aviation Administration's Service Difficulty Reports database, and less than the operators records.
Probable cause:
The Captain's decision to shutdown the left engine during taxi with no hydraulic pressure on the right side hydraulic system to effectively operate the brakes, steering, or thrust reversers. A factor was the fatigue fracture of the rudder shutoff valve which resulted in the loss of right side hydraulic pressure.
Final Report:

Ground fire of a Transall C-160 in Fort-de-France

Date & Time: May 6, 2004 at 1358 LT
Type of aircraft:
Operator:
Registration:
R100/F-RAZR
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Fort-de-France - Fort-de-France
MSN:
F100
YOM:
1970
Country:
Crew on board:
8
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4306
Copilot / Total flying hours:
2564
Aircraft flight hours:
18530
Circumstances:
The aircraft was engaged in a local post maintenance test flight at Fort-de-France-Le Lamentin Airport, carrying five technicians and three crew members on behalf of the Escadron de Transport Outremer 58. After engine startup, the crew started to taxi when a fire erupted. The aircraft was stopped on the ramp and all eight occupants escaped uninjured. Within three minutes, fire bombers were on site and extinguished the fire. Nevertheless, the aircraft was damaged beyond repair.
Probable cause:
The accident was caused by electrical arcing at the power cable to a submersible fuel pump. This arcing occurred above the kerosene liquid inside the tank full of fuel vapors. The cable type used was chosen at the time of the design of the aircraft. Atmospheric conditions on the apron of Fort de France have raised the temperature of the reservoir beyond the flash point kerosene. The vapors contained in this tank were explosive, and the arc was enough to initiate the blast. As such, atmospheric conditions are a certain cause of environmental origin of the accident. The appearance of the arc is, in turn, has only technical causes:
- The quality of cable used and age are in fact responsible for the creation of the electric arc.
- The formation of the insulating sheath of this type of cable is not likely to ensure an absolute seal. This quality is also not claimed by its manufacturer.
Indeed, the analysis carried out show a porosity of electrical cable, even nine, therefore that it is soaked in kerosene. The presence of kerosene increases the phenomenon of porosity of old cables. Degradation characteristics of dielectric strength of the cable insulation explains the appearance of the arc. The accident occurred while the cable was over 19 years old. The fuel pumps wiring has never been a problem. But there has not been a cable that had reached the age of 19 years. The aging of the cable could still degrade the seal. Finally, maintaining this type of cable on the first C160 series until this accident was part of a complex process in which traceability has not been formally established. Doubts indeed appeared in 1969 on the quality of these cables, doubts that can be considered today as precursors. Measures had been adopted precisely to overcome these deficiencies. In this regard, the replacement of the fuel pump wiring of the second series C 160 of these cables with a newer type and considered more efficient is particularly significant. Its extension to the first series aircraft might have seemed relevant, and would probably have prevented the accident. The reasons which led to the maintenance of such cables on the C 160 series first held in both the human factor (underestimation of risk, lack of global view on the issue) and organizational factors, which can be seen as a lack of traceability of technical and logistic actions, a lack of consistency of the measures adopted, and probable deficiencies in the information flow.
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:

Ground accident of an ATR42-300 in Rome

Date & Time: Mar 6, 2003 at 2050 LT
Type of aircraft:
Operator:
Registration:
I-ATRF
Flight Phase:
Survivors:
Yes
Schedule:
Rome - Rimini
MSN:
034
YOM:
1986
Flight number:
MTC403
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
42
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7685
Captain / Total hours on type:
1159.00
Copilot / Total flying hours:
740
Copilot / Total hours on type:
232
Aircraft flight hours:
27472
Aircraft flight cycles:
28492
Circumstances:
Following a normal taxi procedure at Rome-Fiumicino Airport, the crew was at the holding point of runway 25, ready for departure. On board were 42 passengers and a crew of three. Both engines were turning at 70% torque. When the crew released the brakes, the swinging lever of the left main gear failed. The aircraft sank on its belly and stopped. All 45 occupants evacuated safely and there were no injuries. The aircraft was damaged beyond repair.
Probable cause:
Failure of the swinging lever of the left main gear due to the presence of fatigue cracks.
Final Report:

Ground accident of a Dornier DO228-201 in Karachi

Date & Time: Feb 19, 2003
Type of aircraft:
Operator:
Registration:
AP-BGF
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Karachi - Karachi
MSN:
8016
YOM:
1983
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful training flight at Karachi-Quaid-e-Azam Airport, the crew was taxiing to his parking place when control was lost. The aircraft rolled across the apron and eventually collided with a concrete wall. Both pilots escaped uninjured while the aircraft was damaged beyond repair.

Crash of an Airbus A319 in New York

Date & Time: Jan 19, 2003 at 0715 LT
Type of aircraft:
Operator:
Registration:
N313NB
Flight Phase:
Survivors:
Yes
MSN:
1186
YOM:
2000
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Two maintenance technicians where on board Northwest Airlines' Airbus A319 N313NB which was taxied from a maintenance area to Gate 10. When they arrived in the vicinity of gate 10, the mechanic who was steering the plane, activated the parking brake and waited for ground personnel and a jetway operator to arrive. After the ground personnel arrived he released the parking brake. The airplane did not move and he advanced the throttles out of their idle detents "a couple of inches, about halfway." The airplane began to move at a "fairly decent speed," and he realized the throttles were still out of the idle detent position. He pulled the throttle back and applied brakes; however, the airplane did not slow and continued until it struck the concrete support column of the jetway, and the left wing contacted the right side of a Boeing 757-251 (N550NW, parked at gate 9). The nose gear sheared off the Airbus, and the right side of the Boeing sustained a 6-foot long, 2-foot wide gash, just aft of the R1 door. The mechanic estimated that the airplane was about halfway down the parking line when he pulled back the throttles. Initial review of the flight data recorder for the time period surrounding the accident revealed that about 10 seconds after the parking brake was released, the thrust lever angles for both engines were increased to about 17 degrees for about 8 seconds, before they were returned to the idle position. During that time, the engines N1 and N2 speeds increased to about 71, and 85 percent, respectively.
Probable cause:
Maintenance personnel failure to maintain aircraft control as a result of excessive throttle input.

Ground accident of an Embraer ERJ-135LR in Columbus

Date & Time: Jan 18, 2003
Type of aircraft:
Operator:
Registration:
N714BZ
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
145-260
YOM:
2000
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was under maintenance test at Columbus-John Glenn Airport (Port Columbus) and under the control of three technicians. While performing an engine run, the aircraft collided with a hangar and was damaged beyond repair. All three technicians escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
No investigations were conducted by the NTSB on this event.

Ground accident of an Avro RJ85 in Memphis

Date & Time: Oct 15, 2002 at 1224 LT
Type of aircraft:
Operator:
Registration:
N528XJ
Flight Phase:
Survivors:
Yes
MSN:
E2353
YOM:
1999
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following maintenance at Memphis Airport facilities, a crew of two technicians was ferrying the aircraft from the hangar to the main terminal. While approaching the C2 gate, the aircraft could not be stopped in time and collided with the jet bridge. Both occupants escaped with minor injuries while the aircraft was damaged beyond repair.