code

OK

Crash of an IAI 1124 Westwind in Sundance: 2 killed

Date & Time: Mar 18, 2019 at 1537 LT
Type of aircraft:
Registration:
N4MH
Flight Type:
Survivors:
No
Schedule:
Panama City - Sundance
MSN:
232
YOM:
1978
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The aircraft impacted terrain near the east side of runway 18 at Sundance Airport (HSD), Yukon, Oklahoma. As the airplane approached the approach end of runway 18, it began to climb, rolled left, and became inverted before impacting terrain. The airplane was destroyed. Both pilots sustained fatal injuries. The airplane was registered to and operated by Sundance Airport FBO LLC under Title 14 Code of Federal Regulations Part 91. The flight was operating on an instrument rules flight plan. Visual meteorological conditions prevailed at the time of the accident. The flight departed from Northwest Florida Beaches International Airport (ECP), Panama City, Florida and was destined to HSD. The airplane was located about 1,472 feet down and 209 feet east of runway 18. The landing gear and wing flaps were extended. The left thrust reverser was unlatched and open and the right thrust reverser was closed and latched. The airplane was equipped with a cockpit voice recorder (CVR); however, the accident flight was not recorded. The audio on the CVR indicated the last events recorded were from 2007.

Crash of an Extra EA-400 in Ponca City: 5 killed

Date & Time: Aug 4, 2018 at 1045 LT
Type of aircraft:
Operator:
Registration:
N13EP
Flight Phase:
Flight Type:
Survivors:
No
MSN:
10
YOM:
2000
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
Shortly after takeoff from Ponca City Airport, while in initial climb, the single engine lost height and crashed nose first in a soybean field located few miles from the airport. The airplane disintegrated on impact and all five occupants were killed, three adults and two children. The registration needs to be confirmed.

Crash of a Cessna 208B Grand Caravan in Verdigris

Date & Time: Mar 24, 2015 at 1520 LT
Type of aircraft:
Operator:
Registration:
N106BZ
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Tulsa - Claremore
MSN:
288B-0106
YOM:
1988
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine aircraft left Tulsa on a post maintenance control flight with one pilot and one mechanic on board. En route, the pilot informed ATC about engine problems and attempted to divert to the Claremore-Rogers County Airport. The aircraft eventually hit tree tops and crashed in a small wooded area east of Verdigris. Both occupants were slightly injured while the aircraft was written off.

Crash of a Mitsubishi MU-2B-25 Marquise in Owasso: 1 killed

Date & Time: Nov 10, 2013 at 1546 LT
Type of aircraft:
Operator:
Registration:
N856JT
Flight Type:
Survivors:
No
Schedule:
Salina - Tulsa
MSN:
306
YOM:
1974
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
Aircraft impacted wooded terrain while maneuvering near Owasso, Oklahoma. The commercial pilot, who was the sole occupant of the airplane, sustained fatal injuries. The airplane was destroyed. The airplane was registered to Anasazi Winds, LLC, Tulsa, Oklahoma, and was operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed for the flight, and an instrument flight plan had been filed. The flight departed Salina Regional Airport (SLN), Salina, Kansas, about 1500, and was en route to Tulsa International Airport (TUL), Tulsa, Oklahoma. According to preliminary air traffic control communications and radar data, the airplane was cleared to land on runway 18L at TUL, and the pilot was instructed to reduce the airspeed to 150 knots. The pilot acknowledged the clearance and speed reduction. Radar data showed the airplane on a straight-in approach to runway 18L. After the airplane passed the runway 18L outer marker, the airplane began a left turn. The air traffic control tower controller asked the pilot about the deviation, and the pilot reported that he had a control problem. The left turn continued, and the controller then cleared the pilot to maneuver to the west and asked if he needed assistance. The pilot informed the controller that the left engine was shut down. The controller then declared an emergency for the pilot and asked about the number of souls on-board the airplane and the fuel remaining. No further communications were received from the pilot. Radar data showed the airplane complete a 360-degree left turn near the runway 18L outer marker at 1,100 feet mean sea level, and then radar contact was lost. Several witnesses observed the airplane in a shallow left turn; the reported altitudes ranged from 400 to 800 feet above ground level. During the turn, the landing gear was in the extended position, and one engine propeller appeared not to be rotating. The airplane continued in a left turn and the wings began to rock back and forth at a 10- to 15-degree bank angle. The airplane was observed to then make a right turn, followed by a left turn, and then a steep spiral to the left. The airplane disappeared from the witnesses' view as it descended. The accident site was located in wooded terrain about 5 miles north of TUL at a global positioning (GPS) elevation of about 650 feet. The airplane came to rest upright on a measured magnetic heading of 109 degrees. The main wreckage area consisted of all major airplane structure and components. The left engine propeller blades were found in a feathered position. The landing gear was found in the extended position, and the flaps were in the 20-degree position. Postimpact fire consumed a majority of the fuselage and wing structure. At 1553, the TUL automated surface observing system, located 5 miles south of the accident site, reported the wind from 140 degrees at 6 knots, visibility 10 miles, scattered clouds at 9,000 feet, temperature 19 degrees Celsius, dew point 6 degrees Celsius, and an altimeter setting of 30.26 inches of Mercury.

