NYC06FA230 · Beech S35
Beech S35 · Accident: loss of control in flight during takeoff
From Lake City Airpark (FL27) to an unrecorded destination
Event
- NTSB case
- NYC06FA230
- 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
- 1 · 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 S35
- Aircraft type
- Beechcraft 35
- 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
- N5852S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lake City Airpark (FL27), Lake City, FLTo not recorded
- 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
- 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
- Tree(s)
- 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
- 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 evening prior to the accident, the pilot introduced a mixture of hydraulic fluid and lacquer thinner into the engine to free up some "stuck valves." The following morning, he taxied the airplane to the grass runway on the airpark where he lived. He performed a lengthy runup and unintentionally became airborne, shortly after which the airplane rolled to the right and struck trees prior to impacting the ground. He had been treated for a number of ongoing medical issues, and did not have a current medical certificate, He had high blood pressure, recent evidence of some previous asymptomatic strokes, had recently complained of persistent knee pain following a right knee replacement, and was on a blood thinner. The pilot may have been unable to maintain control of the aircraft during the engine run-up due to knee pain or may have suffered a sudden hemorrhagic (bleeding) stroke into the brain, made considerably more likely by his age, his high blood pressure and his continued use of a blood thinner.
Probable cause
A loss of control during an unintentional takeoff for an undetermined reason.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC06FA230
- Event ID
- 20061023X01552
- Case number
- NYC06FA230
- 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: 7b971089a01ee5f3b9eec195f4d957e89e67ba8c6411a6102de90874f2ffb34d; retrieved 2026-09-20T17:02:27.562Z.