# NTSB ERA22LA274: Cessna 172, N5064H, Brevard, NC, June 16, 2022 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Class 3 · Limited · Final report - Date: June 16, 2022, 17:45 local (21:45 UTC) - Place: Brevard, NC - Coordinates: 35.177699, -82.826421 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=35.1777&lon=-82.8264&mi=10 - Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping) - Defining event: [Maneuvering-low-alt flying: Low altitude operation/event](https://openairdocs.org/ntsb-events/220) - Highest injury: Serious injuries - Injuries: 3 serious - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: FAA, Textron Aviation - NTSB case key (mKey): 105281 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA22LA274 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/105281/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=105281 - Page: https://openairdocs.org/ntsb/ERA22LA274 ## Probable cause The pilot’s failure to maintain altitude while maneuvering the airplane at a low altitude, which resulted in impact with trees and terrain. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: altitude](https://openairdocs.org/ntsb-findings/01062012): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172M, 17 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md?model=2072418), [All aircraft, 1,310 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172M, 123 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072418), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Maneuvering-low-alt flying: Low altitude operation/event](https://openairdocs.org/ntsb-events/220) (defining event); cases with it: [Cessna 172M, 8 cases](https://openairdocs.org/ntsb-events/220/sequence.md?model=2072418), [All aircraft, 780 cases](https://openairdocs.org/ntsb-events/220/sequence.md) ## Analysis The pilot and two passengers were flying at low altitudes over a camp and dropping candy from the airplane. The pilot recalled that the airplane was “a couple hundred feet” above the trees in slow flight; the next thing that the pilot remembered was waking up in a hospital. During the flight, one of the passengers commented to the pilot that the airplane was getting close to the treetops and that he needed to apply power and pull up. The pilot stated something similar to, “I’m working on it.” The passenger recalled that the airplane hit trees and that he woke up next to the airplane. He also stated that the engine was operating normally. Postaccident examination of the airplane revealed no evidence of mechanical malfunctions or anomalies that would have precluded normal operation. An onboard image recording from a camera found at the accident site revealed that the airplane was maneuvering at a low altitude and high bank angles until the airplane impacted terrain. Given the passenger’s recollections and the onboard image recording evidence, the pilot allowed the airplane to sink below the level of the treetops while conducting high bank angles at a low altitude. ## Factual narrative On June 16, 2022, about 1745 eastern daylight time, a Cessna 172M, N5064H, was substantially damaged when it was involved in an accident near Brevard, North Carolina. The pilot and the two passengers were seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, the airplane was flying over a camp so that a passenger could drop candy from the airplane. The pilot stated that the airplane was “a couple hundred feet” above the trees in slow flight. The next thing that the pilot remembered was waking up in a hospital. According to one of the passengers, after the candy drop, the airplane flew around the camp so that photographs could be taken. The passenger stated that the airplane was descending and that he made a comment to the pilot about getting close to the treetops and needing to apply power and pull up. The pilot stated that the pilot said something similar to, “I’m working on it.” The passenger recalled that the airplane hit some trees and that he woke up next to the airplane on the ground. He also stated the engine was operating normally. A GoPro video camera was found at the accident site and was sent to the National Transportation Safety Board’s Vehicle Recorders Division, Washington, DC, for download. The camera contained multiple short videos and still pictures of the accident flight. The 8-minute 42-second stitch of the accident image sequence showed the airplane maneuvering at a low altitude and high bank angles. The airplane made multiple passes over a clearing in the tree canopy, and the passenger in the right front seat made motions consistent with dropping objects out of the airplane over the clearing. The airplane continued to maneuver at high bank angles and a low altitude until the airplane impacted terrain. Postaccident examination of the airplane revealed that the tail section had partially separated from the fuselage and that the wing had separated from the fuselage, resulting in substantial damage. All instrument panel components had dislodged from their housings and were scattered around the cabin. Further examination of the airplane revealed that the left wing remained fastened to its attachment points to the fuselage. The leading edge exhibited aft diagonal buckling/crushing from the wing root to the pitot tube. Just inboard of the pitot tube, the leading edge exhibited a tree impact mark that was about 8 inches in diameter. Approximately mid span, the leading edge exhibited a tree impact mark that was about 1.5 inches in diameter. The right wing remained fastened to its attachment points to the fuselage. About 3 ft 5 inches from the wing tip, the leading edge exhibited a tree impact mark that was about 4 inches in diameter. The right horizontal stabilizer was separated about 6 inches outboard from its attachment points. The elevator and trim tab remained attached to the horizontal stabilizer rear spar, which had separated from the rest of thehorizontal stabilizer. Continuity of all primary flight control cables were confirmed from the cockpit to their respective flight control surface. The engine remained attached to the firewall and front section of the fuselage. The propeller remained attached to the engine, and tree bark was noted in the spinner dome, which was bent. Both propeller blades exhibited bent tips, and one blade had S-shaped bending. Both magnetos had separated from the engine. The magnetos were spun with an electric drill and produced sparks on all leads. The top spark plugs exhibited normal wear. Thumb compression and suction were established on all cylinders when the propeller was rotated by hand. Engine continuity was established through the engine and accessory case. A lighted boroscope was used to examine the cylinders, pistons, and valves. The carburetor was disassembled, and no anomalies were noted. Examination of the airframe and engine revealed no evidence of mechanical malfunctions that would have precluded normal operation. ## Aircraft - Registration: [N5064H](https://openairdocs.org/aircraft/N5064H), registered now, S/N 17265325, built 1975 (OpenAirDocs) - Reported make and model: CESSNA 172 (M) - Registry model: [Cessna 172M](https://openairdocs.org/model/cessna-172m) (registry code 2072418) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17265325 - Year built: 1975 - Airframe hours: 4047 - Engines: Lycoming O-360-A4M 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Franklin Air Services LLC - Registered owner: Franklin Air Services LLC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 1, 2022 - Departed: AVL, Ashville, NC - Equipment: None ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 39; injuries: serious; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review August 1, 2021; seat: left; restraint: 3-point ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Temperature: 82 °F, dew point 70 °F - Altimeter: 30.20 inHg - Observed at: K1A5, 29 nm away - METAR: K1A5 162135Z AUTO 00000KT 10SM SCT060 SCT080 SCT100 28/21 A3020 RMK AO2 T02830212 ## 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 20220616010439A](https://openairdocs.org/incident/20220616010439A), Jun 16, 2022: Cessna 172M, Brevard, NC, Destroyed. On June 16, 2022, at 1745 eastern daylight time, a Cessna 172M, [privacy data omitted], was substantially damaged when it was involved in an accident near… ## Docket (8 files) The files NTSB released with the investigation on November 8, 2023, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=105281. 8.6 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 11 pages, 2.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14663788&FileExtension=pdf&FileName=6120_Redacted-Rel.pdf - Memorandum for record a�� telephone interview, pilot (item 2, PDF, 1 page, 108 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14663515&FileExtension=pdf&FileName=Record%20of%20Interview-pilot-Rel.pdf - Memorandum for record a�� telephone interview, passenger (item 3, PDF, 1 page, 109 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14663292&FileExtension=pdf&FileName=Record%20of%20Interview-passenger-Rel.pdf - Maintenance records (item 4, PDF, 3 pages, 3.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14697701&FileExtension=pdf&FileName=Maintenance%20records_Redacted-Rel.pdf - Investigative photo's (item 5, PDF, 3 pages, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14663977&FileExtension=pdf&FileName=Investigative%20Photo%27s-Rel.pdf - NTSB wreckage examination summary (item 6, PDF, 6 pages, 886 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14664168&FileExtension=pdf&FileName=Wreckage%20Examination-Rel.pdf - Release of aircraft wreckage, NTSB form 6120.15 (item 7, PDF, 1 page, 230 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14663566&FileExtension=pdf&FileName=wreckage%20release_Redacted-Rel.pdf - Onboard image recorder - specialist's factual report (item 8, PDF, 7 pages, 411 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16343306&FileExtension=pdf&FileName=ERA22LA274%20GoPro%20Report_FINAL2-Rel.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.