Ground accident of a McDonnell Douglas MD-81 in Newark

Date & Time: Jun 14, 2000 at 1700 LT
Type of aircraft:
Operator:
Registration:
N16884
Flight Phase:
Survivors:
Yes
Schedule:
Newark - Detroit
MSN:
48074
YOM:
1981
Flight number:
CO481
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
45834
Aircraft flight cycles:
36189
Circumstances:
The aircraft was parked at gate C115 awaiting for passengers on a flight (service CO481) from Newark to Detroit-Wayne County Airport. In unclear circumstances, a pilot attempted to make an engine run test while six employees were cleaning the cabin. The aircraft moved forward and collided with the main terminal, suffering major structural damages. There were no injuries among the seven occupants while the aircraft was damaged beyond repair.
Probable cause:
No investigations were conducted by NTSB on this event.

Crash of a Dassault Falcon 20E in Peterborough

Date & Time: Jun 13, 2000 at 2250 LT
Type of aircraft:
Operator:
Registration:
N184GA
Flight Type:
Survivors:
Yes
Schedule:
Louisville – Marion – Detroit – Peterborough
MSN:
266
YOM:
1972
Flight number:
GAE184
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11800
Captain / Total hours on type:
9400.00
Copilot / Total flying hours:
2300
Copilot / Total hours on type:
150
Aircraft flight hours:
15798
Circumstances:
The Dassault-Breguet Falcon 20E aircraft was on an unscheduled charter cargo flight from Detroit Willow Run, Michigan, USA, to Peterborough, Ontario. The flight was being conducted at night and under instrument flight rules in instrument meteorological conditions. Nearing the destination, the flight crew received a clearance to conduct a non-directional beacon runway 09 approach at Peterborough Airport. The flight crew did not acquire the runway environment during this approach and conducted a missed approach procedure. They obtained another clearance for the same approach from Toronto Area Control Centre. During this approach, the flight crew acquired the runway environment and manoeuvred the aircraft for landing on runway 09. The aircraft touched down near the runway midpoint, and the captain, who was the pilot flying, elected to abort the landing. The captain then conducted a left visual circuit to attempt another landing. As the aircraft was turning onto the final leg, the approach became unstabilized, and the flight crew elected to overshoot; however, the aircraft pitched nose-down, banked left, and struck terrain. As it travelled 400 feet through a ploughed farm field, the aircraft struck a tree line and came to rest about 2000 feet before the threshold of runway 09, facing the opposite direction. The aircraft was substantially damaged. No serious injuries occurred.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The captain's attempt to continue the landing during the second approach was contrary to company standard operating procedures and Federal Aviation Regulations, in that the approach was unstable and the aircraft was not in a position to land safely.
2. Following the aborted landing, the flight crew proceeded to conduct a circling approach to runway 09, rather than the missed approach procedure as briefed.
3. The pilot lost situational awareness during the overshoot after the third failed attempt to land, likely when he was subjected to somatogravic illusion.
4. Breakdown in crew coordination after the aborted landing, lack of planning and briefing for the subsequent approach, operating in a dark, instrument meteorological conditions environment with limited visual cues, and inadequate monitoring of flight instruments contributed to the loss of situational awareness.
Final Report:

Crash of a Pilatus PC-6/C1-H2 Turbo Porter in Bremgarten

Date & Time: Jun 13, 2000 at 1330 LT
Registration:
D-FDHM
Flight Type:
Survivors:
Yes
Schedule:
Ailertchen – Bremgarten
MSN:
688
YOM:
1969
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Upon landing, the single engine aircraft went out of control, bounced several time and veered off runway before colliding with trees. All three occupants were injured and the aircraft wa damaged beyond repair. It is believed that the loss of control occurred while the pilot-in-command was initiating a go-around procedure.

Crash of a Cessna 402B in Palma de Mallorca

Date & Time: Jun 11, 2000
Type of aircraft:
Operator:
Registration:
EC-EPK
Survivors:
Yes
MSN:
402B-1036
YOM:
1975
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the last segment, while completing the flare, the twin engine aircraft landed hard. Upon impact, the undercarriage were torn off and the aircraft slid on its belly for few dozen metres before coming to rest. There were no casualties but the aircraft was damaged beyond repair.

