Zone

Crash of a Rockwell Aero Commander 500B near Sylacauga

Date & Time: Jan 28, 2023 at 1740 LT
Operator:
Registration:
N107DF
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Tampa - Birmingham
MSN:
500B-1191-97
YOM:
1962
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The pilot departed Tampa Executive Airport at 1550LT on a cargo flight to Birmingham, Alabama. About two hours and a half into the flight, while approaching Birmingham-Shuttlesworth Airport from the southeast at an altitude of 5,800 feet, the pilot initiated a 180 turn in an apparent attempt to divert to Sylacauga Airport. Shortly later, the twin engine airplane impacted the ground and crashed into trees some 5 km north of Sylacauga Airport which is located 60 km southeast of Birmingham-Shuttlesworth Airport. The pilot was transported to local hospital but seems to be uninjured.

Crash of a Cessna 340A in Tampa: 2 killed

Date & Time: Mar 18, 2016 at 1130 LT
Type of aircraft:
Operator:
Registration:
N6239X
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Tampa – Pensacola
MSN:
340A-0436
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
5195
Aircraft flight hours:
3963
Circumstances:
The airline transport pilot and pilot-rated passenger were departing on an instrument flight rules (IFR) cross country flight from runway 4 in a Cessna 340A about the same time that a private pilot and pilot rated passenger were departing on a visual flight rules repositioning flight from runway 36 in a Cessna 172M. Visual meteorological conditions prevailed at the airport. The runways at the nontowered airport converged and intersected near their departure ends. According to a witness, both airplanes had announced their takeoff intentions on the airport's common traffic advisory frequency (CTAF), which was not recorded; the Cessna 340A pilot's transmission occurred about 10 to 15 seconds before the Cessna 172M pilot's transmission. However, the witness stated that the Cessna 172M pilot's transmission was not clear, but he was distracted at the time. Both occupants of the Cessna 172M later reported that they were constantly monitoring the CTAF but did not hear the transmission from the Cessna 340A pilot nor did they see any inbound or outbound aircraft. Airport video that captured the takeoffs revealed that the Cessna 172M had just lifted off and was over runway 36 approaching the intersection with runway 4, when the Cessna 340A was just above runway 4 in a wings level attitude with the landing gear extended and approaching the intersection with runway 36. Almost immediately, the Cessna 340A then began a climbing left turn with an increasing bank angle while the Cessna 172M continued straight ahead. The Cessna 340A then rolled inverted and impacted the ground in a nose-low and left-wing-low attitude. The Cessna 172M, which was not damaged, continued to its destination and landed uneventfully. The Cessna 340A was likely being flown at the published takeoff and climb speed of 93 knots indicated airspeed (KIAS). The published stall speed for the airplane in a 40° bank was 93 KIAS, and, when the airplane reached that bank angle, it likely exceeded the critical angle of attack and entered an aerodynamic stall. Examination of the Cessna 340A wreckage did not reveal any preimpact mechanical malfunctions that would have precluded normal operation. Because of a postcrash fire, no determination could be made as to how the radios and audio panel were configured for transmitting and receiving or what frequencies were selected. There were no reported discrepancies with the radios of the Cessna 172M, and there were no reported difficulties with the communication between the Cessna 340A and the Federal Aviation Administration facility that issued the airplane's IFR clearance. Additionally, there were no known issues related to the CTAF at the airport. Toxicological testing detected unquantified amounts of atorvastatin, diphenhydramine, and naproxen in the Cessna 340A pilot's liver. The Cessna 340A pilot's use of atorvastatin or naproxen would not have impaired his ability to hear the radio announcements, see the other airplane taking off on the converging runway, or affected his performance once the threat had been detected. Without an available blood level of diphenhydramine, it could not be determined whether the drug was impairing or contributed to the circumstances of the accident.
Probable cause:
The intentional low altitude maneuvering during takeoff in response to a near-miss with an airplane departing from a converging runway, which resulted in an exceedance of the airplane's critical angle of attack and a subsequent aerodynamic stall.
Final Report:

Crash of a Beechcraft A90 King Air in Tampa: 1 killed

