Piper PA-22-160 accident near Leonardtown, Maryland, August 9, 2007
On August 9, 2007 at about 11:07 am local time, a Piper PA-22-160, registered N2731P, was destroyed in an accident near Leonardtown, Maryland (St Mary'S County Regional Airp airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed and 2 people had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's inadequate performance planning and failure to abort the takeoff.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 9, 2007 · about 11:07 am local time
- Place
- Leonardtown, Maryland · St Mary'S County Regional Airp · map
- Type
- Accident
- Injuries
- 1 person was killed and 2 people had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-22-160 · all PA-22-160s on the register
- Registration
- N2731P · no longer on the register · serial 22-3037
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot made a forced landing to an open field on initial takeoff climb. He informed the State Police that he was concerned about the weight of the airplane and the possible performance due to the hot weather. On takeoff, the airplane was slow to accelerate which he attributed to the hot and humid weather. The airplane used about 3,000 feet of runway before becoming airborne at 80 mph with an initial climb of about 50 feet per minute, "well below normal." As the airplane approached a tree line located about 1,500 feet from the end of the runway, the airplane was no longer able to climb and began a descent. The pilot stated that the airplane was at full power, he lowered one notch of flaps, just before reaching the tree line, then he lowered the flaps to the full down position, the airplane skimmed the top of the trees, collided with the ground in a nose down right wing low attitude, and caught fire destroying the airplane. He stated that the gross weight of the airplane was 2,000 pounds, and he did not conduct any formal performance planning for the flight except for mentally going over the weight and balance in his head. In addition, the pilot did not consider that density altitude and pressure altitude was a factor since he was departing from a 4,000-foot runway. The weight and balance was computed using the empty weight and three different baggage weights provided to the State Police, FAA, and NTSB by the pilot, and the empty weight provided by the aircraft manufacturer. The takeoff weight in all three computations ranged from 1,816 pounds to 1,981 pounds. The departure airport is located at an elevation of 142 feet, and the departure runway is 4,150 feet in length. The temperature at the departure airport was 82-degrees Fahrenheit, dew point temperature was 72-degrees Fahrenheit, and the altimeter was 29.88. The density altitude at the time of the accident was 1,755 feet and the pressure altitude was 180 feet. The manufacturer stated that with flaps extended the performance figures were for standard airplanes flown at gross weight under standard conditions at sea level. The takeoff run is 1,220 feet and the takeoff over a 50-foot barrier is 1,600 feet. With a density altitude of 1,755 feet the takeoff run will increase approximately 25 percent for every 1,000 feet increase in density altitude. The takeoff run would have been approximately 43 percent longer or 1,745 feet and 2, 288 feet to clear a 50-foot obstacle. Had the pilot performed written calculations for the weight and balance and density altitude for the departure airport he would have known that his takeoff distance would have increased due to the environmental conditions at the time of accident; thus, he could have selected a go or no go point on the runway to abort the takeoff. Post accident inspection disclosed no evidence of any pre-impact mechanical anomalies.
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
- Certificate: private
- Ratings: single-engine land
- Flight time: 1,000 hours in all; 400 in this make and model; 20 in the last 90 days; 8 in the last 30 days; 1,000 as pilot in command
- Last flight review: April 1, 2006
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: minor injuries
Crew member
No details recorded.
The aircraft
- Airframe total time: 1,958 hours
- Last inspection: annual inspection, February 1, 2006; 20 hours since
- Maximum gross weight: 2,000 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320-B2A (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: 2W6 Leonardtown MD at 11:06 am
- Destination: Bladenboro NC
- Flight plan: none
- Runway 29, 4,150 ft by 75 ft
Weather at the time
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 82°F (28°C), dew point 72°F (22°C)
- Altimeter: 29.87 inHg
- Observation at 11:01 am from 2W6
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 | |||
| Passengers | 1 | 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.
