DFW06CA066 · Robinson R44
Robinson R44 · Accident: hard landing during takeoff
From Rayville, LA to an unrecorded destination
Event
- NTSB case
- DFW06CA066
- 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
Robinson R44
- Aircraft type
- Robinson R44
- 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
- N744MD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rayville, LATo not recorded
- 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
- 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
- Hard landing
- 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
- Pilot in command › Rotor RPM, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 673-hour private pilot, who reported having accumulated 120 hours in the same make and model helicopter reported that while departing on his third flight of the day, into the wind, when approximately 40-feet above ground level (AGL) the helicopter suddenly "veered" to the right. As the pilot responded by applying full left anti-torque pedal, the low rotor RPM warning horn sounded. The pilot then lowered the collective control and applied aft cyclic control. With the helicopter quickly settling, the pilot pulled-up on the collective control; however, he was not able to arrest the high rate of descent. The helicopter landed hard and managed to remain in the upright position. The pilot and two passengers were uninjured. The pilot reported that at the time of the accident, the temperature was 60 degrees Fahrenheit and the winds were from 300 degrees at 10 knots.
Probable cause
The pilot's failure to maintain rotor RPM, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW06CA066
- Event ID
- 20060302X00262
- Case number
- DFW06CA066
- 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, 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: e52b1bd1901664795d83c3b31efc1efddf680f44243af2eced33b523597d241c; retrieved 2026-09-22T05:07:28.004Z.