DFW08CA152 · Rotorway 162F
Rotorway 162F · Accident: system/component malfunction/failure (non-power) during initial climb
From Roger M Dreyer Memorial Airport (T20) to Gonzales, TX
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- DFW08CA152
- 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
Rotorway 162F
- Aircraft type
- Rotorway 162
- Category
- Helicopter
- 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
- N771SS
- Operator
- Jonathan Houser
- Onboard fatalities
- Unknown
- Route
- From Roger M Dreyer Memorial Airport (T20), Gonzales, TXTo Gonzales, TX
- 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
- System/component malfunction/failure (non-power)
- 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
- Aircraft › Aircraft propeller/rotor
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot and his passenger had just departed in a single-engine experimental helicopter when he heard a "loud pop" followed by a loss of engine power. The pilot entered an autorotation from an altitude of 75 feet and flared at approximately 40 feet above the ground to avoid hitting trees. The helicopter landed hard in a grass field and the skids were spread upon impact. The two occupants were able to deplane before the engine exhaust caught the surrounding grass on fire, and subsequently destroyed the helicopter. The pilot reported that the main drive belt, which he had been recently replaced, had failed. The helicopter wreckage was examined by an FAA inspector; however, the drive belt could not be located and it was assumed to have been destroyed in the post-impact fire.
Probable cause
failure of the main rotor drive belt for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW08CA152
- Event ID
- 20080625X00914
- Case number
- DFW08CA152
- 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: 79ce44753de1f85fc71bc3a0e5a71d6d0fdfcd82dd4b4fc19b277bcf014b6b9c; retrieved 2026-09-15T09:48:43.326Z.