ERA12FA051 · Cessna 150F
Cessna 150F · Accident: loss of control in flight during initial climb
From Berkeley County Airport (MKS) to Berkeley County Airport (MKS)
Event
- NTSB case
- ERA12FA051
- 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
Cessna 150F
- Aircraft type
- Cessna 150
- 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
- N3086X
- Operator
- Tollett Kenneth W
- Onboard fatalities
- Unknown
- Route
- From Berkeley County Airport (MKS), Moncks Corner, SCTo Berkeley County Airport (MKS), Moncks Corner, 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
- Defining eventThe 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
- 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
- Personnel issues › Physical
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
According to a flight instructor, the pilot’s intent was to practice for an upcoming flight review. There were no witnesses to the accident; however, a witness at the airport observed the pilot park his car near the hangar that housed the airplane, untie the airplane, and pull it out of the hangar. Then, as the witness was leaving the airport, he saw the pilot get into the airplane. The witness also noted that the sun had gone down, but it was not quite dark when he left. Radar data for the timeframe just after the witness observed the pilot indicated a target transmitting a 1200 transponder code that is consistent with the airplane’s location. Just after sunset, the airplane took off and, after a brief flight to the northwest of the airport, entered the airport traffic area and completed a landing. After 5 minutes, the airplane was again airborne, and, according to radar data, completed another landing or a low approach. There was no further radar contact.
The pilot was reported missing 11 days after the accident and was found 3 days after that about 30 feet away from the airplane wreckage. The wreckage came to rest wedged between several trees about half way along, and to the right of, the runway about 60 feet outside the northwest airport perimeter fence. Initial tree cuts were consistent with an approximate 45-degree right-wing-down turn and 45-degree angle of descent, which is consistent with the pilot’s loss of control in flight. An examination of the wreckage revealed no mechanical malfunctions or failures that would have precluded normal operation.
The pilot’s location at the accident site indicated that he was able to unhook his seatbelt and extricate himself from the airplane. Autopsy results for the pilot indicated that the cause of death was most likely the “toxic effects of ethylene glycol,” a substance most frequently encountered in antifreeze fluid. Toxicological testing did not reveal the presence of ethylene glycol, but the autopsy found associated crystals in the kidney, indicating that the pilot survived long enough for the substance to clear his system. Initial symptoms of ethylene glycol poisoning mimic acute ethanol intoxication, with slurred speech and ataxia. Depression of the central nervous system can result in coma. Kidney failure is a late stage symptom.
According to the pilot's logbooks, his most recent flight review was about 9 years before the accident, and his most recent recorded flight was about 5 months before the accident. It was unknown if the pilot had recently flown but not logged the flight time. Although the pilot’s lack of recently logged flight time could indicate a loss of airplane control related to a lack of currency, it is far more likely that the debilitating effects of ethylene glycol posioning rendered him unable to control the airplane while airborne. How or why the pilot may have ingested ethylene glycol is beyond the scope of this investigation.
Probable cause
The debilitating effects of ethylene glycol poisoning, which resulted in the pilot’s inability to maintain control of the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12FA051
- Event ID
- 20111027X32938
- Case number
- ERA12FA051
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 2cd6b6fda97441969c3acf5bfffece4d4d894c6255467a0ab2ef183daa579ae2; retrieved 2026-09-13T21:56:39.174Z.