Piper PA-28-161 accident near Benton, Pennsylvania, January 3, 2011
On January 3, 2011, a Piper PA-28-161, registered N42997, was substantially damaged in an accident during enroute (cruise) near Benton, Pennsylvania. It was an instructional flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain clearance from terrain during the night flight.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 3, 2011
- Place
- Benton, Pennsylvania · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Piper PA-28-161 · all PA-28-161s on the register
- Registration
- N42997 · no longer on the register · serial 28-8316062
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The instrument-rated pilot was on the return leg of a three-leg cross country flight at night when he encountered clouds in his path. He considered climbing above the clouds, but he was concerned that he would not be able to descend back down through them. He elected to descend below the clouds, and misjudged the distance between the clouds and the ground. The airplane collided with trees and terrain at an elevation of about 2,200 feet in a remote, wooded area. The airplane sustained substantial damage by impact forces and post-crash fire. The pilot reported he did not see the trees or the terrain prior to the collision. Additionally, he stated that there were no mechanical issues with the airplane during the flight.
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
- VFR encounter with IMC during enroute (cruise)
- Controlled flight into terrain or object (CFIT) during enroute (cruise) defining event
The NTSB's findings
- factor Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Clouds › Contributed to outcome
- cause Personnel issues › Action/decision › Action › Incorrect action selection › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 170 hours in all; 170 in this make and model
- Last flight review: July 17, 2010
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: serious injuries
The aircraft
- Airframe total time: 11,625 hours
- Last inspection: annual inspection, December 3, 2010
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320 SER (piston); 0 hours total
- Fire on the ground
- Operator: Tech Aviation Flight School
The flight
- Departed from: IPT Williamsport PA at 11:00 pm
- Destination: AVP Wilkes-Barre PA
- Flight plan: none
Weather at the time
- Light: night
- Wind: from 340° at 7 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 2,600 ft
- Temperature: 36°F (2°C), dew point 27°F (-3°C)
- Altimeter: 29.96 inHg
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.