CEN10CA294 · Holden Frank Joseph RANS S6ES
Holden Frank Joseph RANS S6ES · Accident: loss of control in flight during takeoff
From Waxahachie, TX to Waxahachie, TX
Narrative check · The NTSB narrative appears to contradict this record's location and departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN10CA294
- 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
Holden Frank Joseph RANS S6ES
- Aircraft type
- Holden Frank Joseph RANS S6ES
- 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
- N9870V
- Operator
- Bramall Buster I
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Waxahachie, TXTo Waxahachie, 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
- Takeoff
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While taking off everything seemed normal until rotation. the pilot then noticed that the airplane's nose seemed heavy and slow to lift off. He lowered the nose to gain airspeed and rotated again to achieve only a "very flat fly out." About 100 feet above the ground he initiated a right turn to avoid power lines. As he rolled out he was at about 40 miles per hour on the airspeed indicator and he could not control the pitch with full aft stick. The airplane started to descend and impacted the ground in a hay field. Examination of the airplane revealed no preexisting anomalies. According to the airplane designer, best climb is attained at 65 knots and at 45 knots the elevator will feel mushy. The pilot and owner did not submit a NTSB Form 6120.1.
Probable cause
The pilot's failure to attain adequate airspeed during takeoff, resulting in a stall/msuh.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA294
- Event ID
- 20100603X20702
- Case number
- CEN10CA294
- 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. 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: 1c0e362aa57b46773f8754e28af5fbf74f60d6b57466d5b545e44fed41602a16; retrieved 2026-09-15T14:20:43.961Z.