Crash of a Rockwell Aero Commander 500B in Bartlesville

Date & Time: Jan 13, 2012 at 1930 LT
Operator:
Registration:
N524HW
Flight Type:
Survivors:
Yes
Schedule:
Kansas City - Cushing
MSN:
500-1533-191
YOM:
1965
Flight number:
CTL327
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8487
Captain / Total hours on type:
3477.00
Circumstances:
The pilot was en route on a positioning flight when the airplane’s right engine surged and experienced a partial loss of power. He adjusted the power and fuel mixture controls; however, a few seconds later, the engine surged again. The pilot noted that the fuel flow gauge was below 90 pounds, so he turned the right fuel pump on. The pilot then felt a surge on the left engine, so he performed the same actions he as did for the right engine. He believed that he had some sort of fuel starvation problem. The pilot then turned to an alternate airport, at which time both engines lost total power. The airplane impacted trees and terrain about 1.5 miles from the airport. The left side fuel tank was breached during the accident; however, there was no indication of a fuel leak, and about a gallon of fuel was recovered from the airplane during the wreckage retrieval. The company’s route coordinator reported that prior to the accident flight, the pilot checked the fuel gauge and said the airplane had 120 gallons of fuel. A review of the airplane’s flight history revealed that, following the flight immediately before the accident flight, the airplane was left with approximately 50 gallons of fuel on board; there was no record of the airplane having been refueled after that flight. Another company pilot reported the airplane fuel gauge had a unique trait in that, after the airplane’s electrical power has been turned off, the gauge will rise 40 to 60 gallons before returning to zero. When the master switch was turned to the battery position during an examination of another airplane belonging to the operator, the fuel gauge indicated approximately 100 gallons of fuel; however, when the master switch was turned to the off position, the fuel quantity on the gauge rose to 120 gallons, before dropping off scale, past empty. Additionally, the fuel cap was removed and fuel could be seen in the tank, but there was no way to visually verify the quantity of fuel in the tank.
Probable cause:
The total loss of engine power due to fuel exhaustion and the pilot’s inadequate preflight inspection, which did not correctly identify the airplane’s fuel quantity before departure.
Final Report:

Crash of a Cessna 421A Golden I Eagle in Tulsa: 3 killed

