Piper PA-28R-200 accident near Dover, Delaware, January 13, 2013
On January 13, 2013 at about 11:45 pm local time, a 1970 Piper PA-28R-200, registered N4975S, was substantially damaged in an accident during approach (IFR final approach) near Dover, Delaware (Dover Air Force Base airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The pilot's failure to land the airplane at multiple airports that were equipped with adequate instrument approach procedures while operating in low instrument meteorological conditions and his delay in declaring a fuel-related emergency, which resulted in a loss of engine power due to fuel exhaustion.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 13, 2013 · about 11:45 pm local time
- Place
- Dover, Delaware · Dover Air Force Base · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Piper PA-28R-200, built 1970 · all PA-28R-200s on the register
- Registration
- N4975S · no longer on the register · serial 28R-35693
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot had planned a night instrument cross-country flight of 3 hours 45 minutes, with 5 hours 30 minutes of fuel onboard. About 3 hours 20 minutes into the flight, when the airplane was approximately 15 miles from the intended destination airport, the pilot diverted as the airplane ahead of him had to perform a missed approach due to a low cloud ceiling. The pilot diverted to a nearby airport with calm wind and an instrument landing system (ILS) approach; however, he attempted two GPS approaches to the opposite end of the 6,400-foot-long runway. He performed a missed approach on both GPS approaches before reaching the decision altitude of 306 feet above ground level (agl), when an overcast ceiling at 400 feet prevailed. The pilot did not attempt the ILS approach. The pilot then diverted a second time, about 4 hours 20 minutes into the flight, to an airport that was not equipped with an ILS approach. He performed a GPS approach to that airport, down to about 250 feet GPS altitude, which was below the published minimum descent altitude of 310 feet agl, when an overcast ceiling of 300 feet prevailed, which resulted in a missed approach. After the missed approach, about 5 hours into the flight, the pilot reported to air traffic control that he was low on fuel. The pilot then diverted for a third time, to another airport that did not have an ILS approach, but he planned to attempt a VOR approach at that airport. The pilot could have declared an emergency and performed an ILS approach to a military airport that he overflew enroute to the VOR approach, and was in radio and radar contact with; however, he continued on and was cleared for the VOR approach about 5 hours 5 minutes into the flight and declared emergency 6 minutes later, reporting fuel exhaustion. At that time, the airplane was provided radar vectors to the military airport, but impacted wooded terrain about 2 miles prior to the runway.
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
- Fuel exhaustion during approach (IFR final approach) defining event
- Loss of engine power (total) during approach (IFR final approach)
- Off-field or emergency landing during emergency descent
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- cause Personnel issues › Action/decision › Action › Delayed action › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 598 hours in all; 537 in this make and model; 31 in the last 90 days; 15 in the last 30 days
- Last flight review: July 1, 2012
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 5,613 hours
- Last inspection: annual inspection, June 2, 2012
- Maximum gross weight: 2,650 lb
- Seats: 4
- Landing gear: retractable
- Engine: Lycoming IO-360 (piston); 1,088 hours total
The flight
- Departed from: OKZ Sandersville GA at 6:30 pm
- Destination: EVY Middletown DE
- Flight plan: IFR
Weather at the time
- Light: night
- Wind: from 330° at 3 knots
- Visibility: 4 statute miles
- Sky: overcast at 400 ft
- Temperature: 46°F (8°C), dew point 46°F (8°C)
- Altimeter: 30.04 inHg
- Observation at 11:42 pm from DOV, 2 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.