Crash of an Antonov AN-32B in Lima-25

Date & Time: Jun 7, 2000
Type of aircraft:
Registration:
UR-48054
Flight Type:
Survivors:
Yes
Schedule:
Khartoum - Lima-25
MSN:
28 04
YOM:
1991
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
2799
Aircraft flight cycles:
1985
Circumstances:
Damaged beyond repair at Lima-25 Airstrip when a crowd of some 300 local residents ran out onto the runway as the aircraft touched down. The captain ground looped the aircraft to the right to avoid crashing into them. The aircraft colliding with obstacles as a result. There were no casualties.

Crash of a Fokker F27 Friendship 600 in Accra: 7 killed

Date & Time: Jun 5, 2000 at 1135 LT
Type of aircraft:
Operator:
Registration:
G524
Survivors:
Yes
Schedule:
Tamale - Accra
MSN:
10535
YOM:
1976
Flight number:
GH200
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
44
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The aircraft was completing a schedule service (flight GH200) from Tamale to Accra on behalf of the Ghana Air Force. On final approach to Accra-kotoka Airport, the crew encountered poor weather conditions with limited visibility due to heavy rain falls. In a nose down attitude, the aircraft landed hard on runway 21, nose first. Upon impact, the aircraft broke in two and came to rest. Seven passengers were killed while several others were injured, some seriously.

Crash of a Cessna 401 in La Romana: 1 killed

Date & Time: Jun 2, 2000 at 1240 LT
Type of aircraft:
Operator:
Registration:
HI-696CT
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
La Romana - La Romana
MSN:
401-0021
YOM:
1967
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
On June 2, 2000, about 1240 Atlantic standard time, a Cessna 401, Dominican Republic registration HI-696CT, registered to and operated by Air Century, crashed shortly after takeoff from La Romana International Airport, La Romana, Dominican Republic, while on an instructional flight. Visual meteorological conditions prevailed at the time and no flight plan was filed. The aircraft was destroyed. The commercial-rated pilot received fatal injuries. The commercial-rated second pilot received serious injuries. The flight was originating at the time of the accident. Civil aviation authorities stated that the flight was an instructional flight. Shortly after takeoff on runway 12, the pilot simulated the failure of the left engine. Control of the aircraft was lost and the aircraft crashed 350 meters from the runway. Examination of the aircraft and engines showed no mechanical anomalies.

Crash of a Piper PA-46-310P Malibu in Hawthorne: 3 killed

