MIA05FA050 · Cessna T337G
Cessna T337G · Accident: abrupt maneuver during initial climb
From Lakeland Linder International Airport (KLAL) to Tallahassee International Airport (KTLH)
Event
- NTSB case
- MIA05FA050
- 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
- 2 · 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 T337G
- 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
- N42WA
- Operator
- Danny Ferrer
- Onboard fatalities
- Unknown
- Route
- From Lakeland Linder International Airport (KLAL), Lakeland, FLTo Tallahassee International Airport (KTLH), Tallahassee, 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
- Initial climb
- 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
- Abrupt maneuver
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Airspeed(vs), not maintained
- Pilot in command › Operation with known deficiencies in equipment
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to a witness, the airplane was in a steep nose-up attitude after becoming airborne, then rolled left and impacted the ground while in a slight nose-up and left wing low attitude. An individual who owns a Cessna 337 heard both engines operating at what he thought was full power. The airplane impacted on the runway surface and was destroyed by impact and the postcrash fire. According to a witness, the pilot started the engines and taxied to utilize all available runway. The flight was cleared to takeoff, and according to a controller in the tower cab, he did not observe the point of rotation, but reported the airplane was in a normal climb attitude when the flight was airborne approximately 1,000 feet down the runway, when it was approximately 500 feet more down the length of the runway, he observed the airplane pitch up to between an estimated 30-45 degrees, then level off at an estimated altitude of between 150-200 feet above ground level. Approximately 5 seconds later, the wings were noted to rock up and down and the airplane drifted north of the runway. The airplane rolled nose and left wing low, then appeared to level off before impacting the ground while in a slight nose up and left wing low attitude. He did not hear any unusual engine sounds during the flight and could not determine if the engines were run-up before departure. Both engines' rpm sounded to be synchronized during the flight. There was no distress call made by the pilot. The owner recently purchased the airplane and had a pre-buy inspection of it; no discrepancies were noted related to the flight controls. The airplane was flown from the place where purchased (California), to Florida, and was delivered 2 days before the accident. The pilot who flew the airplane to Florida reported it was a "fairly flawless trip." He did report that the autopilot was inoperative, and the digital fuel flow meter was inoperative. No repairs were performed to correct the inoperative autopilot before the accident flight. The accident pilot flew the airplane on 3 separate flights earlier on the day of the accident, and during the takeoff of all 3 flights, a pilot rated passenger later reported that the airplane pitched up aggressively during rotation. The passenger looked at the elevator trim setting and noted it was in the correct range for takeoff. During the landing of the third leg, the accident pilot reportedly performed a full stall landing from a height of 10 feet. The airplane was then taxied to the ramp and both fuel tanks were topped off for the accident flight. No maintenance was performed to the elevator primary or secondary flight control systems as a result of the reported excessive pitch-up events. Examination of the primary and secondary flight control system of the airplane revealed no evidence of preimpact failure or malfunction of the cables. The elevator trim was found set to 4 to 5 degrees aircraft nose-down. The flaps were extended 10 degrees, and the landing gear was extended at impact. Examination of the front and rear engines propeller and propeller governors revealed no evidence of preimpact failure or malfunction. Examination of the pilot's seat tracks revealed both exhibited evidence of lock pin engagement at the time of impact in the 9th hole from the front. The airplane was calculated to be within weight and balance limits at the time of the accident.
Probable cause
The pilot's operation of the airplane with known deficiencies in equipment related to pitch, an abrupt pitch-up during the initial climb after takeoff for undetermined reasons and the failure of the pilot to maintain airspeed (Vs) resulting in inadvertent stall, uncontrolled descent, and in-flight collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA05FA050
- Event ID
- 20050125X00104
- Case number
- MIA05FA050
- 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: e354aeb8bf162f08f576dcc1afa0c1f7950ce6d3055b1cbfb4408cb7537e3c8e; retrieved 2026-09-20T18:08:43.505Z.