Zone

Crash of a Raytheon 390 Premier I in South Bend: 2 killed

Date & Time: Mar 17, 2013 at 1623 LT
Type of aircraft:
Operator:
Registration:
N26DK
Survivors:
Yes
Site:
Schedule:
Tulsa - South Bend
MSN:
RB-226
YOM:
2008
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
613
Captain / Total hours on type:
171.00
Copilot / Total flying hours:
1877
Copilot / Total hours on type:
0
Aircraft flight hours:
457
Circumstances:
According to the cockpit voice recorder (CVR), during cruise flight, the unqualified pilot-rated passenger was manipulating the aircraft controls, including the engine controls, under the supervision and direction of the private pilot. After receiving a descent clearance to 3,000 feet mean sea level (msl), the pilot told the pilot-rated passenger to reduce engine power to maintain a target airspeed. The cockpit area microphone subsequently recorded the sound of both engines spooling down. The pilot recognized that the pilot-rated passenger had shutdown both engines after he retarded the engine throttles past the flight idle stops into the fuel cutoff position. Specifically, the pilot stated "you went back behind the stops and we lost power." According to air traffic control (ATC) radar track data, at the time of the dual engine shutdown, the airplane was located about 18 miles southwest of the destination airport and was descending through 6,700 feet msl. The pilot reported to the controller that the airplane had experienced a dual loss of engine power, declared an emergency, and requested radar vectors to the destination airport. As the flight approached the destination airport, the cockpit area microphone recorded a sound similar to an engine starter spooling up; however, engine power was not restored during the attempted restart. A review of the remaining CVR audio did not reveal any evidence of another attempt to restart an engine. The CVR stopped recording while the airplane was still airborne, with both engines still inoperative, while on an extended base leg to the runway. Subsequently, the controller told the pilot to go-around because the main landing gear was not extended. The accident airplane was then observed to climb and enter a right traffic pattern to make another landing approach. Witness accounts indicated that only the nose landing gear was extended during the second landing approach. The witnesses observed the airplane bounce several times on the runway before it ultimately entered a climbing right turn. The airplane was then observed to enter a nose low, rolling descent into a nearby residential community. The postaccident examinations and testing did not reveal any anomalies or failures that would have precluded normal operation of the airplane. Although the CVR did not record a successful engine restart, the pilot was able to initiate a go-around during the initial landing attempt, which implies that he was able to restart at least one engine during the initial approach. The investigation subsequently determined that only the left engine was operating at impact. Following an engine start, procedures require that the respective generator be reset to reestablish electrical power to the Essential Bus. If the Essential Bus had been restored, all aircraft systems would have operated normally. However, the battery toggle switch was observed in the Standby position at the accident site, which would have prevented the Essential Bus from receiving power regardless of whether the generator had been reset. As such, the airplane was likely operating on the Standby Bus, which would preclude the normal extension of the landing gear. However, the investigation determined that the landing gear alternate extension handle was partially extended. The observed position of the handle would have precluded the main landing gear from extending (only the nose landing gear would extend). The investigation determined that it is likely the pilot did not fully extend the handle to obtain a full landing gear deployment. Had he fully extended the landing gear, a successful single-engine landing could have been accomplished. In conclusion, the private pilot's decision to allow the unqualified pilot-rated passenger to manipulate the airplane controls directly resulted in the inadvertent dual engine shutdown during cruise descent. Additionally, the pilot's inadequate response to the emergency, including his failure to adhere to procedures, resulted in his inability to fully restore airplane systems and ultimately resulted in a loss of airplane control.
Probable cause:
The private pilot's inadequate response to the dual engine shutdown during cruise descent, including his failure to adhere to procedures, which ultimately resulted in his failure to
maintain airplane control during a single-engine go-around. An additional cause was the pilot's decision to allow the unqualified pilot-rated passenger to manipulate the airplane controls, which directly resulted in the inadvertent dual engine shutdown.
Final Report:

Crash of a Cessna T303 Crusader in Mill Creek: 5 killed

Date & Time: Nov 13, 2006 at 2003 LT
Type of aircraft:
Registration:
N611BB
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
South Bend - Ankeny
MSN:
303-00145
YOM:
1982
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
504
Aircraft flight hours:
4577
Circumstances:
The pilot departed his home airport at 0502 and landed at another airport where he picked up employees of a marketing company to fly them to an out of state meeting. The accident occurred at 2003 shortly after taking off on the return trip to fly the employees back home. Shortly before departure a fourth passenger was added to the flight after his commercial flight was cancelled. A person who worked for the fixed base operator at the departure airport stated the pilot looked tired or just ready to go home. The pilot received his clearance for the IFR flight prior to takeoff. The pilot misread the clearance back to the controlled and was corrected. Radar data showed the pilot initially flew the assigned south-southwest heading prior to the airplane turning right to a westerly heading. The controller queried the pilot and issued a heading to intercept the VOR. The pilot corrected the heading and shortly thereafter the airplane once again began a right turn back toward the west. The airplane continued to climb throughout the heading changes. Radar data showed the airplane then began another left turn during which time it entered a spiraling rapid descent. According to weather data, the airplane was in instrument meteorological conditions when this occurred. The airplane impacted the terrain in an open cornfield. Weight and balance calculations indicate the airplane was at least 383 pounds over gross weight. Post accident inspection of the airplane and engines did not reveal any preexisting failure/malfunction.
Probable cause:
The pilot became spatially disoriented and as a result failed to maintain control of the airplane. Factors associated with the accident were the instrument meteorological conditions aloft and the pilot being fatigued.
Final Report:

