ATL07LA111 · Piper PA-22-160
Piper PA-22-160 · Accident: forced landing
From St. Mary's County Regional Airport (2W6) to Bladenboro, NC
Event
- NTSB case
- ATL07LA111
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA-22-160
- Aircraft type
- Piper PA-22
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N2731P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From St. Mary's County Regional Airport (2W6), Leonardtown, MDTo Bladenboro, NC
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · emergency landing after takeoff
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Forced landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aborted takeoff, not performed
- Pilot in command › Performance data, not calculated
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
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.
Probable cause
The pilot's inadequate performance planning and failure to abort the takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL07LA111
- Event ID
- 20070814X01184
- Case number
- ATL07LA111
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 71e4f426c129200a5a34b61328af64c66191fd228c4f4925ac7f3e7538c51a06; retrieved 2026-09-20T16:22:56.941Z.