CEN24FA298 · DeGraw DeBird
DeGraw DeBird · Accident during initial climb
Event
- NTSB case
- CEN24FA298
- 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
DeGraw DeBird
- Aircraft type
- Degraw DEBIRD
- Category
- Gyroplane
- 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
- N140DG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 27 years (built 1997)
- 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
- Unknown or undetermined
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot’s husband reported that his wife was conducting an evening pleasure flight in the accident gyroplane. He heard the gyroplane taxi to the runway and begin its takeoff. He said he did not hear anything unusual until he heard two loud thumps. The gyroplane was later located in a wooded area left of the departure runway. There were no witnesses to the accident and no flight track data was available. Examination of the gyroplane did not reveal any preimpact anomalies that would have precluded normal operations. The gyroplane’s tail surfaces were found separated from the rest of the gyroplane with unbroken trees between the resting location of the tail surfaces and the main wreckage. Additionally, impact marks and paint transfer on the rotor blades, tail, and tail boom were consistent with the main rotor blades impacting the tail. It is most likely that the main rotors impacted the tailboom which resulted in the separation of the tail. Main rotor blade contact with the tail would have rendered the gyroplane uncontrollable. Based on the design of the gyroplane, the rotor blades would have had to droop a significant amount in order to contact the tail boom. Without flight track, engine, or rotor speed data to assist the investigation, the reason that the main rotor blade contacted the tail boom could not be determined. The pilot’s postmortem toxicological testing indicated that the pilot had used the sedating antihistamine medication diphenhydramine. However, diphenhydramine testing in cavity blood was inconclusive. Based on these results, it was not possible to determine whether the pilot had used diphenhydramine recently enough to be experiencing impairing effects at the time of the accident
Probable cause
Separation of the gyroplane’s tail due to main rotor blade contact for reasons that could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24FA298
- Event ID
- 20240804194834
- Case number
- CEN24FA298
- 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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2024-08-04.
- API snapshot SHA-256: e1e3dc291a3ad169bec87fca7cdff7891fcaaa7816e7d0d2a29d79d7fb9d8cca; retrieved 2026-09-15T08:26:11.367Z.