WPR23FA323 · Hensler Howard CASSUTT
Hensler Howard CASSUTT · Accident: loss of control in flight during initial climb
Event
- NTSB case
- WPR23FA323
- 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
Hensler Howard CASSUTT
- Aircraft type
- Hensler Howard CASSUTT
- 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
- N6291N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 22 years (built 2001)
- 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
- Aircraft › Aircraft oper/perf/capability
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was performing test flights in the accident airplane after he assembled and installed the engine. The pilot (racer) who was scheduled to fly the airplane in an upcoming air race stated that, during the flight before the accident flight, the accident pilot had noticed high engine oil temperature. The racer also stated that the engine oil pressure was low before the accident pilot departed on the accident flight. The racer witnessed that accident, and stated that, after the airplane lifted off about 1/3 down the runway, it entered a climb and then made an abrupt right turn, entered a nose-down attitude, and rapidly descended to the ground. Surveillance video showed the airplane impact the fence and the ground in a slight nose- and left-wing-low attitude. There was no flight track data associated with the accident flight or nonvolatile memory recovered from the airplane. Postaccident examination of the airframe revealed multiple separations in the flight control system; however, there was no evidence of a preimpact mechanical anomaly or malfunction that would have precluded normal operation. The engine examination showed circumferential recessed grooves on multiple crankshaft main journals, longitudinal scoring marks on each of the piston skirts, and severe wear on several of the bearing shell inner surfaces. This engine wear was likely to have caused a malfunction such as a loss of power or engine seizure; however, whether or to what extent an engine performance deficiency contributed to the accident could not be determined. The pilot had reconfigured the airplane from a conventional to a T-tail design. Subsequent flight testing by the pilot’s friend showed that the airplane could enter a “deadband” during turns, in which the elevator would become ineffective. Elevator effectiveness could only be resolved by accelerating. No maintenance or flight records were obtained for the accident airplane, and the pilot’s total and recent experience in the airplane, either before or after the empennage reconfiguration, could not be determined. While the witness’ descriptions of the accident indicate that the airplane may have entered an accelerated stall during the turn, it is also possible that the pilot lost elevator authority while maneuvering at a low altitude and he was unable to recover. Due to the lack of data associated with the accident flight, the circumstances of the loss of control could not be determined. The pilot’s autopsy report identified 75% narrowing of the left anterior descending coronary artery by plaque and no other evidence of significant natural disease; however, there was no forensic evidence that the pilot had a cardiac event in flight, thus it is unlikely that the pilot’s coronary artery disease contributed to the accident.
Probable cause
A loss of control during the initial climb for reasons that could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR23FA323
- Event ID
- 20230824192931
- Case number
- WPR23FA323
- 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, cause areas. 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: bf21a22e55deac1ba11b9b274604c03db8d77a4cf2e725e867a36144c7814120; retrieved 2026-09-15T08:05:12.095Z.