Crash of a Canadair CL-601-1A Challenger in Montrose: 3 killed

Date & Time: Nov 28, 2004 at 0955 LT
Type of aircraft:
Operator:
Registration:
N873G
Flight Phase:
Survivors:
Yes
Schedule:
Montrose – South Bend
MSN:
3009
YOM:
1983
Flight number:
HPJ073
Crew on board:
3
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
12396
Captain / Total hours on type:
913.00
Copilot / Total flying hours:
1586
Copilot / Total hours on type:
30
Aircraft flight hours:
14317
Aircraft flight cycles:
8910
Circumstances:
On November 28, 2004, about 0958 mountain standard time, a Canadair, Ltd., CL-600-2A12, N873G, registered to Hop-a-Jet, Inc., and operated by Air Castle Corporation dba Global Aviation as Glo-Air flight 73, collided with the ground during takeoff at Montrose Regional Airport (MTJ), Montrose, Colorado. The on-demand charter flight was operated under the provisions of 14 Code of Federal Regulations (CFR) Part 135 on an instrument flight rules (IFR) flight plan. Instrument meteorological conditions prevailed, and snow was falling. Of the six occupants on board, the captain, the flight attendant, and one passenger were killed, and the first officer and two passengers were seriously injured. The airplane was destroyed by impact forces and post crash fire. The flight was en route to South Bend Regional Airport (SBN), South Bend, Indiana.
Probable cause:
The flight crew's failure to ensure that the airplane’s wings were free of ice or snow contamination that accumulated while the airplane was on the ground, which resulted in an attempted takeoff with upper wing contamination that induced the subsequent stall and collision with the ground. A factor contributing to the accident was the pilots’ lack of experience flying during winter weather conditions.
Final Report:

Crash of a Beechcraft 200 Super King Air in Chicago: 3 killed

Date & Time: Nov 11, 1999 at 2020 LT
Operator:
Registration:
N869
Flight Phase:
Survivors:
No
Schedule:
Chicago - South Bend
MSN:
BB-174
YOM:
1976
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
18000
Captain / Total hours on type:
4536.00
Aircraft flight hours:
8636
Circumstances:
Shortly after being cleared for takeoff on runway 18 (3,899 feet by 150 feet, dry concrete) at Merrill C. Meigs Field, Chicago, Illinois, the airplane impacted into Lake Michigan, approximately 300 feet south of the end of the runway. The tower controller said that at the 3/4 field point, the airplane had not rotated. 'All I can see are lights [from the airplane]. At the point where he would have been at the end of the runway, [I] lost the lights.' A witness on the airport said that when the airplane went by, it 'didn't sound like most King Airs do at that point.' There was a pulsating sound, but it was not heavy. The witness said that the airplane was 'bouncing up and down on the [gear] struts, and wasn't coming off the ground.' NTSB Materials examination of the pilot's control yoke showed that there were small distortions in the holes of the column and the rod where the control lock would be inserted. A small crack was observed around 1/4 of the control lock rod hole. The control lock was a substitute for the original airplane equipment. The examination of the control lock showed 'several shiny scratches ... parallel to the length of the pin.' A small deformation was observed near the top of the pin part of the control lock. The company flight department's third pilot said that when they flew the airplane, they always placed the control lock in the pilot's side cockpit wall pocket, along with a car key and a remote hanger door opener. The car key and the door opener were found in the wall pocket during the on-scene investigation. The control lock was
recovered from the lake, 7 days later.
Probable cause:
On ground collision with the lake for undetermined reasons.
Final Report:

Crash of a Cessna 401B in Caldwell

