# NTSB ERA14LA388: Piper PA-28-161, N706GS, Buffalo, NY, August 14, 2014 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: August 14, 2014, 14:45 local (18:45 UTC) - Place: Buffalo, NY - Coordinates: 42.940555, -78.732223 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=42.9406&lon=-78.7322&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) - Highest injury: Minor injuries - Injuries: 1 minor, 2 uninjured - Status: Completed, report July 11, 2016 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO, Lycoming Engines, Prior Aviation Services Inc., Piper Aircraft Inc. - NTSB case key (mKey): 89885 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA14LA388 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/89885/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=89885 - Page: https://openairdocs.org/ntsb/ERA14LA388 ## Probable cause A total loss of engine power for reasons that could not be determined because a postaccident examination of the airframe and engine test run revealed no mechanical malfunctions or failures that would have precluded normal operation. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Piper PA-28-161, 14 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=7102803), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) (defining event); cases with it: [Piper PA-28-161, 22 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=7102803), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Piper PA-28-161, 19 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=7102803), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing-flare/touchdown: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-28-161, 58 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102803), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The flight instructor was providing an introductory flight to the passengers. Following an uneventful preflight inspection and engine run-up, the flight instructor prepared to depart. An air traffic controller offered, and the instructor accepted, an intersection takeoff that reduced the runway's 8,800-ft available takeoff length by about half. Shortly after rotation, the engine briefly lost all power. As the flight instructor attempted to troubleshoot the problem, the engine power was briefly restored, and she then decided to return to the airport and land. As she turned the airplane back toward the runway, the engine again lost total power. As the airplane's airspeed decreased, she chose to perform a forced landing to a parking lot, during which the airplane was substantially damaged. A postaccident engine test run revealed no anomalies, and examination of the airframe and fuel system revealed no mechanical malfunctions or failures. The reason for the loss of engine power could not be determined. ## Factual narrative On August 14, 2014, about 1445 eastern daylight time, a Piper PA-28-161, N706GS, was substantially damaged during a forced landing shortly after takeoff from Buffalo International Airport (BUF), Buffalo, New York. The flight instructor and two passengers were not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the local instructional flight, which was conducted under the provisions of Title 14 Code of Federal Regulations Part 91.The flight instructor was providing an introductory flight to both of the passengers, and following an uneventful preflight inspection and run-up check of the airplane's engine, began taxiing to the departure runway. During the taxi, air traffic control offered, and the flight instructor accepted, an intersection departure from runway 23 at its intersection with runway 14. The flight instructor subsequently guided the front seated passenger through the takeoff. Shortly after rotation, the engine experienced a total loss of power. The instructor responded by verifying that the throttle and mixture controls were both pushed fully forward. The engine then resumed producing power, and the instructor elected to return to the airport and land. As the flight instructor turned the airplane left toward runway 32, the engine again experienced a total loss of power. She attempted to restore engine power and verified the position of the throttle, mixture, and auxiliary fuel pump, but heard the aural stall warning sound. She then lowered the airplane's nose and decided to forgo troubleshooting the engine, as the airplane was close to the ground. During the subsequent forced landing, the airplane struck several bushes, and eventually landed hard in a parking lot adjacent to the airport, resulting in substantial damage to the airframe. The airplane was recovered from the accident site to the operator's maintenance facility for initial examination. Both wings remained attached to the fuselage, and the fuselage exhibited extensive damage to the left and right lower structure from the firewall aft to the aft bulkhead. Both of the propeller blades were damaged, with one blade tip bent slightly forward and the other bent slightly aft. The firewall and engine mounts were impact damaged, and the engine controls were not free to move, due to deformation of surrounding components. The fuel system to the engine was examined, and fuel was found within the engine-driven fuel pump, fuel boost pump, and fuel filter bowl, and the carburetor float bowl. A fuel sample was tested for the presence of water, none was noted. The fuel selector was found on the right tank position, and was free to move through all positions. The right wing was attached to the fuselage and the fuel tank was intact with its fuel cap installed. The right fuel tank vent was unobstructed. The left wing was partially attached to the fuselage, and the fuel tank was intact, with its fuel cap installed. Flight control continuity was confirmedfrom each control surface to the cockpit. The stabilator trim actuator was measured, and correlated to a slightly nose-up pitch trim setting. The rudder trim was fully nose right, as observed on the cockpit trim indicator. The flaps were found in the fully retracted position. While still attached to the airframe, an abbreviated engine test run was performed. The engine was started, allowed to idle, then the throttle was advanced. A heavy vibration was noted at any engine power setting above idle. The engine was then shut down and the propeller was replaced with a like-pitched and diameter propeller. The engine was then restarted and could be accelerated to an approximate setting slightly above 1,000-1500 rpm. Due to the un-balanced condition of the second propeller, the engine run was suspended without testing at any higher power setting. The engine was subsequently removed from the airframe and forwarded to the engine manufacturer for a full-power test run. After mounting in a test cell, the engine was started and run in accordance with the manufacturer's standard engine run-in procedure. The engine produced full rated power during the test, and no anomalies were noted. Following the test run, the carburetor was tested and examined in detail and tested in accordance with the manufacturer's standard procedures. No anomalies were noted during the testing or disassembly examinations. According to Federal Aviation Administration (FAA) airworthiness and aircraft registration records, the airplane was manufactured in September 2013. Review of maintenance records revealed that the airplane's most recent 100-hour inspection was completed on August 13, 2014. At that time the airframe and engine had accumulated 187 total hours of operation. No discrepancies of the engine were discovered during the inspection. The flight instructor held a commercial pilot certificate with numerous ratings including airplane single engine land. She also held a flight instructor certificate with a rating for airplane single engine. She held an FAA-issued first-class medical certificate, and her most recent flight review was completed in December 2013. She had accumulated 453 total hours of flight experience, of which 352 hours were in the accident airplane make and model. She had accumulated 51 hours of flight experience in the 30 days preceding the accident. The runway configuration at BUF resembled an 'X' layout. Runway 23 was 8,829 feet long by 150 feet wide, and was intersected by runway 14 about 4,175 feet from the runway 23 threshold. ## Aircraft - Registration: [N706GS](https://openairdocs.org/deregistered/N706GS-2015-05-26), registration cancelled 2015-05-26, S/N 2842391, built 2013 (OpenAirDocs) - Reported make and model: PIPER PA-28-161 - Registry model: [Piper PA-28-161](https://openairdocs.org/model/piper-pa-28-161) (registry code 7102803) (OpenAirDocs) - Registry engine: [Lycoming O-320-D3G](https://openairdocs.org/engine/lycoming-o-320-d3g) (registry code 42156, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 2842391 - Year built: 2013 - Airframe hours: 187 - Engines: LYCOMING O-320-D3G 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Prior Aviation Service Inc - Registered owner: Prior Aviation Service Inc - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, August 13, 2014, 0 hours before - Departed: BUF, Buffalo, NY - Destination: BUF, Buffalo, NY - Airport: BUF, Buffalo Niagara Intl, runway 23, 8,829 × 150 ft, asphalt - Equipment: Stall warning system, Electronic primary flight display, Electronic multifunction display ## Flight crew As NTSB recorded them. NTSB leaves out names. - Flight instructor; age 31; injuries: minor; flight instructor, private, commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review December 15, 2013; seat: right; restraint: 3-point; flight hours: 453 total, 352 in this make and model, 403 as pilot in command, 109 in the last 90 days, 51 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 260° at 16 knots, gusting 21 - Visibility: 10 statute miles - Lowest ceiling: 4,000 ft broken - Temperature: 64 °F, dew point 46 °F - Altimeter: 29.87 inHg - Observed at: KBUF ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20140814015749A](https://openairdocs.org/incident/20140814015749A), Aug 14, 2014: Piper PA-28-161, Buffalo, NY, Substantial damage. On August 14, 2014 at about 1450 hrs local time this aircraft departed runway 23 at the Buffalo Niagara International Airport with one pilot and two passengers… ## Docket (7 files) The files NTSB released with the investigation on May 31, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=89885. 4.9 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40440562&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Memorandum for Record - Telephone Interview, Flight Instructor (item 2, .PDF, 91 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40440563&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20-%20Telephone%20Interview,%20Flight%20Instructor-Master.PDF - Engine Test Run Results (item 3, .PDF, 477 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40440564&FileExtension=.PDF&FileName=Engine%20Test%20Run%20Results-Master.PDF - Carburetor Test Results (item 4, .PDF, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40440565&FileExtension=.PDF&FileName=Carburetor%20Test%20Results-Master.PDF - Engine Maintenance Logs (item 5, .PDF, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40440566&FileExtension=.PDF&FileName=Engine%20Maintenance%20Logs-Master.PDF - Statement of Party Representatives to NTSB Investigation (item 6, .PDF, 263 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40440567&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Master.PDF - Photo (Courtesy of FAA) (item 7, .PDF, 1 photo, 154 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40440568&FileExtension=.PDF&FileName=Photo%20(Courtesy%20of%20FAA)-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.