Amateur-built ROTORWAY 162F accident near Dallas, Georgia, April 23, 2010
On April 23, 2010 at about 5:00 pm local time, a amateur-built ROTORWAY 162F (helicopter), registered N831MS, was substantially damaged in an accident during landing near Dallas, Georgia (Paulding County Regional airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The student pilot's failure to maintain control of the helicopter during landing resulting in a roll over.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 23, 2010 · about 5:00 pm local time
- Place
- Dallas, Georgia · Paulding County Regional · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built ROTORWAY 162F
- Registration
- N831MS · registry record · serial 6887
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The student helicopter pilot reported that he was practicing hovering, pedal turns, and ground taxiing in the ramp area. As he slowed for landing at the conclusion of the flight, the helicopter settled more than he anticipated and the right skid touched the pavement. The student pilot immediately lost control of the helicopter and the helicopter rolled onto its side, incurring substantial damage. The student pilot did not report any anomalies with the helicopter prior to the accident.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Abnormal runway contact during landing
- Dynamic rollover during landing defining event
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student pilot
Dual student
- Certificate: private, student
- Ratings: single-engine land
- Flight time: 285 hours in all; 15 in this make and model; 3 in the last 90 days; 3 in the last 30 days; 189 as pilot in command
- Last flight review: September 21, 2007
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 9 hours
- Last inspection: condition inspection, February 8, 2009; 9 hours since
- Maximum gross weight: 1,500 lb
- Seats: 2
- Landing gear: fixed
- Engine: Rotorway RI 162F (piston); 0 hours total
The flight
- Departed from: PUJ Dallas GA
- Destination: PUJ Dallas GA
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 210° at 7 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 81°F (27°C), dew point 50°F (10°C)
- Altimeter: 29.95 inHg
- Observation at 4:53 pm from VPC, 14 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Other NTSB records under N831MS the same tail number, which may have belonged to a different aircraft at the time
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.