MIA96FA130 · Helio H-295
Helio H-295 · Accident: airframe, component or system failure during takeoff
From an unrecorded airport to 47J · Cheraw, SC
Event
- NTSB case
- MIA96FA130
- 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
- 0
- 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
Helio H-295
- Aircraft type
- Helio H-295
- 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
- N700HC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 47J · Cheraw, 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
- Takeoff · roll/run
- 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
- Airframe, component or system failure
- 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
- Pilot in command › Aircraft preflight, inadequate
- Pilot in command › Removal of control/gust lock(s), not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During takeoff, the aircraft veered to the right and went off of the airstrip about 300 feet from the departure end, then it continued on a course parallel to the airstrip. The aircraft was reported to be in a tail-high, nose-low attitude, and the propeller was striking the ground. The aircraft was estimated to be traveling at about 89 knots at that time. Subsequently, the aircraft collided with a berm and became airborne, then it collided with trees and crashed into a ditch at the end of the airstrip. A postcrash fire erupted and further damaged the aircraft. Postcrash examination of the aircraft structure and engine did not show evidence of a precrash failure or malfunction; except during a check of the flight controls, the remains of a drywall screw were found in the control lock hole on the control column. This screw was locking the controls in an aircraft nose-down attitude. Members of the pilot's family and the mechanic, who maintained the aircraft, identified the drywall screw as the device used by the pilot to lock the controls on the ground.
Probable cause
failure of the pilot to remove the control lock during the preflight, and his failure to check the flight controls before taking off.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA96FA130
- Event ID
- 20001208X05631
- Case number
- MIA96FA130
- 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. 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: 4fc60e463ea3910b3f2b648032ca292e61a870f2a3d57547bd6e9d2301930f68; retrieved 2026-09-20T23:22:24.925Z.