Premier down KSBN
03-22-2013, 05:57 AM
#51
Gets Weekends Off
Joined APC: Mar 2008
Position: FAA 'Flight Check'
Posts: 13,837
NTSB looking for links.
Spate of Beechcraft Premier Accidents Claims Nine | Aviation International News
Spate of Beechcraft Premier Accidents Claims Nine | Aviation International News
...they are also trying to determine whether there are any links between this accident and two other Premier crashes within a three-week period. Nine people have died in the three recent accidents involving Premiers.
04-05-2013, 08:59 AM
#53
Line Holder
Joined APC: Mar 2008
Posts: 96
NTSB Identification: CEN13FA196
14 CFR Part 91: General Aviation
Accident occurred Sunday, March 17, 2013 in South Bend, IN
Aircraft: Hawker Beechcraft Corporation 390, registration: N26DK
Injuries: 2 Fatal,3 Serious.
This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators either traveled in support of this investigation or conducted a significant amount of investigative work without any travel, and used data obtained from various sources to prepare this aircraft accident report.
On March 17, 2013, at 1623 eastern daylight time, a Hawker Beechcraft model 390 (Premier IA) business jet, N26DK, serial number RB-226, 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.
14 CFR Part 91: General Aviation
Accident occurred Sunday, March 17, 2013 in South Bend, IN
Aircraft: Hawker Beechcraft Corporation 390, registration: N26DK
Injuries: 2 Fatal,3 Serious.
This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators either traveled in support of this investigation or conducted a significant amount of investigative work without any travel, and used data obtained from various sources to prepare this aircraft accident report.
On March 17, 2013, at 1623 eastern daylight time, a Hawker Beechcraft model 390 (Premier IA) business jet, N26DK, serial number RB-226, 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.
04-05-2013, 10:17 AM
#54
Gets Weekends Off
Joined APC: Mar 2008
Position: FAA 'Flight Check'
Posts: 13,837
the pilot declared an emergency because of a lack of engine power, reporting that they were "dead stick" and without any power.
"we've lost all power, and we have no hydraulics."
if the airplane remained controllable, the pilot replied "ah, barely controllable."
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.
04-05-2013, 10:31 AM
#55
Gets Weekends Off
Joined APC: Feb 2012
Position: CRJ FO
Posts: 4,599
Bummer report... Sounds like a bad situation all around. Just out of curiosity, how would you guys of dealt with a similar situation? That seems like a heap of bad happening in a short period of time.
04-05-2013, 10:54 AM
#57
Gets Weekends Off
Joined APC: Feb 2012
Position: CRJ FO
Posts: 4,599
Well if the preliminary report is saying that pilot lost his hydraulics and electrics... It sounds like a bad situation that close to the ground. If that is indeed what happened, how would you of handled it?
Thread
Thread Starter
Forum
Replies
Last Post
