# NTSB GAA18CA467: Beech 58, N59PR, Greenville, SC, August 3, 2018

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: August 3, 2018, 10:25 local (14:25 UTC)
- Place: Greenville, SC
- Coordinates: 34.848056, -82.349998 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=34.8481&lon=-82.3500&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300)
- Highest injury: No injuries
- Injuries: 3 uninjured
- Status: Completed, report September 26, 2019
- Report: Approved by Office Director
- NTSB office: General Aviation Accidents
- Parties: FAA
- NTSB case key (mKey): 97983
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA18CA467
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/97983/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=97983
- Page: https://openairdocs.org/ntsb/GAA18CA467

## Probable cause

The pilot failure to attain the proper touchdown point on a wet runway, which resulted in insufficient runway remaining to safely stop the airplane.

## 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: [Raytheon 58, 5 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7150003), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Raytheon 58, 4 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=7150003), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/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: [Raytheon 58, 1 case](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=7150003), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md)
- [Object/animal/substance: fence/fence post](https://openairdocs.org/ntsb-findings/03022047): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Raytheon 58, 1 case](https://openairdocs.org/ntsb-findings/03022047/cases.md?model=7150003), [All aircraft, 313 cases](https://openairdocs.org/ntsb-findings/03022047/cases.md)
- [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Raytheon 58, 1 case](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=7150003), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md)
- [Runway/land/takeoff/taxi surface: wet surface](https://openairdocs.org/ntsb-findings/03023010): Environmental issues › Physical environment · Effect on operation; cases with it: [Raytheon 58, 1 case](https://openairdocs.org/ntsb-findings/03023010/cases.md?model=7150003), [All aircraft, 141 cases](https://openairdocs.org/ntsb-findings/03023010/cases.md)

## Sequence of events

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

- [Landing-landing roll: Miscellaneous/other](https://openairdocs.org/ntsb-events/900); cases with it: [Raytheon 58, 1 case](https://openairdocs.org/ntsb-events/900/sequence.md?model=7150003), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md)
- [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Raytheon 58, 2 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7150003), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)
- [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Raytheon 58, 7 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7150003), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

The pilot in the multiengine airplane reported that, following an instrument approach, the airplane broke out of the clouds about 600 ft above ground level. The pilot reported that he was concerned that the airplane was too high for a safe landing on the wet runway, so he contacted air traffic control and requested to circle and land. The tower controller cleared the pilot to circle and land on a 4,000-ft-long runway. The pilot reported that, during the landing roll, as the airplane approached the last taxiway, the airplane slid and overran the runway end. The airplane then rolled down an embankment and impacted a chain link fence and trees. The airplane sustained substantial damage to the fuselage and both wings. According to Federal Aviation Administration aviation safety inspectors, the airplane touched down with about 1,300 ft of runway remaining.

## Factual narrative

The pilot in the multi-engine airplane reported that following an instrument approach, the airplane broke out of the clouds about 600ft AGL. Concerned with the length of remaining runway, the pilot felt that the airplane was too high for a safe landing on the wet asphalt. The pilot requested to circle and land. The tower controller cleared the pilot to circle and land on a 4,000ft runway. During the landing roll, the pilot reported that as the airplane approached the last taxiway the airplane was "sliding instead of stopping", and it over-ran the runway. The airplane exited the departure end of the runway and rolled down an embankment, impacting a chain link fence and trees. According to Federal Aviation Administration Aviation Safety Inspectors, the airplane touched down with about 1,300ft of runway remaining. The pilot informed the ASI that there were no mechanical issues with the airplane. The airplane sustained substantial damage to the fuselage and both wings.

## Aircraft

- Registration: [N59PR](https://openairdocs.org/deregistered/N59PR-2019-12-20), registration cancelled 2019-12-20, S/N TH-1940, built 2000 (OpenAirDocs)
- Reported make and model: Beech 58 (Undesignat)
- Registry model: [Raytheon 58](https://openairdocs.org/model/raytheon-58) (registry code 7150003) (OpenAirDocs)
- Registry engine: [Continental IO-550 series](https://openairdocs.org/engine/continental-io-550-series) (registry code 17042, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: TH-1940
- Year built: 2000
- Engines: reciprocating; reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Four D Llc
- Registered owner: Four D Llc
- Airworthiness certificate: Standard, Normal
- Departed: CHS, Charleston, SC
- Destination: GMU, Greenville, SC
- Flight plan: IFR
- Airport: GMU, Greenville Downtown, runway 28, 4,000 × 80 ft, asphalt
- Equipment: Unknown

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 59; injuries: none; commercial, flight instructor; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2; seat: front; flight hours: 1,707 total, 44 in this make and model, 44 in the last 90 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 220° at 4 knots
- Lowest ceiling: 800 ft broken
- Temperature: 73 °F, dew point 72 °F
- Altimeter: 30.14 inHg
- Observed at: KGMU

## 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 20180803009849A](https://openairdocs.org/incident/20180803009849A), Aug 3, 2018: Raytheon Aircraft Company 58, Greenville, SC, Substantial damage. Aircraft missed the approach to runway 19, circled and landed on runway 28. The aircraft slid off of the end of runway 28

## Docket (3 files)

The files NTSB released with the investigation on May 9, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=97983. 452 KB in all.

- Memorandum for Record - Pilot Statement (item 1, .PDF, 138 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40472792&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20-%20Pilot%20Statement-Master.PDF
- Memorandum for Record - FAA Statement (item 2, .PDF, 126 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40472793&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20-%20FAA%20Statement-Master.PDF
- Photo (item 3, .PDF, 1 photo, 188 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40472794&FileExtension=.PDF&FileName=Photo-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.
