# NTSB ERA10CA289: Cessna 172N, N6371D, Sterling, MA, May 31, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: May 31, 2010, 15:30 local (19:30 UTC) - Place: Sterling, MA - Coordinates: 42.424167, -71.791114 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=42.4242&lon=-71.7911&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR go-around: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed, report April 12, 2011 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 76150 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA10CA289 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76150/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76150 - Page: https://openairdocs.org/ntsb/ERA10CA289 ## Probable cause The pilot’s decision to not continue with the go-around, which resulted in a collision with trees. Contributing to the accident was the pilot’s distraction due to the passenger’s panicked condition. ## 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 172N, 29 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2072434), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) - [Mental/emotional state: anxiety/panic](https://openairdocs.org/ntsb-findings/02022515): Personnel issues › Psychological · Passenger (probable cause); cases with it: [Cessna 172N, 1 case](https://openairdocs.org/ntsb-findings/02022515/cases.md?model=2072434), [All aircraft, 10 cases](https://openairdocs.org/ntsb-findings/02022515/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR go-around: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) (defining event); cases with it: [Cessna 172N, 14 cases](https://openairdocs.org/ntsb-events/120/sequence.md?model=2072434), [All aircraft, 1,074 cases](https://openairdocs.org/ntsb-events/120/sequence.md) - [Landing: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172N, 81 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072434), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The pilot entered the traffic pattern for runway 34 based on the prevailing wind. She observed the wind sock change to favor runway 16 and in response she maneuvered the airplane for a runway 16 landing. The wind changed direction again to favor runway 34 and she maneuvered the airplane to that runway. She thought the airplane was too high over the touchdown zone and elected to perform a go-around. The passenger in the right seat panicked and started screaming, so the pilot discontinued the go-around, closed the throttle, and the airplane settled into the trees past the runway’s end. The airplane sustained structural damage to the wings and fuselage. The pilot reported no preaccident mechanical anomalies with the airplane. ## Factual narrative The pilot entered the traffic pattern for runway 34 based on prevailing winds. She observed the wind sock change to favor runway 16, so she began to maneuver the airplane for a runway 16 landing. The winds again changed direction to favor runway 34. While on final approach for runway 34, she found herself too high over the touchdown zone, so she executed a go-around. A passenger in the right seat panicked and started screaming, so the pilot discontinued the go-around, closed the throttle, and the airplane settled into the trees past the runway end. Structural damage to the wings and fuselage resulted. The pilot reported no mechanical anomalies with the airplane. ## Aircraft - Registration: [N6371D](https://openairdocs.org/deregistered/N6371D-2013-02-13), registration cancelled 2013-02-13, S/N 17272757 (OpenAirDocs) - Reported make and model: CESSNA 172N - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17272757 - Airframe hours: 7086 - Engines: LYCOMING O-320-H20D 160 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Savard Paula K - Registered owner: Savard Paula K - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 15, 2010 - Departed: 2B2, Newbury Port, MA - Destination: 3B3, Sterling, MA - Flight plan: VFR/IFR - Airport: 3B3, Sterling Airport, runway 34, 3,086 × 40 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 66; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review December 8, 2008; seat: left; flight hours: 412 total, 408 in this make and model, 412 as pilot in command, 16 in the last 90 days, 7 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 170° at 10 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 81 °F, dew point 54 °F - Altimeter: 29.92 inHg - Observed at: FIT, 8 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 20100531036759A](https://openairdocs.org/incident/20100531036759A), May 31, 2010: Cessna 172N, Sterling, MA, Substantial damage. 05/31/10 [privacy data omitted] departed Sterling Airport with 2 passengers at 11AM on 5/31/2010, they flew to plum island for lunch. Departed plum island at… ## Docket (2 files) The files NTSB released with the investigation on November 23, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76150. 734 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 595 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40332394&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - FAA Inspector's Statement (item 2, .PDF, 139 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40332395&FileExtension=.PDF&FileName=FAA%20Inspector%27s%20Statement-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.