Remos Aircraft GMBH REMOS G-3/ accident near Sims, North Carolina, October 8, 2009
On October 8, 2009 at about 10:36 pm local time, a Remos Aircraft GMBH REMOS G-3/, registered N18241, was substantially damaged in an accident during enroute (cruise) near Sims, North Carolina. 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 pilot's failure to maintain altitude, resulting in controlled flight into water.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 8, 2009 · about 10:36 pm local time
- Place
- Sims, North Carolina · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Remos Aircraft GMBH REMOS G-3/ 2006
- Registration
- N18241 · no longer on the register · serial 182
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that he was flying above the reservoir at 500 feet approximately thirty minutes before sundown. As he completed a 180-degree turn, the sun was in his eyes. He put on a cap to block the sun from his eyes, and as he was adjusting the cap, the aircraft impacted the water. The pilot stated he “apparently relaxed the back pressure on the stick enough to lose altitude.” During the impact, the right wing incurred substantial damage. No preimpact malfunctions were reported by the pilot.
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
- Altitude deviation during enroute (cruise)
- Controlled flight into terrain or object (CFIT) during enroute (cruise) defining event
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Environmental issues › Conditions/weather/phenomena › Light condition › Glare › Effect on personnel
Pilot
- Certificate: private, sport pilot
- Ratings: single-engine land
- Flight time: 600 hours in all; 65 in this make and model; 6 in the last 30 days; 520 as pilot in command
- Last flight review: December 28, 2008
- Medical certificate: Sport Pilot (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 65 hours
- Last inspection: annual inspection, November 28, 2008; 25 hours since
- Maximum gross weight: 1,320 lb
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 912 UL-S (piston); 0 hours total
The flight
- Departed from: JNX Smithfield NC at 9:45 pm
- Destination: JNX Smithfield NC
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 66°F (19°C), dew point 55°F (13°C)
- Altimeter: 30.14 inHg
- Observation at 10:39 pm from JNX, 15 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.
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.
