# NTSB ERA12CA053: Cessna 172F, N5613R, Smoketown, PA, October 28, 2011 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Data collection · Final report - Date: October 28, 2011, 15:40 local (19:40 UTC) - Place: Smoketown, PA - Coordinates: 40.041389, -76.201385 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=40.0414&lon=-76.2014&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern final: Miscellaneous/other](https://openairdocs.org/ntsb-events/900) - Highest injury: Serious injuries - Injuries: 1 serious - Status: Completed, report February 16, 2012 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 82204 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA12CA053 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/82204/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=82204 - Page: https://openairdocs.org/ntsb/ERA12CA053 ## Probable cause The pilot did not maintain a proper approach path, which resulted in a collision with a tree. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172F, 3 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2072414), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172F, 5 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2072414), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern final: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490); cases with it: [Cessna 172F, 5 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=2072414), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) - [Approach-VFR pattern final: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172F, 22 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072414), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Approach-VFR pattern final: Miscellaneous/other](https://openairdocs.org/ntsb-events/900) (defining event); cases with it: [Cessna 172F, 2 cases](https://openairdocs.org/ntsb-events/900/sequence.md?model=2072414), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md) ## Analysis The pilot reported that, while on final approach for landing, he descended the airplane too low and that the airplane's left wing contacted a tree. The airplane veered left and continued to descend before impacting the ground, resulting in substantial damage to both wings and the engine firewall. A postaccident examination of the airplane revealed no mechanical malfunctions or anomalies. ## Factual narrative The pilot reported to a Federal Aviation Administration (FAA) inspector that, while on final approach for landing, he descended the airplane too low and the airplane's left wing contacted a tree. The airplane veered left and continued to descend before impacting the ground, resulting in substantial damage to both left and right wings and the engine firewall. The inspector's postaccident examination of the airplane revealed no mechanical malfunctions or anomalies. ## Aircraft - Registration: [N5613R](https://openairdocs.org/deregistered/N5613R-2013-08-27), registration cancelled 2013-08-27, S/N 17253225, built 1965 (OpenAirDocs) - Reported make and model: CESSNA 172F - Registry model: [Cessna 172F](https://openairdocs.org/model/cessna-172f) (registry code 2072414) (OpenAirDocs) - Registry engine: [Continental 0-300 series](https://openairdocs.org/engine/continental-0-300-series) (registry code 17022, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17253225 - Airframe hours: 2850 - Engines: CONT MOTOR 0-300 SER 145 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Otto John C - Registered owner: Otto John C - Airworthiness certificate: Standard, Normal - Departed: Unknown - Destination: S37, Smoketown, PA - Flight plan: Unknown - Airport: S37, Smoketown Airport, runway 10, 2,400 × 50 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 76; injuries: serious; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review July 15, 2010; seat: front; flight hours: 1,030 total, 1,000 in this make and model, 4 in the last 90 days ## Weather - Conditions: Visual (VMC), Day - Wind: 30° at 3 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 46 °F, dew point 28 °F - Observed at: LNS, 6 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 20111028024679A](https://openairdocs.org/incident/20111028024679A), Oct 28, 2011: Cessna 172F, Smoketown, PA, Destroyed. The pilot was too low on final approach to rwy 10 at Smoketown (S37). As a result, the aircraft's left wing struck a tree on final approach. The impact caused… ## Docket (4 files) The files NTSB released with the investigation on December 30, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=82204. 7.0 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 83 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40359349&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Memorandum for Record - FAA Inspector (item 2, .PDF, 88 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40359351&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20-%20FAA%20Inspector-Master.PDF - Photo 1 (Courtesy of FAA) (item 3, .PDF, 5.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40359352&FileExtension=.PDF&FileName=Photo%201%20(Courtesy%20of%20FAA)-Master.PDF - Photo 2 (Courtesy of FAA) (item 4, .PDF, 1.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40359353&FileExtension=.PDF&FileName=Photo%202%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.