Date & Time: Jul 10, 2010 at 2205 LT
Type of aircraft:
Operator:
Registration:
N88DF
Flight Type:
Survivors:
No
Schedule:
Pontiac - Riverside
MSN:
421-0084
YOM:
1968
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
592
Captain / Total hours on type:
67.00
Aircraft flight hours:
640
Circumstances:
During the 3.5-hour flight preceding the accident flight, the airplane used about 156 gallons of the 196 gallons of usable fuel. After landing, the airplane was topped off with 156 gallons of fuel for the return flight. During the preflight inspection, a line serviceman at the fixed based operator observed the right main fuel tank sump become stuck in the open position. He estimated 5 to 6 gallons of fuel were lost before the sump seal was regained, but the exact amount of fuel lost could not be determined. The lost fuel was not replaced before the airplane departed. Data from an on board GPS unit indicate that the airplane flew the return leg at an altitude of about 4,500 feet mean sea level for about 4 hours. About 4 minutes after beginning the descent to the destination airport, the pilot requested to divert to a closer airport. The pilot was cleared for an approach to runway 18R at the new destination. While on approach to land, the pilot reported to the air traffic control tower controller, “we exhausted fuel.” The airplane descended and crashed into a forested area about 1/2 mile from the airport. Post accident examination of the right and left propellers noted no leading edge impact damage or signatures indicative of rotation at the time of impact. Examination of the airplane wreckage and engines found no malfunctions or failures that would have precluded normal operation. The pilot did not report any problems with the airplane or its fuel state before announcing the fuel was exhausted. His acceptance of the approach to runway 18R resulted in the airplane flying at least 1 mile further than if he had requested to land on runway 18L instead. If the pilot had declared an emergency and made an immediate approach to the closest runway when he realized the exhausted fuel state, he likely would have reached the airport. Toxicological testing revealed cyclobenzaprine and diphenhydramine in the pilot’s system at or above therapeutic levels. Both medications carry warnings that use may impair mental and/or physical abilities required for activities such as driving or operating heavy machinery. The airplane would have used about 186 gallons of fuel on the 4-hour return flight if the engines burned fuel at the same rate as the previous flight. The fuel lost during the preflight inspection and the additional 30 minutes of flight time on the return leg reduced the airplane’s usable fuel available to complete the planned flight, and the pilot likely did not recognize the low fuel state before the fuel was exhausted due to impairment by the medications he was taking.
Probable cause:
The pilot’s inadequate preflight fuel planning and management in-flight, which resulted in total loss of engine power due to fuel exhaustion. Contributing to the accident was the pilot’s use of performance-impairing medications.
Final Report:

Crash of a Cessna 500 Citation in Oklahoma City: 5 killed

Date & Time: Mar 4, 2008 at 1515 LT
Type of aircraft:
Operator:
Registration:
N113SH
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Oklahoma City-Mankato
MSN:
500-0285
YOM:
1975
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
Less than 2 minutes after take off, the aircraft crashed in a wooded area located 5 miles SE of Wiley Post airport. All 4 occupants were killed. The aircraft was outbound for Mankato, Minnesota. According to preliminary report, it seems that the aircraft collided with a flock of birds.

Crash of a Rockwell Aero Commander 500 in Tulsa: 1 killed

Date & Time: Jan 16, 2008 at 2243 LT
Operator:
Registration:
N712AT
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Tulsa - Oklahoma City
MSN:
500-1118-68
YOM:
1961
Location:
Crew on board:
1
Crew fatalities:
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4373
Captain / Total hours on type:
695.00
Aircraft flight hours:
17888

Crash of a Rockwell Grand Commander 690 in Antlers: 4 killed

Date & Time: Oct 15, 2006 at 1303 LT
Operator:
Registration:
N55JS
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Oklahoma City-Orlando
MSN:
690-11195
YOM:
1974
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
6450
Captain / Total hours on type:
150.00
Aircraft flight hours:
7943
Circumstances:

Less than one hour after takeoff from Oklahoma City-Wiley Post airport, the aircraft disappeared from radar screens and crashed in a wooded area located near Antlers, Oklahoma. All four occupants were killed. Weather conditions at the time of the accident were considered as bad with low visibility and heavy rain falls.

Crash of a Beechcraft Super King Air 200 in Tulsa

Date & Time: Dec 9, 2004 at 1831 LT
Operator:
Registration:
N6PE
Flight Type:
Survivors:
Yes
Schedule:
La Crosse-Tulsa
MSN:
BB-0856
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2089
Captain / Total hours on type:
469.00
Aircraft flight hours:
3084
Circumstances:
On final approach, the twin engine aircraft crashed 5 km short of runway. The pilot was injured and the aircraft destroyed. One of the engine stopped during final approach due to fuel exhaustion