SEA05LA076 · Beech A36
Beech A36 · Accident: loss of engine power during initial climb
From Plant City Municipal Airport (PCM) to Rock Hill - York County Airport (UZA)
Event
- NTSB case
- SEA05LA076
- 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 A36
- 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
- N33CF
- Operator
- Clarence O. Floyd · private individual
- Onboard fatalities
- Unknown
- Route
- From Plant City Municipal Airport (PCM), Plant City, FLTo Rock Hill - York County Airport (UZA), Rock Hill, SC
- 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 engine power
- 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
- 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
The pilot reported the takeoff roll was normal; however shortly after takeoff during the climb he noted a reduction in the climb performance at takeoff power. He stated the airplane began to settle, eventually impacting terrain in a tail-low attitude. The pilot and the five passengers aboard the airplane were not injured and were able to exit the airplane without assistance. Post accident examination of the engine revealed no evidence of a mechanical malfunction that would have contributed to a loss of engine power. Downloaded data for the airplane's engine monitoring system revealed no evidence of an engine anomaly. Data from the accident flight were consistent with normal engine operations and no different from the values found in identically equipped and configured engine.
Probable cause
An engine power interruption during takeoff for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA05LA076
- Event ID
- 20050419X00475
- Case number
- SEA05LA076
- 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: 134bdda51f0cd6c0eb0cb074fbaaa5fec2a676b398951ea95c3fb10d9b5633d6; retrieved 2026-09-22T06:03:11.090Z.