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
Flight Type:
Survivors:
Yes
Schedule:
Tulsa - South Bend
MSN:
RB-226
YOM:
2008
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Aircraft collided with three residential structures and terrain following an aborted landing attempt on runway 9R located at the South Bend Regional Airport (KSBN), South Bend, Indiana. The private pilot and pilot-rated-passenger occupying the cockpit seats were fatally injured. An additional two passengers and one individual on the ground sustained serious injuries. The airplane was registered to 7700 Enterprises of Montana, LLC and operated by Digicut Systems of Tulsa, Oklahoma, under the provisions of 14 Code of Federal Regulations Part 91 while on an instrument flight plan. Day visual meteorological conditions prevailed for the business flight that departed Richard Lloyd Jones Jr. Airport (KRVS), Tulsa, Oklahoma, at 1358 central daylight time. According to preliminary air traffic control information, at 1610:31, the accident pilot established radio communications with South Bend Approach Control while at 11,000 feet mean sea level (msl). The air traffic controller cleared the flight direct to KNUTE intersection and told the pilot to expect a visual approach to runway 9R. At 1611:44, the flight was cleared to descend to 10,000 feet msl. At 1613:06, the flight was cleared to 3,000 feet msl. At 1615:00, the approach controller told the pilot to make a 5-degree left turn to align with runway 9R and asked the pilot to report when he had the airport in sight. At 1615:07, the pilot declared an emergency because of a lack of engine power, reporting that they were "dead stick" and without any power. About 23 seconds later, at 1615:30, the pilot transmitted "we've lost all power, and we have no hydraulics." When the controller asked if the airplane remained controllable, the pilot replied "ah, barely controllable." The controller advised that all runways at KSBN were available for landing and issued the current winds, which were 130-degrees at 10 knots. At 1615:22, the pilot transmitted that the airplane’s navigational systems were inoperative and requested a radar vector toward the airport. The controller replied that the airport was 9 miles directly ahead of the airplane’s current position. At 1616:12, the controller told the pilot to turn 10-degrees left to intersect runway 9R. At 1616:15, the pilot replied "26DK, turning left." No additional voice communications were received from the accident airplane. The approach controller continued to transmit radar vectors toward runway 9R without any response from the accident pilot. At 1618:58, the approach controller told the accident airplane to go-around because the main landing gear was not extended. (The tower controller had informed the approach controller that only the nose landing gear was extended) The accident airplane was then observed to climb and enter a right traffic pattern for runway 9R. The airplane made another landing approach to runway 9R with only the nose landing gear extended. Several 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 descent into a nearby residential community.

Crash of a Cessna 303 Crusader in South Bend: 5 killed

Date & Time: Nov 13, 2006 at 2003 LT
Type of aircraft:
Registration:
N611BB
Flight Phase:
Flight Type:
Survivors:
No
Site:
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 aircraft was carrying 5 people (4 businessmen and a pilot) from South Bend, Indiana, to Ankeny, Iowa. Few minutes after takeoff, while flying at 5,700 feet, the aircraft spiraled down to about 1,200 feet and crash in a vertically position. Nobody survived.

Crash of a Canadair CL-600 Challenger in Montrose: 3 killed

Date & Time: Nov 28, 2004 at 0955 LT
Type of aircraft:
Registration:
N873G
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Montrose-South Bend
MSN:
3009
YOM:
1983
Flight number:
GLB73
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:
Aircraft stalled on takeoff and hit a fence before crashing at the end of runway 31. Both pilots and a passenger were killed. NTSB concluded that crew forgot to deice before departure.

Crash of a Pilatus PC-12 in Missouri: 2 killed

Date & Time: Sep 14, 2002 at 1555 LT
Type of aircraft:
Registration:
N451ES
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Lake Ozark-South Bend
MSN:
0425
YOM:
2001
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1645
Captain / Total hours on type:
58.00
Aircraft flight hours:
505
Aircraft flight cycles:
470

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

Date & Time: Nov 11, 1999 at 2020 LT
Operator:
Registration:
N869
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Chicago-South Bend
MSN:
BB-0174
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

Crash of a Cessna 401 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
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

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
Site:
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: