CESSNA 340A near Ocala, FL — 2012-01-27
- Date
- 2012-01-27
- Location
- Ocala, FL, USA
- Airport
- OCF
- Aircraft
- CESSNA 340A
- Registration
- N340HF
- Category
- Airplane
- Highest injury
- Fatal
- Fatalities
- 1
- Phase of flight
- Approach
Probable cause
The pilot's failure to maintain adequate airspeed and altitude on final approach, resulting in an impact with terrain short of the airport.
NTSB narrative
The pilot entered the left downwind leg of the traffic pattern to land to the north. A surface wind from the west prevailed with gusts to 15 knots. Radar data revealed that the airplane was on final approach, about 1.16 miles from the runway and about 210 feet above the ground. The airplane then crashed in a pasture south of the airport, in a slight left-wing-low attitude, and came to rest upright. The cockpit and cabin were consumed in a postcrash fire. The pilot's wife, who was in the aft cabin and survived the accident, recalled that it was choppy and that they descended quickly. She recalled hearing two distinct warning horns in the cockpit prior to the crash. The airplane was equipped with two aural warning systems in the cockpit: a landing gear warning horn and a stall warning horn. The pilot likely allowed the airspeed to decay while aligning the airplane on final approach and allowed the airplane to descend below a normal glide path. Examination of the wreckage revealed that the landing gear were in transit toward the retracted position at impact, indicating that the pilot was attempting to execute a go-around before the accident. The pilot made no distress calls to air traffic controllers before the crash. The pilot did not possess a current flight review at the time of the accident. Examination of the wreckage, including a test run of both engines, revealed no evidence of a pre-existing mechanical malfunction or failure that would have precluded normal operation of the airplane.
Analysis
- Primary failure mode
- Controlled flight into terrain
- First missed decision gate
- Pilot could have aborted the approach when conditions became choppy and bumpy.
NTSB coding
Evidence available
- ATC audio
- ADS-B / radar
- Photos
- 27 docket documents
Docket documents27
- Partial Transcripts - ATC Communicationsatc
- Evidence Control Formsform
- Reports from Federal Agencies - FAA Form 8020-6form
- Retention / Release of Wreckage Formform
- FAA Record of Interview with Passengerinterview
- Statement of Party Representatives to NTSB Investigationinterview
- Excerpts - Aircraft Logbookother
- Excerpts - Left Engine Logbookother
- Excerpts - Pilot Logbookother
- Excerpts - Right Engine Logbookother
- NTSB Record of Conversation - C Golsonother
- NTSB Record of Conversation - Loweryother
- NTSB Record of Conversation - Petersonother
- Photo 1: Main Wreckage, Viewed from Right (NTSB Digital Photo)photos
- Photo 2: Main Wreckage, Viewed from Front (NTSB Digital Photo)photos
- Photo 3: Main Wreckage, Viewed from Left (NTSB Digital Photo)photos
- Photo 4: Main Wreckage, Viewed from Aft (NTSB Digital Photo)photos
- Photo 5: Initial Ground Impact Scar (NTSB Digital Photo)photos
- Photo 6: Left Engine and Propeller (NTSB Digital Photo)photos
- Photo 7: Right Engine and Propeller (NTSB Digital Photo)photos
- Photo 8: Cockpit Fire Damage (NTSB Digital Photo)photos
- Photo 9: Landing Gear Actuator (NTSB Digital Photo)photos
- Radar Dataradar
- Left Engine Test Report - CMIreport
- Right Engine Test Report - CMIreport
- Toxicological Reportreport
- Weather Reports and Recordsreport
Related mishaps
- SUTPHIN JOHN E RANS S-12
2022-08-31 · Hilliard, FL
- LET L-23 SUPER BLANIK
2022-06-22 · Yoder, KS
- BEECH E35
2022-06-18 · Buckeye, AZ · 2 fatalities
- ZENITH STOL CH701
2021-11-12 · Randsburg, CA · 2 fatalities
- KOSTRAZEWA ANDRE Sonex Light Sport
2020-06-25 · Centerville, UT · 2 fatalities
- Cirrus SR20
2020-05-20 · Santa Maria, CA · 1 fatality