6 Aug 2017: PIPER PA28 140

6 Aug 2017: PIPER PA28 140 (N56884) — Unknown operator

No fatalities • Pittstown, NJ, United States

Probable cause

The student pilot's improper decision to conduct a night flight and his failure to maintain adequate altitude during the approach, which resulted in controlled flight into trees and terrain. Contributing to the accident was the student pilot's lack of total and recent night flight experience.

— NTSB Determination

Accident narrative

On August 5, 2017, about 2230 eastern daylight time, a Piper PA-28-140, N56884, owned and operated by the student pilot, was substantially damaged during a collision with trees and terrain, while on approach to Sky Manor Airport (N40), Pittstown, New Jersey. The student pilot and one passenger were seriously injured, while a second passenger sustained minor injuries. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Night visual meteorological conditions prevailed and a visual flight rules flight plan was filed for the flight that departed Blairstown Airport (1N7), Blairstown, New Jersey, about 2210.Due to his injuries, the student pilot did not recall the accident sequence. He reported a total flight experience of 105 hours, of which, 5 hours were at night. The student pilot had not flown during the 90-day period preceding the accident. The front seat passenger stated that he and the student pilot previously spoke several times about flying the airplane to N40 for required equipment (avionics) installation. The front seat passenger was also seriously injured and remembered only some of the accident sequence. He recalled the student pilot saying, "we are losing altitude, this is not good."

The rear seat passenger sustained minor injuries and recalled that the student pilot stated they had to complete a 360° turn before landing. The student pilot then adjusted the wing flaps and the rear seat passenger saw a red blinking light, powerlines, and trees. The student pilot then stated that they needed to climb, but they were not climbing. The student pilot subsequently remarked that he thought he saw the problem and adjusted the wing flaps again. The rear seat passenger did not recall the impact.

Review of radar data and air traffic control (ATC) communications provided by the Federal Aviation Administration (FAA), revealed that the airplane was at 3,500 feet mean sea level (msl) when the student pilot reported beginning a descent to ATC at 2224. The airplane flew a track consistent with an approximate 3-mile left base leg to final leg of the airport traffic pattern for runway 7, at N40. While on final approach, the airplane descended from about 2,300 feet msl to 1,300 feet msl as it neared the runway threshold (which was at 548 feet msl). The airplane then completed a right 360° turn and the last radar target was recorded over the airport about 2230, indicating a groundspeed of 70 knots and an altitude of 1,000 feet msl.

The wreckage was located about 1/2-mile beyond the departure end of runway 7 and had been partially consumed by a postcrash fire. Examination of the wreckage by an FAA inspector did not reveal any preimpact mechanical malfunctions. The inspector was able to rotate the crankshaft by hand and confirm camshaft, crankshaft, and valve train continuity to the rear accessory section of the engine. He also attained thumb compression on all four cylinders. The inspector added that the passengers were not certificated pilots.

The student pilot's flight instructor reported that the student pilot attempted to schedule a lesson for August 4, 2017, to gain proficiency; however, the flight instructor already had a commitment. The student pilot then scheduled the flight instructor for August 10, 2017. The flight instructor added that he last provided ground instruction to the student pilot on February 18, 2017, and the student pilot subsequently completed a solo cross-country flight uneventfully during the same day.

The recorded weather at an airport located about 12 miles east of the accident site, at 2253, included calm wind, clear sky and visibility 10 miles.

Contributing factors

  • cause Altitude — Not attained/maintained
  • cause Pilot
  • cause Student/instructed pilot
  • factor Student/instructed pilot
  • cause Effect on operation
  • factor Student/instructed pilot
  • Effect on personnel

Conditions

Weather
VMC, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.