MIA07LA133 · Beech B36TC
Beech B36TC · Accident: loss of control in flight during initial climb
From Clearwater Air Park (CLW) to Spruce Creek Airport (7FL6)
Event
- NTSB case
- MIA07LA133
- 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
Beech B36TC
- Aircraft type
- Beechcraft 36
- 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
- N6750C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Clearwater Air Park (CLW), Clearwater, FLTo Spruce Creek Airport (7FL6), Spruce Creek, 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
- Loss of control in flight
- 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/mush
- 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 › Climb, improper
- Pilot in command › Rotation, 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 the day was hot and humid, and during the takeoff roll he rotated at 85 knots, with the engine developing full power, and no problems being noted. About 60 feet off the ground he said he raised the landing gear and shortly thereafter the airplane did one yaw to the right, and one yaw to the left. It then settled/pancaked straight down landing hard and flat, and then skidded some distance. According to the pilot the engine was producing good power, and was loaded within the weight and balance envelope, having 105 gallons of fuel on board, along with himself and two normal sized adults. The owner of the accident airplane said that he both observed the takeoff, and later spoke with the pilot while he was in the hospital, and the pilot told him that the takeoff roll had been uneventful, however, after rotating, and when about 50 feet in the air, the flight controls became mushy, and he did not have any elevator or rudder control. Other witnesses all stated that they saw the airplane lift off in the vicinity of the fuel farm, which is about 1100 feet from the beginning of the runway, and as the airplane climbed, they noticed that its wings began to rock increasingly, and the airplane began to porpoise. They further stated that the gear had been retracted when they saw the airplane at that point, and the airplane appeared as if it simply ceased flying. According to the witnesses, the engine sounded as if it was operating normally, and the propeller had also been rotating throughout the takeoff. An FAA inspector responded to the scene and his postcrash examination revealed that airplane's flight controls functioned normally, and there were no anomalies. In addition, another FAA inspector along with technicians from Teledyne Continental Motors, conducted a detailed examination of the airplane's engine and accessories, and no anomalies were noted.
Probable cause
The pilot's improper rotation and climb during the takeoff which resulted in a stall/mush, a descent, and an impact with the ground.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA07LA133
- Event ID
- 20070823X01231
- Case number
- MIA07LA133
- 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: 46f04dfe3c2068cb04e6d9f2567081d1a4a829361d859cf1a7c1cb0529bbf79b; retrieved 2026-09-21T08:45:27.541Z.