7 Jun 2014: PIPER PA-28-140

7 Jun 2014: PIPER PA-28-140 (N5169T) — Unknown operator

No fatalities • Newport, VT, United States

Probable cause

The pilot's failure to maintain adequate airspeed during an aborted landing, which resulted in an aerodynamic stall and collision with the ground. Contributing to the accident was the pilot's alcohol impairment.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHTOn June 7, 2014, at approximately 1700 eastern daylight time, a Piper PA-28-140, N5169T, was substantially damaged during a balked landing at Newport State Airport (EFK), Newport, Vermont. The private pilot and pilot rated passenger were not injured. Visual meteorological conditions prevailed and no flight plan was filed for the local personal flight, conducted under the provisions of Title 14 Code of Federal Regulations Part 91.

According to the pilot, he first attempted a landing which resulted in him having to execute a go-around. During his second attempted landing he stated that on final approach he was "too high and fast." During the landing flare, the airplane floated in ground effect, and touched down approximately 3,000 feet down the runway. The pilot then applied full power to abort the landing. The pilot stated at approximately 900 feet agl the engine lost all power.

According to the passenger he was not at the controls of the aircraft during the final landing. Mr. Booth stated that the he did not remember the engine failing during the accident sequence. He also said that Mr. Quirion told Mr. Booth before the flight that he would assume the pilot in command responsibilities since he was the one who owned the airplane. Mr. Booth also confirmed that Mr. Quirion had left the scene of the accident immediately after the crash. Mr. Booth could not confirm that Mr. Quirion had consumed any alcohol prior to the flight.

Immediately after the accident the pilot exited the wreckage was observed leaving the airport.

According to a witness, the airplane pitched up abruptly, and climbed to an altitude of approximately 200 feet above ground level (agl). The airplane then banked left and settled back towards the ground. The airplane subsequently impacted terrain north of the departure end of runway 36. The witness also stated that the engine was running up to the point of impact. PERSONNEL INFORMATIONAccording to Federal Aviation Administration (FAA) and pilot records the pilot held a private pilot certificate with a rating for airplane single-engine land. At the time of the accident he did not possess an FAA medical certificate. The pilot reported that he had accrued 604 hours of total flight experience, of which 525 were in the accident airplane make and model.

According to FAA records the pilot rated passenger held a private pilot certificate with a rating for airplane single-engine land. He received a third class medical October 1, 2012. AIRCRAFT INFORMATIONAccording to the FAA, the airplane was issued a standard airworthiness certificate on May 1, 1972. The airplane was purchased by the pilot on February 22, 2006.

The airplane's registration had expired on May 31, 2014, approximately 7 days prior to the accident.

Despite requests by the FAA and NTSB, no maintenance records were provided by the pilot/owner. A review of FAA airworthiness records indicated as of April 1, 1992 the airplane had accrued 3,183 total hours of operation. METEOROLOGICAL INFORMATIONAt 2055 the ecorded weather at EFK included, wind 300 degrees at 7 knots, visibility 10 statute miles, scattered clouds at 7,500 feet, temperature 24 C, dewpoint 10 C, and altimeter setting of 29.95 inches of mercury. AIRPORT INFORMATIONAccording to the FAA, the airplane was issued a standard airworthiness certificate on May 1, 1972. The airplane was purchased by the pilot on February 22, 2006.

The airplane's registration had expired on May 31, 2014, approximately 7 days prior to the accident.

Despite requests by the FAA and NTSB, no maintenance records were provided by the pilot/owner. A review of FAA airworthiness records indicated as of April 1, 1992 the airplane had accrued 3,183 total hours of operation. WRECKAGE AND IMPACT INFORMATIONThe airplane came to rest upright in a field approximately 850 feet off the end of runway 36. Examination of the accident site revealed multiple propeller strike marks in the ground leading up to the main wreckage.

During examination of the wreckage, no evidence of any preimpact failures or malfunctions of the airplane were discovered.

Examination of the wreckage revealed that the nose landing gear and right main landing gear had collapsed and the left main landing gear had separated from the airplane. The airplane's fuselage structure was substantially damaged.

The propeller of the aircraft exhibited evidence of rotation. The propeller tips were twisted and exhibited chordwise scratching.

Examination of the engine revealed there was no evidence of any preimpact failures or malfunctions that would have precluded normal engine operation. A cold engine compression check was conducted and no anomalies were found. The damaged propeller was replaced and an engine start and run-up was conducted using the same fuel that was onboard the airplane at the time of the accident. The engine was first run at 1500 RPM for approximately 3 minutes and was then shut down. A second startup was conducted and the engine power was subsequently increased to 2300 RPM. At that time the power was reduced to 2100 RPM and a magneto check was conducted and no anomalies were noted. ADDITIONAL INFORMATIONAccording to a witness, on the morning of the accident she observed the pilot consume 12 to 16 alcoholic beverages between 0745 and 1230, then the pilot left to meet his passenger for the flight.

According to an FAA inspector, after the accident the Vermont State Police made contact with the pilot at his residence where he refused a breathalyzer test.

Contributing factors

  • cause Airspeed — Not attained/maintained
  • cause Pilot
  • factor Pilot

Conditions

Weather
VMC, wind 300/07kt, 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.