Date & Time: Jun 12, 2006 at 1235 LT
Type of aircraft:
Operator:
Registration:
N7043G
Flight Type:
Survivors:
Yes
Schedule:
Sarasota - Tampa
MSN:
LM-37
YOM:
1967
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2120
Captain / Total hours on type:
457.00
Copilot / Total flying hours:
1208
Copilot / Total hours on type:
44
Aircraft flight hours:
15671
Circumstances:
The first officer reported that during cruise flight, both propeller secondary low pitch stop (SLPS) lights illuminated, indicating the SLPS system prevented both propellers from going below the low pitch hydraulic mechanical stop. The right occurred first, then the left approximately 1 minute later. Emergency procedures to correct the condition were ineffective. The right propeller feathered at some point during the flight, and the first officer reported that while operating single engine, they experienced a problem with the propeller governor. The flight proceeded direct to an airport with short runways approximately 3.2 nautical miles (nm) northwest of their present position, rather than to an air carrier airport located 8.5 nm away. The captain entered a close-in right base to runway 35 (2,688 feet long runway), while flying at 155 knots (51 knots above single engine reference speed). He turned onto final approach with the landing gear and flaps retracted, but overshot the runway. The airplane contacted a taxiway near the departure end of intended runway, and then collided with several obstacles before coming to rest at a house located past the departure end of runway 35. A post crash fire consumed the cockpit, cabin, and sections of both wings. Post accident examination of the airframe, engines, and propellers revealed no evidence of preimpact failure or malfunction. No determination was made as to the reason for the annunciation of both SLPS lights.
Probable cause:
The poor in-flight planning decision by the captain for his failure to establish the airplane on a stabilized approach for a forced landing, resulting in the airplane landing on a taxiway near the departure end of the runway. Contributing to the accident were the failure or malfunction of the primary hydraulic low pitch stop of both propellers for undetermined reasons, the excessive approach airspeed and the failure of the captain to align the airplane with the runway for the forced landing.
Final Report:

Crash of a Beechcraft AT-11 Kansan in Tampa: 2 killed

Date & Time: Feb 27, 1999 at 1010 LT
Type of aircraft:
Registration:
N65860
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Tampa - Lakeland
MSN:
4531
YOM:
1943
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
15000
Captain / Total hours on type:
2000.00
Aircraft flight hours:
13300
Circumstances:
Witnesses saw the airplane depart the airport to the south, turn left at an altitude of about 200 feet above the ground (agl), fly downwind to the departure runway, climb to an altitude of about 800 to 1,000 feet, and then turn right. A witness, who was operating a crane near the crash site said, he saw the airplane approaching from the south heading towards the north, turn to the right (east), and flew directly over him. He told police officers that he could see both propellers 'spinning,' and could 'actually see the pilot flying the plane.' The witness said, '...[the] motor sounded fine...[and the airplane] took a sharp downward fall, hit the road and bounced in the air, then fire started....' Other witnesses said they saw the angle of bank increase, the airplane descend rapidly, impact on a four-lane hard surface road right wing first, strike a wooden power pole, burst into flames, and come to rest in marshy area on the eastside of the road. Examination of the airframe, engine and propeller revealed no discrepancies.
Probable cause:
The pilot's failure to maintain control of the airplane resulting in an inadvertent stall at too low an altitude to allow for recovery.
Final Report:

Crash of a Cessna 401 off Tampa

Date & Time: Dec 31, 1976 at 1156 LT
Type of aircraft:
Operator:
Registration:
N111TV
Flight Type:
Survivors:
Yes
Schedule:
Tampa - Tampa
MSN:
401-0158
YOM:
1968
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
437
Captain / Total hours on type:
129.00
Circumstances:
The twin engine airplane departed Tampa Airport in the morning for a local pleasure flight. On final approach to Tampa Airport, the pilot failed to extend the landing gear. Upon landing, the engine's propeller struck the runway surface. The pilot initiated a go-around but unable to maintain altitude, the aircraft lost height and crashed into Tampa Bay. All six occupants were rescued with minor injuries and the aircraft was lost.
Probable cause:
Wheels-up landing and controlled collision with water during go-around manoeuvre. The following contributing factors were reported:
- The pilot failed to extend landing gear on approach,
- Un maintain altitude during go-around due to prop damages.
Final Report: