Piper PA-22-160 N2731P
9 August 2007 · Leonardtown, Maryland, United States · Fatal
Summary
On 9 August 2007 at about 11:07 local time, a Piper PA-22-160 registered N2731P was involved in an accident near Leonardtown, Maryland, United States. 3 people were on board and one died, 2 had minor injuries. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 11:07
- Classification
- Accident
- Location
- Leonardtown, Maryland, United States
- Nearest airport
- ST Mary's County Regional Airp (K2W6)
- Coordinates
- 38.3083, -76.5611
- Aircraft
- Piper PA-22-160
- Registration
- N2731P
- Category
- Airplane
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Leonardtown → Bladenboro
- Aircraft damage
- Destroyed
- Weather
- VMC
- NTSB number
- ATL07LA111
People
1 person died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 3 | 1 | 0 | 2 | 0 |
Probable cause
The pilot's inadequate performance planning and failure to abort the takeoff.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
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.
Quoted verbatim from the NTSB record.
Other Piper PA-22 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 26 Dec 2007 | Piper PA-22-150 | North Pole, Alaska, United States | Forest M. Kirst | No injuries | - |
| 24 Apr 2007 | Piper PA-22 | Soldotna, Alaska, United States | - | No injuries | - |
| 29 Oct 2007 | Piper PA-22-150 | Canon City, Colorado, United States | - | No injuries | - |
| 23 Feb 2007 | Piper PA-22-150 | Fort Pierce, Florida, United States | - | No injuries | - |
| 4 May 2007 | Piper PA-22 | Chiloquin, Oregon, United States | - | Serious injuries | - |
| 16 Apr 2007 | Piper PA-22-108 | Ava, Missouri, United States | - | Fatal | 1 |
All 3,095 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 24 Aug 2007 | Iniziative Industriali Italian SKY AERO 600 SPORT | Stevensville, Maryland, United States | - | No injuries | - |
| 25 Apr 2007 | Boeing 737-300 | La Plata, Maryland, United States | - | Serious injuries | - |
| 29 Apr 2007 | Flight CTSW | Fort Meade, Maryland, United States | - | Minor injuries | - |
| 25 Aug 2007 | McNicholas S-12 | Cambridge, Maryland, United States | Robert C. Hill | Serious injuries | - |
| 4 May 2007 | Piper PA38-112 | Odenton, Maryland, United States | - | Serious injuries | - |
| 24 Mar 2007 | Piper PA-32R-301 | Jacksonville, Maryland, United States | Theodore Charles Ryder | Fatal | 3 |