The U.S. aircraft register, updated daily
Accidents · NTSB IAD03LA054 · Final report

Amateur-built Ragwing RW8-PT2S accident near Hanover, Virginia, April 21, 2003

On April 21, 2003, a amateur-built Ragwing RW8-PT2S, registered UNREG, was substantially damaged in an accident near Hanover, Virginia. It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A loss of engine power for undetermined reasons. A factor was the wheat in the forced landing field.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
April 21, 2003
Place
Hanover, Virginia · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Amateur-built Ragwing RW8-PT2S
Registration
UNREG · no longer on the register · serial None
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The non-certificated pilot was maneuvering his unregistered airplane at low altitude when the engine lost power. The pilot performed a forced landing to a wheat field, and the airplane flipped over when it became entangled in the wheat. Post-flight examination of the airplane revealed a non-standard fuel source, but there was no evidence that it negatively affected engine operation. In addition, no engine anomalies were found.

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

Pilot

  • Flight time: 1,400 hours in all; 10 in this make and model
  • Medical certificate: None
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Last inspection: inspection type not recorded
  • Maximum gross weight: 440 lb
  • Seats: 1
  • Landing gear: fixed
  • Engine: Rotax 503 (piston); 0 hours total

The flight

  • Departed from: VA50 Hanover VA at 9:30 pm
  • Flight plan: none
  • Runway 15, 2,200 ft by 80 ft

Weather at the time

  • Light: daylight
  • Wind: at 0 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 59°F (15°C), dew point 48°F (9°C)
  • Altimeter: 30.14 inHg
  • Observation at 10:54 pm from KOFB, 7 miles away

Injuries

FatalSeriousMinorNone
Crew1

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 UNREG the same tail number, which may have belonged to a different aircraft at the time

2026-07-07CEN26LA246 · accident near Hooker, OK · substantial damage · minor injuries
2026-02-28CEN26LA131 · accident near Van Burensburg, IL · substantial damage · no injuries
2025-10-13ERA26LA017 · accident near Gaffney, SC · substantial damage · serious injuries
2025-09-27CEN25LA397 · accident near Harvard, IL · substantial damage · no injuries
2025-09-12CEN25LA385 · accident near Rossville, IN · substantial damage · serious injuries
2025-07-07CEN25LA242 · incident near Ingram, TX · minor damage · no injuries
2025-06-18DCA25WA305 · accident near N/A · serious injuries
2025-05-01OPS25LA034 · incident near Washington, DC
2025-04-11CEN25LA155 · accident near Brady, TX · substantial damage · serious injuries
2025-01-30DCA25MA108 · accident near Washington, DC · destroyed · fatal

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.