Date & Time: May 28, 2000 at 1159 LT
Operator:
Registration:
N567YV
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Hawthorne – Las Vegas
MSN:
46-8408016
YOM:
1984
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
2550
Captain / Total hours on type:
1250.00
Circumstances:
The aircraft collided with the ground in a steep nose down descent angle while maneuvering to return to the runway during the takeoff initial climb from the airport. Pilot and mechanic witnesses on the airport described the engine sounds during the takeoff as abnormal. The takeoff ground roll was over 3,000 feet in length, and the airplane's climb out angle was much shallower than usual. Two other witnesses said the engine sounded "like a radial engine," and both believed that the power output was lower than normal. One mechanic witness said the engine was surging and not developing full power; he believed the symptoms could be associated with a fuel feed problem, a turbocharger surge, or an excessively lean running condition. The ground witnesses located near the impact site said the airplane began a steep left turn between 1/4- and 1/2-mile from the runway's end at a lower than normal altitude. The bank angle was estimated by the witnesses as 45 degrees or greater. The turn continued until the nose suddenly dropped and the airplane entered a spiraling descent to ground impact. The majority of these witnesses stated that they heard "sputtering" or "popping" noises coming from the airplane. Engineering personnel from the manufacturer developed a performance profile for a normal takeoff and climb under the ambient conditions of the accident and at gross weight. The profile was compared to the actual aircraft performance derived from recorded radar data and the witness observations. The ground roll was 1,300 feet longer than it should have been, and the speed/acceleration and climb performance were consistently well below the profile's predictions. Based on the radar data and factoring in the winds, the airplane's estimated indicated airspeed during the final turn was 82 knots; the stall speed at 45 degrees of bank is 82 knots and it increases linearly to 96 knots at 60 degrees of bank. No evidence was found that the pilot flew the airplane from December until the date of the accident. The airplane sat outside during the rainy season with only 10 gallons of fuel in each tank. Comparison of the time the fueling began and the communications transcripts disclosed that the pilot had 17 minutes 41 seconds to refuel the airplane with 120 gallons, reboard the airplane, and start the engine for taxi; the maximum nozzle discharge flow rate of the pump he used is 24 gallons per minute. Review of the communications transcripts found that a time interval of 3 minutes 35 seconds elapsed from the time the pilot asked for a taxi clearance from the fuel facility until he reported ready for takeoff following a taxi distance of at least 2,000 feet. During the 8 seconds following the pilot's acknowledgment of his takeoff clearance, he and the local controller carried on a non pertinent personal exchange. The aircraft was almost completely consumed in the post crash fire; however, extensive investigation of the remains failed to identify a preimpact mechanical malfunction or failure in the engine or airframe systems. The pistons, cylinder interiors, and spark plugs from all six cylinders were clean without combustion deposits. The cockpit fuel selector lever, the intermediate linkages, and the valve itself were found in the OFF position; however, an engineering analysis established that insufficient fuel was available in the lines forward of the selector to start, taxi, and perform a takeoff with the selector in the OFF position.
Probable cause:
A partial loss of power due to water contamination in the fuel system and the pilot's inadequate preflight inspection, which failed to detect the water. The pilot's failure to perform an engine run-up before takeoff is also causal. Additional causes are the pilot's failure to maintain an adequate airspeed margin for the bank angle he initiated during the attempted return to runway maneuver and the resultant encounter with a stall/spin. Factors in the accident include the pilot's failure to detect the power deficiency early in the takeoff roll due to his diverted attention by a non pertinent personal conversation with the local controller, and, the lack of suitable forced landing sites in the takeoff flight path.
Final Report:

Crash of a Short 330-200 in Paris: 1 killed

Date & Time: May 25, 2000 at 0252 LT
Type of aircraft:
Operator:
Registration:
G-SSWN
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Paris - Luton
MSN:
3064
YOM:
1981
Flight number:
SSW200
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2240
Captain / Total hours on type:
1005.00
Copilot / Total flying hours:
4370
Copilot / Total hours on type:
14
Aircraft flight hours:
15215
Aircraft flight cycles:
19504
Circumstances:
The Short was departing Paris-Roissy-CDG Airport on a cargo service to Luton with two pilots on board. The crew were cleared to depart cargo stand N51 and proceed to runway 27 at 02:38. Around the same time Air Liberté Flight 8807 (an MD-83, F-GHED) also taxied to runway 27 for a flight to Madrid. At 02:44 the Charles de Gaulle ground controller asked Streamline 200 if they wished to enter runway 27 at an intermediate taxiway; the crew asked for and were granted to enter Taxiway 16. At 02:50:49 the tower controller cleared the MD-83 for takeoff: "Liberté 8807, autorisé au décollage 27, 230°, 10 à 15 kts.". The controller then immediately told the Shorts to line up and wait: "Stream Line two hundred line up runway 27 and wait, number two". As the MD-83 was travelling down the runway, the Shorts started to taxi onto the runway. At a speed of about 155 knots the left wing of MD-83 slashed through the cockpit of the Shorts plane; the MD-83 abandoned takeoff.
Probable cause:
The following findings were identified:
- Firstly, by the LOC controller’s erroneous perception of the position of the aircraft, this being reinforced by the context and the working methods, which led him to clear the Shorts to line up,
- Secondly, by the inadequacy of systematic verification procedures in ATC which made it impossible for the error to be corrected,
- Finally, by the Shorts’ crew not dispelling any doubts they had as to the position of the 'number one' aircraft before entering the runway.
Contributory factors include:
- Light pollution in the area of runway 27, which made a direct view difficult for the LOC controller,
- Difficulty for the LOC controller in accessing radar information: the ASTRE image was difficult to read and the AVISO image not displayed at his control position,
- The use of two languages for radio communications, which meant that the Shorts crew were not conscious that the MD 83 was going to take off,
- The angle between access taxiway 16 and the runway which made it impossible for the Shorts crew to perform a visual check before entering the runway,
- The lack of coordination between the SOL and LOC controllers when managing the Shorts, exacerbated by the presence of a third party whose role was not defined,
- A feedback system which was recent and still underdeveloped.
Final Report:

