Cessna 340 N6239X
18 March 2016 · Tampa, Florida, United States · Fatal
Summary
On 18 March 2016 at about 15:30 local time, a Cessna 340 registered N6239X was involved in an accident near Tampa, Florida, United States. 2 people were on board and 2 died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 15:30
- Classification
- Accident
- Location
- Tampa, Florida, United States
- Nearest airport
- Peter O Knight (TPF)
- Coordinates
- 27.9197, -82.4478
- Aircraft
- Cessna 340
- Registration
- N6239X
- Category
- Airplane
- Year built
- 1977
- Engines
- 2
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Tampa → Pensacola
- Aircraft damage
- Destroyed
- Weather
- VMC
- Light
- Day
- NTSB number
- ERA16FA133
People
2 people died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 2 | 2 | 0 | 0 | 0 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
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.
Quoted verbatim from the NTSB record.
Other Cessna 340 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 27 Jan 2016 | Cessna 340A | Bakersfield, California, United States | Pacific FBO Properties LLC | No injuries | - |
| 1 Dec 2016 | Cessna 340 | Fargo, North Dakota, United States | - | Fatal | 1 |
| 9 Sep 2017 | Cessna 340 | McKinney, Texas, United States | Holubar Properties Inc | No injuries | - |
| 2 Mar 2017 | Cessna 340 | Ft Lauderdale, Florida, United States | Southern Aircraft Consultancy Inc Truste | No injuries | - |
| 27 Aug 2015 | Cessna 340A | Vicovu de Sus, Romania | - | No injuries | - |
| 24 Dec 2017 | Cessna 340 | Bartow, Florida, United States | - | Fatal | 5 |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 12 Dec 2016 | Beechcraft A36 | New Smyrna Beach, Florida, United States | - | Minor injuries | - |
| 24 Aug 2016 | Heberlein Ronald VANS RV 9A | Sebring, Florida, United States | - | Fatal | 1 |
| 18 Jan 2016 | Cessna 210 | Venice, Florida, United States | - | No injuries | - |
| 21 Aug 2016 | Cessna 152 | Miami, Florida, United States | - | No injuries | - |
| 23 Aug 2016 | Progressive Aerodyne SEAREY | Sebring, Florida, United States | - | Serious injuries | - |
| 17 Dec 2016 | Beechcraft A36 | Ormond Beach, Florida, United States | - | Serious injuries | - |