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

Beech P35 accident near Edgewater, Maryland, February 27, 2010

On February 27, 2010 at about 9:25 pm local time, a Beech P35, registered N1521S, was substantially damaged in an accident during approach (VFR pattern final) near Edgewater, Maryland (Lee airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain adequate airspeed while on approach, which resulted in an inadvertent stall. Contributing to the accident was the pilot's likely impairment due to back pain, symptoms of opiate withdrawal, or both.

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

What the record shows

Date
February 27, 2010 · about 9:25 pm local time · cases in 2010
Place
Edgewater, Maryland · Lee · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Beech P35 · all P35s on the register
Registration
N1521S · registry record · serial D-6963
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The airplane was on final approach to land about 300 feet above the ground, when it stalled, banked right, and descended into trees about 1/2 mile from the approach end of the runway. A postcrash fire destroyed the cockpit and consumed a majority of the airframe. The engine separated and was located in a creek, about 100 feet east of the main wreckage. Examination of the wreckage did not reveal any preimpact malfunctions. It was noted that while witnesses reported they observed the airplane's landing gear and flaps extended during the beginning of the accident sequence, postaccident observations were consistent with the landing gear and flaps in the retracted position. The pilot had a history consistent with alcohol and prescription drug dependence, and had at least once previously failed rehabilitation treatment. He had been experiencing worsening back pain, and had undergone surgery about 6 weeks prior to the accident, with continuing pain after the surgery. He had been using prescription narcotic medications from multiple different providers for over a year prior to the accident, most recently filling a large prescription for prescription narcotic medications 3 days prior to the accident. Postmortem toxicology testing was consistent with recent use of a prescription anti-depressant, also used to treat nicotine dependence that can increase the likelihood of seizure activity, though that risk remains low. Toxicology testing also was consistent with the relatively recent use of a prescription narcotic medication, but the lack of such medication in the pilot's blood suggests the possibility that the pilot may have been experiencing the effects of opiate withdrawal, which can include agitation, anxiety, nausea, and abdominal cramping, among other symptoms. The pilot may also have been distracted by back pain. The FAA failed to identify the pilot's substance dependence, in spite of substantial differences in his and police reports regarding a Driving Under the Influence charge in 2005, and publicly available records that documented his misuse of prescription medications.

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

  1. Loss of control in flight during approach (VFR pattern final) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • factor Personnel issues › Physical › Impairment/incapacitation › (general) › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,125 hours in all; 185 in this make and model; 8 in the last 90 days; 3 in the last 30 days
  • Last flight review: January 15, 2010
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Last inspection: annual inspection, February 26, 2010
  • Maximum gross weight: 3,125 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Cont Motor IO-470 SERIES (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: ANP Annapolis MD at 9:05 pm
  • Destination: ANP Annapolis MD
  • Flight plan: VFR
  • Runway 30, 2,500 ft by 48 ft

Weather at the time

  • Light: daylight
  • Wind: from 280° at 9 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 43°F (6°C), dew point 21°F (-6°C)
  • Altimeter: 29.62 inHg
  • Observation at 9:54 pm from NAK, 5 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

23 documents, released by the NTSB on September 9, 2011. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Witness Statements PDF, 8 pages View Download
2 Aircraft Bill of Sale PDF, 1 page View Download
3 FAA radar Data PDF, 2 pages View Download
4 Wreckage Diagram (Provided by Maryland State Police) PDF, 1 page View Download
5 Pilot Logbook (Excerpts) PDF, 11 pages View Download
6 Aircraft Maintenance Records PDF, 13 pages View Download
7 U.s. Naval Academy Annapolis Weather Observations PDF, 1 page View Download
8 Airplane Flight Manual (Excerpts) PDF, 3 pages View Download
9 Engine Data Monitor (EDM) - Specialist's Factual Report PDF, 3 pages View Download
10 Medical Records Information PDF, 6 pages View Download
11 Statement of Party Representatives to NTSB Investigation PDF, 1 page View Download
12 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page View Download
13 FAA Toxicology Report PDF, 2 pages View Download
14 Photograph # 1 – Main Wreckage as It Came to Rest. PDF, 1 page View Download
15 Photograph # 2 – View Facing East-northeast of Main Wreckage. Note the Airplane's Engine Came to Rest in the Body of Water Visible in the Background. PDF, 1 page View Download
16 Photograph # 3 – View of Airplane Center Section PDF, 1 page View Download
17 Photograph # 4 – View of A Empennage, with Separated Pilot Seat and Separated Portion of the Nose Gear Assembly Also Visible. PDF, 1 page View Download
18 Photograph # 5 – Close-up View of Separated Nose Section with Gear Assembly. PDF, 1 page View Download
19 Photograph # 6 – View of Engine After It Was Recovered from the Water. PDF, 1 page View Download
20 Photograph # 7 – View of Engine in Hanger (Note Engine Is in an Inverted Position) PDF, 1 page View Download
21 Photograph # 8 – View of 1-3-5 Side of Engine Cylinder Assemblies. PDF, 1 page View Download
22 Photograph # 9 – View of 2-4-6 Side of Engine Cylinder Assemblies. PDF, 1 page View Download
23 Photograph # 10 - View of Propeller PDF, 1 page View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA10FA154.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.