Crash of a BAe Jetstream 31 in Wilkes-Barre: 19 killed

Date & Time: May 21, 2000 at 1148 LT
Type of aircraft:
Operator:
Registration:
N16EJ
Survivors:
No
Schedule:
Atlantic City – Wilkes-Barre
MSN:
834
YOM:
1988
Crew on board:
2
Crew fatalities:
Pax on board:
17
Pax fatalities:
Other fatalities:
Total fatalities:
19
Captain / Total flying hours:
8500
Captain / Total hours on type:
1874.00
Copilot / Total flying hours:
1282
Copilot / Total hours on type:
742
Aircraft flight hours:
13972
Aircraft flight cycles:
18503
Circumstances:
On May 21, 2000, about 1128 eastern daylight time (EDT), a British Aerospace Jetstream 3101, N16EJ, operated by East Coast Aviation Services (doing business as Executive Airlines) crashed
about 11 miles south of Wilkes-Barre/Scranton International Airport (AVP), Wilkes-Barre, Pennsylvania. The airplane was destroyed by impact and a post crash fire, and 17 passengers and two flight crewmembers were killed. The flight was being conducted under 14 Code of Federal Regulations (CFR) Part 135 as an on-demand charter flight for Caesar’s Palace Casino in Atlantic City, New Jersey. An instrument flight rules (IFR) flight plan had been filed for the flight from Atlantic City International Airport (ACY) to AVP. The captain checked in for duty about 0800 at Republic Airport (FRG) in Farmingdale, New York, on the day of the accident. The airplane was originally scheduled to depart FRG at 0900 for ACY and to remain in ACY until 1900, when it was scheduled to return to FRG. While the pilots were conducting preflight inspections, they received a telephone call from Executive Airlines’ owner and chief executive officer (CEO) advising them that they had been assigned an additional flight from ACY to AVP with a return flight to ACY later in the day, instead of the scheduled break in ACY. Fuel records at FRG indicated that 90 gallons of fuel were added to the accident airplane’s tanks before departure to ACY. According to Federal Aviation Administration (FAA) air traffic control (ATC) records, the flight departed at 0921 (with 12 passengers on board) and arrived in ACY at 0949. According to passenger statements, the captain was the pilot flying from FRG to ACY. After arrival in ACY, the flight crew checked the weather for AVP and filed an IFR flight plan. Fuel facility records at ACY indicated that no additional fuel was added. The accident flight to AVP, which departed ACY about 1030, had been chartered by Caesar’s Palace. According to ATC records, the flight to AVP was never cleared to fly above 5,000 feet mean sea level (msl). According to ATC transcripts, the pilots first contacted AVP approach controllers at 1057 and were vectored for an instrument landing system (ILS) approach to runway 4. The flight was cleared for approach at 1102:07, and the approach controller advised the pilots that they were 5 nautical miles (nm) from Crystal Lake, which is the initial approach fix (IAF) for the ILS approach to runway 4. The pilots were told to maintain 4,000 feet until established on the localizer. At 1104:16, the approach controller advised that a “previous landing…aircraft picked up the airport at minimums [decision altitude].” The pilots were instructed to contact the AVP local (tower) controller at 1105:09, which they did 3 seconds later. The airplane then descended to about 2,200 feet, flew level at 2,200 feet for about 20 seconds, and began to climb again about 2.2 nm from the runway threshold when a missed approach was executed (see the Airplane Performance section for more information). At 1107:26 the captain reported executing the missed approach but provided no explanation to air traffic controllers. The tower controller informed the North Radar approach controllers of the missed approach and then instructed the accident flight crew to fly runway heading, climb to 4,000 feet, and contact approach control on frequency 124.5 (the procedure published on the approach chart). The pilots reestablished contact with the approach controllers at 1108:04 as they climbed through 3,500 feet to 4,000 feet and requested another ILS approach to runway 4. The flight was vectored for another ILS approach, and at 1110:07 the approach controller advised the pilots of traffic 2 nm miles away at 5,000 feet. The captain responded that they were in the clouds. At 1014:38, the controller directed the pilots to reduce speed to follow a Cessna 172 on approach to the airport, and the captain responded, “ok we’re slowing.” The flight was cleared for a second approach at 1120:45 and advised to maintain 4,000 feet until the airplane was established on the localizer. At 1123:49 the captain transmitted, “for uh one six echo juliet we’d like to declare an emergency.” At 1123:53, the approach controller asked the nature of the problem, and the captain responded, “engine failure.” The approach controller acknowledged the information, informed the pilots that the airplane appeared to be south of the localizer (off course to the right), and asked if they wanted a vector back to the localizer course. The flight crew accepted, and at 1124:10 the controller directed a left turn to heading 010, which the captain acknowledged. At 1124:33, the controller asked for verification that the airplane was turning left. The captain responded, “we’re trying six echo juliet.” At 1124:38, the controller asked if a right turn would be better. The captain asked the controller to “stand by.” At 1125:07, the controller advised the pilots that the minimum vectoring altitude (MVA) in the area was 3,300 feet. At 1125:12, the captain transmitted, “standby for six echo juliet tell them we lost both engines for six echo juliet.” At that time, ATC radar data indicated that the airplane was descending through 3,000 feet. The controller immediately issued the weather conditions in the vicinity of the airport and informed the flight crew about the location of nearby highways. At 1126:17, the captain asked, “how’s the altitude look for where we’re at.” The controller responded that he was not showing an altitude readout from the airplane and issued the visibility (2.5 miles) and altimeter setting. At 1126:43, the captain transmitted, “just give us a vector back to the airport please.” The controller cleared the accident flight to fly heading 340, advised the flight crew that radar contact was lost, and asked the pilots to verify their altitude. The captain responded that they were “level at 2,000.” At 1126:54, the controller again advised the flight crew of the 3,300-foot MVA and suggested a 330° heading to bring the airplane back to the localizer. At 1127:14 the controller asked, “do you have any engines,” and the captain responded that they appeared to have gotten back “the left engine now.” At 1127:23, the controller informed the pilots that he saw them on radar at 2,000 feet and that there was a ridgeline between them and the airport. The captain responded, “that’s us” and “we’re at 2,000 feet over the trees.” The controller instructed the pilots to fly a 360° heading and advised them of high antennas about 2 nm west of their position. At 1127:46, the captain transmitted, “we’re losing both engines.” Two seconds later the controller advised that the Pennsylvania Turnpike was right below the airplane and instructed the flight crew to “let me know if you can get your engines back.” There was no further radio contact with the accident airplane. The ATC supervisor initiated emergency notification procedures. A Pennsylvania State Police helicopter located the wreckage about 1236, and emergency rescue units arrived at the accident site about 1306. The accident occurred in daylight instrument meteorological conditions (IMC). The location of the accident was 41° 9 minutes, 23 seconds north latitude, 75° 45 minutes, 53 seconds west longitude, about 11 miles south of the airport at an elevation of 1,755 feet msl.
Probable cause:
The flight crew’s failure to ensure an adequate fuel supply for the flight, which led to the stoppage of the right engine due to fuel exhaustion and the intermittent stoppage of the left engine due to fuel starvation. Contributing to the accident were the flight crew's failure to monitor the airplane’s fuel state and the flight crew's failure to maintain directional control after the initial engine stoppage.
Final Report: