CEN20CA313 · Robinson R44
MF Helicopters Robinson R44 · Accident: collision during takeoff/landing
From Dakota, IL to Dakota, IL
Event
- NTSB case
- CEN20CA313
- 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
- N570WH
- Operator
- MF Helicopters
- Onboard fatalities
- Unknown
- Route
- From Dakota, ILTo Dakota, IL
- Aircraft age
- About 22 years (built 1998)
- 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 137: Agricultural
- 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
- Landing
- 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
- Collision during takeoff/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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he repositioned the helicopter to load application chemical for the aerial application flight. The chemical was in a tank in a hay wagon and the tops of the hay wagon curved outward. He "slowly" set the helicopter down and felt the left skid touch followed by the right skid. The pilot lowered collective after the helicopter touched down and the main rotor blade struck the hay wagon. The helicopter "jumped" and shook violently. Both left and right windshields ejected from the helicopter and the main rotors came to a stop. The pilot attempted to shut down the engine; however, the engine continued to run. He exited the helicopter and applied the fuel cutoff. The helicopter sustained substantial damage to the main and tail rotors, the skids, and the helicopter "frames." The pilot reported that there was no mechanical malfunctions or failures with the helicopter that would have precluded normal operation. His safety recommendation stated that when setting the helicopter down near obstacles, recheck rotor clearance before fully lowering collective and be mindful that "the blades will move out of cone."
Probable cause
The pilot’s failure to maintain main rotor clearance from a ground obstacle during a landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20CA313
- Event ID
- 20200727X61210
- Case number
- CEN20CA313
- 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: ad8b71f506e85a06321f696543afcab86e514f14522d8aaeaee6c80266e5cea6; retrieved 2026-09-16T12:17:28.186Z.