# NTSB ERA17CA213: Cessna 207, N207GM, Vinalhaven, ME, June 26, 2017

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Data collection · Final report
- Date: June 26, 2017, 07:41 local (11:41 UTC)
- Place: Vinalhaven, ME
- Coordinates: 44.070556, -68.821662 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=44.0706&lon=-68.8217&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-aborted after touchdown: Landing area overshoot](https://openairdocs.org/ntsb-events/380)
- Highest injury: Minor injuries
- Injuries: 1 minor
- Status: Completed, report October 24, 2018
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA
- NTSB case key (mKey): 95433
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA17CA213
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/95433/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=95433
- Page: https://openairdocs.org/ntsb/ERA17CA213

## Probable cause

The pilot’s failure to maintain a stabilized approach, which resulted in a bounced landing and subsequent go-around with insufficient distance to clear trees during the climb.

## 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 207, 7 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2073602), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Aircraft capability: climb capability](https://openairdocs.org/ntsb-findings/01061010): Aircraft › Aircraft oper/perf/capability · Capability exceeded (probable cause); cases with it: [Cessna 207, 1 case](https://openairdocs.org/ntsb-findings/01061010/cases.md?model=2073602), [All aircraft, 183 cases](https://openairdocs.org/ntsb-findings/01061010/cases.md)
- [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 207, 1 case](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2073602), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md)
- [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 207, 1 case](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=2073602), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md)
- [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Effect on operation (probable cause); cases with it: [Cessna 207, 1 case](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=2073602), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md)

## Sequence of events

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

- [Landing: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Cessna 207, 1 case](https://openairdocs.org/ntsb-events/090/sequence.md?model=2073602), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md)
- [Landing-aborted after touchdown: Landing area overshoot](https://openairdocs.org/ntsb-events/380) (defining event); cases with it: [Cessna 207, 2 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=2073602), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md)
- [Approach-VFR go-around: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 207, 9 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2073602), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

The pilot reported that the approach appeared normal, but during the landing on the 1,500-ft-long gravel strip, the airplane firmly struck the runway and bounced. He added that the bounce was high and that the remaining runway was too short to correct the landing with power. The pilot chose to go around, applying full power and 20° of flaps for the balked landing procedure. During the climb, the airplane drifted left toward 50-ft-tall trees about 150 ft from the departure end of the runway. Unable to climb over the trees, the airplane struck the tree canopy, the nose dropped, and the pilot instinctively reduced power as the airplane descended through the trees and impacted terrain. The wings and fuselage were substantially damaged. The pilot reported no preimpact mechanical failures or malfunctions with the airplane that would have precluded normal operation.

## Factual narrative

The pilot reported that the approach appeared normal, but during the landing on the 1,500 ft gravel strip, the airplane firmly struck the runway and bounced. He added that the bounce was high, and the remaining runway was too short to correct the landing with power. The pilot elected to go-around, applying full power and 20° of flaps for the balked landing procedure. During the climb, the airplane drifted to the left towards the 50 ft trees about 150 ft from the departure end of runway 24. Unable to climb over the trees, the airplane struck the tree canopy; the nose dropped and the pilot instinctively reduced power as the airplane descended through the trees and impacted terrain. The wings and fuselage were substantially damaged. The pilot reported no preimpact mechanical failures or malfunctions with the airplane that would have precluded normal operation.

## Aircraft

- Registration: [N207GM](https://openairdocs.org/aircraft/N207GM), registered now, S/N 20700217, built 1973 (OpenAirDocs)
- Reported make and model: CESSNA 207 (UNDESIGNAT)
- Registry model: [Cessna 207](https://openairdocs.org/model/cessna-207) (registry code 2073602) (OpenAirDocs)
- Registry engine: [Continental IO-520 series](https://openairdocs.org/engine/continental-io-520-series) (registry code 17032, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 20700217
- Year built: 1973
- Airframe hours: 12458
- Engines: Continental IO-520-LCF 300 horsepower reciprocating
- Damage: Substantial damage
- Flight: Part 135
- Operator: Waters Aero Marine Inc, doing business as Penobscot Island Air
- Registered owner: Waters Aero Marine Inc
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, May 23, 2017
- Departed: RKD, ROCKLAND, ME
- Destination: ME55, Vinalhaven, ME
- Airport: ME55, Vinalhaven, runway 24, 1,510 × 60 ft, gravel
- Equipment: Unknown

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 65; injuries: minor; flight instructor, airline transport; airplane ratings: single-engine land, multi-engine sea, single-engine sea; instrument ratings: airplane; medical: class 2, without waivers/limitations; last flight review August 5, 2016; seat: left; restraint: lap only; flight hours: 15,438 total, 356 in this make and model, 10,655 as pilot in command, 32 in the last 90 days, 23 in the last 30 days, 0 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 290° at 8 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 64 °F, dew point 57 °F
- Altimeter: 29.88 inHg
- Observed at: RKD, 9 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 20170626005969A](https://openairdocs.org/incident/20170626005969A), Jun 26, 2017: Cessna 207, Vinalhaven, ME, Substantial damage. The pilot experienced a bounced landing on runway 24 and in the subsequent go-around attempt crashed into the woods approximately 150 feet left of the…

## Docket (3 files)

The files NTSB released with the investigation on August 27, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=95433. 2.5 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 861 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40465994&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- Pilot Memo of Conversation (item 2, .PDF, 130 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40465995&FileExtension=.PDF&FileName=Pilot%20Memo%20of%20Conversation-Master.PDF
- Photographs of Accident Site and Damage (item 3, .PDF, 3 photos, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40465996&FileExtension=.PDF&FileName=Photographs%20of%20Accident%20Site%20and%20Damage-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.
