# NTSB ERA16FA329: Cessna 172, N52126, Laytonsville, MD, September 27, 2016

- Type: NTSB accident investigation
- Classification: Accident · Fatal · Field investigation · Final report
- Date: September 27, 2016, 18:30 local (22:30 UTC)
- Place: Laytonsville, MD
- Coordinates: 39.235553, -77.13639 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=39.2356&lon=-77.1364&mi=10
- Phase of flight: [Emergency descent](https://openairdocs.org/ntsb-phases/600) (OpenAirDocs' grouping)
- Defining event: [Emergency descent: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241)
- Highest injury: Fatal
- Injuries: 1 fatal
- Status: Completed, report August 9, 2017
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA, Textron, Lycoming
- NTSB case key (mKey): 94092
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA16FA329
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/94092/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=94092
- Page: https://openairdocs.org/ntsb/ERA16FA329

## Probable cause

The pilot/mechanic's failure to maintain airspeed following a loss of engine power, which resulted in the airplane exceeding its critical angle of attack and experiencing an aerodynamic stall. Also causal was the pilot/mechanic's failure to service the engine with oil following maintenance, which resulted in the total loss of engine power.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172P, 76 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072436), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Action: forgotten action/omission](https://openairdocs.org/ntsb-findings/02041035): Personnel issues › Action/decision · Maintenance personnel (probable cause); cases with it: [Cessna 172P, 2 cases](https://openairdocs.org/ntsb-findings/02041035/cases.md?model=2072436), [All aircraft, 440 cases](https://openairdocs.org/ntsb-findings/02041035/cases.md)
- [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172P, 7 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=2072436), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md)
- [Performance/control parameters: angle of attack](https://openairdocs.org/ntsb-findings/01062042): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172P, 3 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md?model=2072436), [All aircraft, 990 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md)
- [Fluids: oil](https://openairdocs.org/ntsb-findings/01071020): Aircraft › Fluids/misc hardware · Incorrect service/maintenance (probable cause); cases with it: [Cessna 172P, 2 cases](https://openairdocs.org/ntsb-findings/01071020/cases.md?model=2072436), [All aircraft, 174 cases](https://openairdocs.org/ntsb-findings/01071020/cases.md)
- [Fluids: oil](https://openairdocs.org/ntsb-findings/01071020): Aircraft › Fluids/misc hardware · Not installed/available (probable cause); cases with it: [Cessna 172P, 2 cases](https://openairdocs.org/ntsb-findings/01071020/cases.md?model=2072436), [All aircraft, 174 cases](https://openairdocs.org/ntsb-findings/01071020/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Prior to flight: Aircraft maintenance event](https://openairdocs.org/ntsb-events/040); cases with it: [Cessna 172P, 2 cases](https://openairdocs.org/ntsb-events/040/sequence.md?model=2072436), [All aircraft, 484 cases](https://openairdocs.org/ntsb-events/040/sequence.md)
- [Enroute: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341); cases with it: [Cessna 172P, 14 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=2072436), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md)
- [Emergency descent: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241) (defining event); cases with it: [Cessna 172P, 10 cases](https://openairdocs.org/ntsb-events/241/sequence.md?model=2072436), [All aircraft, 1,529 cases](https://openairdocs.org/ntsb-events/241/sequence.md)

## Analysis

Earlier on the day of the accident, the pilot/mechanic flew the airplane from its home base airport to another airport to perform scheduled maintenance. Airport security video captured the entire maintenance event and showed the pilot/mechanic removing the engine cowling, draining the engine oil, and inspecting the spark plugs, air filter, and other components. The video did not show him adding engine oil before reinstalling the engine cowling and departing on the accident flight. Shortly after takeoff, the pilot reported to an air traffic controller that the airplane's engine was losing power and that he was returning to the airport. Witnesses reported that the airplane began to fly erratically, rolled into a steep bank, and descended to ground impact about 1 mile from the airport. The witness observations were consistent with the pilot failing to maintain airspeed following the loss of engine power, which resulted in the airplane exceeding its critical angle of attack and experiencing an aerodynamic stall. Postaccident disassembly of the engine revealed catastrophic failure of internal engine components and signatures consistent with no lubrication and high heat.

## Factual narrative

The four-seat, high-wing airplane was manufactured in 1981. It was powered by a 180-horsepower Lycoming O-360-A4M engine and was equipped with a two-bladed Sensenich propeller. The airplane's maintenance records were destroyed in the postimpact fire and maintenance intervals could not be verified. On September 27, 2016, about 1830 eastern daylight time, a Cessna 172P, N52126, was destroyed when it impacted terrain following a loss of control near Laytonsville, Maryland. The commercial pilot/mechanic was fatally injured. The airplane was owned by TSS Flying Club, Inc., and was operated by the pilot. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight conducted under the provisions of 14 Code of Federal Regulations Part 91. The airplane departed from Davis Airport (W50) in Laytonsville and was destined for Montgomery County Airpark (GAI), Gaithersburg, Maryland. According to representatives at the TSS Flying Club, about 1400, the pilot/mechanic flew the airplane from the club's base at GAI to W50 to complete a 100-hour maintenance inspection of the airplane. A review of airport security video at W50 revealed that the pilot taxied the airplane onto the maintenance ramp, shut down the engine, and uncowled the engine. He then drained the engine oil and inspected the spark plugs, air filter, and other engine components before reinstalling the engine cowling. The pilot then pushed the airplane back, started the engine, and taxied to the runway for takeoff. The video did not depict the pilot/mechanic servicing the engine with oil. According to air traffic control audio communication recordings provided by the Federal Aviation Administration (FAA), shortly after takeoff from W50, the pilot reported to an air traffic controller that he was "losing an engine" and was returning to the airport. Several witnesses reported that the airplane flew in a southeasterly direction, completed a 180° turn, and flew back toward W50. The airplane was then seen "flying erratically" before it stabilized momentarily and then "fell out of the sky sideways." One witness stated he could see the top of the airplane's wing during its entire descent to the ground. Review of airport security surveillance video revealed that about 8 minutes after the airplane departed, it began emitting a smoke plume. At that point, the airplane was about 1 mile southeast of the airport. The Office of the Chief Medical Examiner, State of Maryland, performed an autopsy on the pilot. The autopsy findings included "multiple injuries." The FAA Bioaeronautical Sciences Research Laboratory, Oklahoma City, Oklahoma, performed forensic toxicology on specimens from the pilot. The toxicology report stated that no ethanol or drugs were detected in the urine. The 1815 recorded weather at GAI, located 4 miles southwest of the accident site, included wind from 180° at 5 knots, visibility 10 miles, clear skies, temperature 22°C, dew point 11°C, and an altimeter settingof 29.94 inches of mercury. According to FAA records, the pilot held a commercial pilot certificate with a rating for airplane single-engine land. His most recent FAA third-class medical certificate was issued on April 13, 2016. He reported 1,183 total hours of flight experience on that date. He also held a mechanic certificate with ratings for airframe and powerplant. The wreckage was examined at the accident site, and all major components were accounted for at the scene. The engine compartment, cockpit, cabin area, empennage, and most of both wings were consumed by postcrash fire. Flight control cable continuity was confirmed from the cockpit area to the flight control surfaces. The two-bladed propeller remained attached to the engine. One blade was bent aft, partially melted, and displayed leading edge nicks. The outboard half of the other propeller blade was consumed by fire. The engine was separated from the wreckage and placed on an engine stand for examination. The oil sump, oil filter, and the accessory section were destroyed by fire. Examination of the starter housing and starter ring gear support revealed no witness marks. The top spark plugs were removed, and an attempt to rotate the crankshaft with the propeller was unsuccessful. The valve covers were removed, and they contained no oil or oil residue. Investigators then attempted to remove the cylinders. Only cylinder Nos. 1 and 2 could be removed from the case base studs. The No. 1 cylinder had internal damage to the piston, and the connecting rod exhibited restricted rotation about the crankshaft. The No. 2 cylinder connecting rod was found to move freely. The rear accessory housing was removed, and the oil pump was disassembled. Investigators attempted to rotate the oil pump drive shaft by hand with negative results. The steel gears were locked and would not rotate. The accessory housing side of the oil pump was discolored and exhibited signs consistent with a lack of lubrication. The case halves were split. The No. 3 intake tappet body and the No. 4 exhaust tappet body were found damaged and fell out of the case. The outside of the case at the No. 4 cylinder was fractured. The No. 3 cylinder was thermally damaged at the cylinder head to steel barrel interface. The inside of the case was noted to be void of residual oil. The camshaft exhibited heat signatures consistent with a lack of lubrication. The Nos. 1 and 2 connecting rod bearings were removed from the crankshaft. The No. 1 connecting rod bearing exhibited discoloration and heat damage consistent with a lack of lubrication. Once the case halves were split, the No. 4 connecting rod was found broken and discolored. The No. 4 connecting rod cap was found inside the case half and was severely damaged, consistent with impact with the rotating crankshaft. The No. 4 connecting rod bearing halves were found discolored and impact damaged, consistent with the broken connecting rod and crankshaft striking the halves and flattening thebearing. The crankshaft was removed and found to be highly discolored at the connecting rod and main journals. The No. 4 journal exhibited a crack about 2 inches long near the middle of the journal. The No. 3 bearing exhibited discoloration and showed the copper underlay. The bearing edges exhibited signs of extruding of the surfaces. All engine damage signatures were consistent with a lack of lubrication.

## Aircraft

- Registration: [N52126](https://openairdocs.org/deregistered/N52126-2017-02-23), registration cancelled 2017-02-23, S/N 17274420, built 1980 (OpenAirDocs)
- Reported make and model: CESSNA 172 (P)
- Registry model: [Cessna 172P](https://openairdocs.org/model/cessna-172p) (registry code 2072436) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17274420
- Year built: 1980
- Engines: LYCOMING O-360-A4M 180 horsepower reciprocating
- Damage: Destroyed
- Fire: On-Ground
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Departed: W50, Laytonsville, MD
- Destination: GAI, Gaithersburg, MD
- Airport: W50, Davis, runway 26, 2,000 × 25 ft, asphalt
- Equipment: Unknown

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 78; injuries: fatal; commercial; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; seat: left; toxicology performed; flight hours: 1,183 total, 1,000 in this make and model

## Weather

- Conditions: Visual (VMC), Day
- Wind: 180° at 5 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 72 °F, dew point 52 °F
- Altimeter: 29.94 inHg
- Observed at: KGAI, 4 nm away

## 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 20160927019689A](https://openairdocs.org/incident/20160927019689A), Sep 27, 2016: Cessna 172P, Laytonsville, MD, Destroyed, 1 fatal. On September 27, 2016, william Hughes flew a Cessna 172P, N52126 from montgomery county airpark (gai) airport in gaithersburg MD, to Davis Airport (W50) in…

## Docket (8 files)

The files NTSB released with the investigation on August 4, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=94092. 25.2 MB in all.

- Witness Statements (item 1, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40454886&FileExtension=.PDF&FileName=Witness%20Statements-Master.PDF
- Air Traffic Control Radio Communication Audio (item 2, WAV, 15.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40454887&FileExtension=wav&FileName=Air%20Traffic%20Control%20Radio%20Communication%20Audio-Master
- Airport Security Surveillance Video - Event Times (item 3, .PDF, 341 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40454888&FileExtension=.PDF&FileName=Airport%20Security%20Surveillance%20Video%20-%20Event%20Times-Master.PDF
- Airport Security Surveillance Video - Excerpted Frames (item 4, .PDF, 652 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40454889&FileExtension=.PDF&FileName=Airport%20Security%20Surveillance%20Video%20-%20Excerpted%20Frames-Master.PDF
- Investigative Photos (item 5, .PDF, 2.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40454890&FileExtension=.PDF&FileName=Investigative%20Photos-Master.PDF
- Release of Aircraft Wreckage, NTSB Form 6120.15 (item 6, .PDF, 262 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40454891&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Master.PDF
- Toxicological Report (item 7, .PDF, 203 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40454892&FileExtension=.PDF&FileName=Toxicological%20Report-Master.PDF
- Statement of Party Representatives to NTSB Investigation (item 8, .PDF, 4.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40454893&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-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.
