FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA05CA092 · Cessna 337 B

13 Apr 2005 · Ocala, FL, United States

Cessna 337 B · Accident: hard landing during takeoff

From Ocala International Airport - Jim Taylor Field (OCF) to Ocala International Airport - Jim Taylor Field (OCF)

Report a problem

Event

NTSB case
MIA05CA092
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 337 B

Aircraft type
Cessna 337
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N463DA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Ocala International Airport - Jim Taylor Field (OCF), Ocala, FLTo Ocala International Airport - Jim Taylor Field (OCF), Ocala, FL
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Takeoff · rejected takeoff
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Hard landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Flare, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot stated that during the engine run up check he discovered the rear engine shutdown. He restarted the rear engine, leaned the fuel mixture and performed a magneto check. He taxied to the hold short line for runway 26, then announced his departure on the airport Unicom frequency and positioned the airplane onto the runway. He partially advanced the rear engine throttle and the airplane moved forward. He heard an aircraft reporting final and was not certain if the broadcast was for runway 26 or 36. Not certain for which runway, he advanced both throttles forward. The airplane accelerated to 70 knots and was about 1,000 feet down the runway when he rotated. The airplane lifted off the ground; however the airplane did not accelerate. He glanced inside the cockpit and saw the fuel mixtures were not full forward. He advanced the mixtures and looked outside of the cockpit. The airplane was about 2/3 down and about 100 feet above the runway. He elected to abort the takeoff at that point. He retarded the throttles, selected the flaps full up to get airplane on its wheels, as soon as the wheels touched down, the airplane slammed into the ground at a nose high attitude. He believes the airplane bounced once coming to rest on its nose and propeller in the dirt; about 50 feet from the left edge and 500 feet past the end of the runway. He secured the airplane and exited through the enter door. The pilot stated there were no mechanical failures or malfunctions to the airplane or any of its systems prior to the accident. Runway 26 at the Ocala International Airport is published 3,010 foot long runway.

Probable cause

The pilot's improper landing flare during an aborted takeoff, which resulted in a hard landing and damage to the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA05CA092
Event ID
20050513X00607
Case number
MIA05CA092
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 6caed1c0d37240fe33f1fb292d7028baae13375d4970e240df509a58cc59cf32; retrieved 2026-09-22T06:05:21.972Z.