GAA17CA401 · Robinson Helicopter Company R44 II
JMX Helicopters Robinson Helicopter Company R44 II · Accident: low altitude operation/event while maneuvering
From Sparta Community Airport - Hunter Field (SAR) to Washington, IN
Event
- NTSB case
- GAA17CA401
- 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 Helicopter Company R44 II
- 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
- N3203D
- Operator
- JMX Helicopters
- Onboard fatalities
- Unknown
- Route
- From Sparta Community Airport - Hunter Field (SAR), Sparta, ILTo Washington, IN
- Aircraft age
- About 12 years (built 2005)
- 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
- Maneuvering · low-altitude flying
- 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
- Low altitude operation/event
- 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 › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
***This report was modified on June 13,2018. Please see the docket for this accident to view the original report.***
The helicopter pilot reported that he was performing an agricultural application flight and was in a hurry to spray the field because of a previous 3-hour delay caused by a broken fuel truck. The pilot reported that the weight of the helicopter was 40 lbs below the helicopter's maximum gross weight and that he "approached the field with the understanding that I was heavier, and it was hotter and more windy than I originally planned for."
The pilot reported that the helicopter was headed south and that the wind was from the southwest about 15 knots. He made a low-altitude, low-airspeed, left turn to the north, and the helicopter entered a nose-low attitude and sank more rapidly than he anticipated. The pilot aborted the turn and chose to maintain a southeast heading to use the crosswind to avoid power lines. He attempted to arrest the sink rate by increasing the collective, but the low rotor rpm horn sounded.
The helicopter impacted the ground, bounced, and then rolled onto its left side. The helicopter sustained substantial damage to the tailboom and the main rotor system.
The nearest METAR was about 32 miles northwest of the accident site, and it reported, at the time of the accident, wind from 230° at 9 knots, gusting to 16 knots. The temperature was 88°F and the dew point was 20°F. The field elevation was 696 ft, and the density altitude was 2,786 ft.
According to the Federal Aviation Administration (FAA) Helicopter Flying Handbook, FAA-8083-21A (pg. 2-4, para. 5), "turns in a helicopter increase the load factor exponentially, ultimately increasing the power requirement that is necessary to maintain the helicopter's altitude. Left pedal turns increase the quantity of anti-torque produced by the tail rotor, by demanding additional power from the 245-brake horsepower engine. Pilot flight control inputs demanding more power than the engine is capable of producing, with respect to the atmospheric conditions, adversely affects the helicopter's ability to sustain its altitude. Available engine power is directly correlated to main and tail rotor RPM. When the engine fails to produce the required power to sustain airspeed and altitude at high DA [descent altitude], the main rotor blades will exceed their critical angle of attack, consequently decreasing main rotor blade RPM."
The pilot reported that there were no preaccident mechanical malfunctions or failures with the helicopter that would have precluded normal operation.
Probable cause
The pilot's decision to maneuver an overgross weight helicopter at a low altitude and airspeed with a gusting tailwind, which resulted in a high descent rate and collision with terrain. Contributing to the accident was the pilot's self-induced pressure to complete the operations due to a delay before the operations began.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA401
- Event ID
- 20170710X41152
- Case number
- GAA17CA401
- 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: 21f3546168ead94ce89ad9e2889fd718ca9657c2e6a104020813bf2437aefa7a; retrieved 2026-09-16T05:31:22.823Z.