Date & Time: Oct 2, 1999 at 0751 LT
Type of aircraft:
Registration:
N88VA
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Caldwell - South Bend
MSN:
401-0118
YOM:
1968
Crew on board:
1
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
738
Captain / Total hours on type:
118.00
Aircraft flight hours:
4686
Circumstances:
The pilot aborted the takeoff run after the airspeed indication rose to about 80 miles per hour, but would not go any higher. He could not stop the airplane, before it went off the end of the runway, over a berm, and into a drainage ravine. When the airplane was pulled out of the ravine, both pitot covers were still in place, around the pitot tubes. The runway was 4,553 feet long, calculated takeoff distance was about 2,525 feet, and calculated accelerate-stop distance was approximately 2,950 feet. Tire skid marks started around 3,600 feet from the approach end of the runway, and led to the wreckage. About a year earlier, another airplane was destroyed when it ran into the same ravine, which was located about 200 feet from the end of the runway.
Probable cause:
The pilot's inadequate preflight, which resulted in an attempted takeoff with the pitot covers installed. An additional cause was the pilot's delayed decision to abort the takeoff, while factors included the misleading airspeed indications, and the proximity of the drainage ravine to the end of the runway.
Final Report:

Crash of a Cessna 340A in Aspen: 4 killed

Date & Time: Feb 15, 1983 at 0813 LT
Type of aircraft:
Registration:
N33340
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Aspen – South Bend
MSN:
340A-0529
YOM:
1978
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
3193
Aircraft flight hours:
724
Circumstances:
Prior to departure the flight was given an IFR clearance which began at Herls intersection (16 miles NNE) and to cross Herls at or above 16,000 feet msl. Departure airport field elevation is 7,793 feet. Flights are required to proceed VFR to the initial fix of the IFR clearance. After takeoff the aircraft was observed heading northeast toward the mountains. Aircraft departing Aspen usually fly a northern heading, then turn northeast after clearing the mountains. Witnesses stated that the weather was good in the valley north of the airport, but the mountain tops east of the airport were obscured by low clouds. The aircraft crashed 3 1/2 miles northeast of the airport at the 9,000 feet level of an 11,000 feet mountain. The last time the pilot had flown into Aspen was in 1980. All four occupants were killed.
Probable cause:
Occurrence #1: in flight encounter with weather
Phase of operation: climb - to cruise
Findings
1. (c) preflight planning/preparation - inadequate - pilot in command
2. (c) VFR procedures - not followed - pilot in command
3. (f) lack of familiarity with geographic area - pilot in command
4. (f) weather condition - clouds
5. (f) weather condition - obscuration
6. (c) VFR flight into IMC - continued - pilot in command
----------
Occurrence #2: in flight collision with terrain/water
Phase of operation: climb - to cruise
Findings
7. (f) terrain condition - high terrain
8. (f) terrain condition - mountainous/hilly
9. (f) terrain condition - rising
Final Report:

Crash of a Beechcraft E18S near Argos: 1 killed

Date & Time: Apr 1, 1975 at 0130 LT
Type of aircraft:
Operator:
Registration:
N140J
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Indianapolis - South Bend
MSN:
BA-334
YOM:
1958
Location:
Crew on board:
1
Crew fatalities:
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
7000
Captain / Total hours on type:
5000.00
Circumstances:
While in cruising altitude on a cargo flight from Indianapolis to South Bend, the pilot contacted ATC and reported a fire in the cabin. He reduced his altitude when few minutes later, the twin engine airplane struck tree tops and crashed in flames in a wooded area located in the region of Argos. The airplane was destroyed and the pilot, sole on board, was killed.
Probable cause:
In-flight fire for undetermined reason. The following findings were reported:
- Fire in cabin, cockpit, baggage compartment,
- High obstructions.
Final Report:

Crash of a Douglas DC-3-201F in Chicago

Date & Time: Jul 2, 1946 at 0910 LT
Type of aircraft:
Operator:
Registration:
NC28383
Flight Phase:
Survivors:
Yes
Schedule:
Chicago – South Bend
MSN:
4091
YOM:
1941
Flight number:
TW456
Crew on board:
3
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2559
Captain / Total hours on type:
2261.00
Copilot / Total flying hours:
2939
Copilot / Total hours on type:
381
Aircraft flight hours:
14043
Circumstances:
After takeoff, while climbing to a height of some 600 feet, the left engine failed. The crew informed ATC about the situation and obtained the permission to return for an emergency landing. While trying to restart the left engine, the right engine failed as well. The aircraft stalled and crashed on a railway road located few hundred yards from the runway threshold. While the aircraft was damaged beyond repair, all 21 occupants were evacuated with minor injuries.
Probable cause:
The probable cause of this accident was the complete loss of power in both engines due to fuel starvation necessitating an emergency landing in an unfavorable area. The cause for fuel starvation of the engines has not been determined.
Final Report:

Crash of a Stearman C-3MB in Fort Wayne: 1 killed

Date & Time: Apr 21, 1932
Type of aircraft:
Operator:
Registration:
NC6412
Flight Type:
Survivors:
No
Schedule:
South Bend – Fort Wayne
MSN:
162
YOM:
1928
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
On final approach to Fort Wayne Airport, at an altitude of 300 feet, the airplane stalled and crashed short of runway. The pilot, sole on board, was killed.