# NTSB ERA18LA070: Piper PA32R, N47863, Marathon, FL, January 25, 2018

- Type: NTSB accident investigation
- Classification: Accident · Serious injuries · Limited investigation · Final report
- Date: January 25, 2018, 14:25 local (19:25 UTC)
- Place: Marathon, FL
- Coordinates: 24.956943, -81.050552 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=24.9569&lon=-81.0506&mi=10
- Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping)
- Defining event: [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230)
- Highest injury: Serious injuries
- Injuries: 4 serious
- Status: Completed, report November 6, 2019
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA/FSDO
- NTSB case key (mKey): 96656
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA18LA070
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/96656/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=96656
- Page: https://openairdocs.org/ntsb/ERA18LA070

## Probable cause

The pilot's failure to maintain directional control during takeoff.

## 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: [Piper PA-32R-300, 14 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7103213), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-32R-300, 3 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7103213), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md)
- [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Piper PA-32R-300, 4 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=7103213), [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.

- [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Piper PA-32R-300, 2 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7103213), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md)
- [Takeoff: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Piper PA-32R-300, 2 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=7103213), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md)
- [Takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA-32R-300, 6 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7103213), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)
- [Takeoff: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-32R-300, 32 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103213), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

The private pilot reported that the airplane "was performing well and didn't have any issues" during the attempted takeoff. When the airplane reached about 60 knots during the takeoff roll, the nosewheel lifted off the runway, and the airplane began immediately turning left. The pilot attempted to arrest the turn with rudder and aileron control inputs, but the airplane continued to turn left, exited the runway, and impacted trees. Given that the airplane had been performing as expected initially, it is likely that the pilot failed to adequately compensate for the airplane's natural left turning tendencies due to torque effects during the attempted takeoff, which resulted in a loss of directional control.

## Factual narrative

On January 25, 2018, about 1425 eastern standard time, a Piper PA-32R-300, N47863, was substantially damaged during collision with terrain shortly after takeoff from Florida Keys Marathon International Airport (MTH), Marathon, Florida. The private pilot and three passengers sustained serious injuries. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight conducted under the provisions of Title 14 Code of Federal Regulations Part 91.The accident flight was recorded via airport surveillance video. One video revealed the airplane began its takeoff roll from a complete stop, on runway 07 and travelled about 800 ft before the nose wheel lifted from the runway. At liftoff, the nose pitched up steeply and the airplane rolled left immediately, before it disappeared from the frame. A second video captured the takeoff from a much greater distance. The image in the frame was smaller with poorer resolution. The video revealed a steep pitch and left bank at takeoff. The climb stopped immediately after liftoff, and the airplane maintained approximately the same angle of bank as it departed the runway to its left, entered the trees, and disappeared. Several seconds later, a fireball appeared above the trees about the point where the airplane entered them. The pilot reported to a Federal Aviation Administration (FAA) inspector that the airplane "was performing well and didn't have any issues." The airplane reached approximately 60 knots on the takeoff roll when the nose wheel lifted from the runway and the airplane began an immediate left turn. He attempted to arrest the turn with rudder and aileron, but the turn continued until the airplane entered the trees. A rear seat passenger told the inspector that he was seated in the third row of seats with the other passenger, and that the center row of seats was unoccupied. The pilot held a private pilot certificate with ratings for airplane single engine land and instrument airplane. His most recent FAA third-class medical certificate was issued October 20, 2016. He reported 500 total hours of flight experience on that date. According to FAA airworthiness and maintenance records, the airplane was manufactured in 1977. Its most recent annual inspection was completed October 20, 2017, at 6,156.86 total aircraft hours. The maintenance records reflected a "50-hour" inspection completed January 16, 2018. At 1453, the weather reported at MTH included an overcast ceiling at 4,700 ft, 10 miles visibility, and winds from 050° at 18 knots. The temperature was 22° C, the dew point was 16° C, and the altimeter setting was 30.19 inches of mercury. The wreckage was examined at the accident site by an FAA inspector and all major components were accounted for at the scene. The wings and fuselage were substantially damaged by impact and postcrash fire. According to FAA Advisory Circular AC-61-23C, Pilot's Handbook of Aeronautical Knowledge: "The effect of torque increases in directproportion to engine power, airspeed, and airplane attitude. If the power setting is high, the airspeed slow, and the angle of attack high, the effect of torque is greater. During takeoffs and climbs, when the effect of torque is most pronounced, the pilot must apply sufficient right rudder pressure to counteract the left-turning tendency and maintain a straight takeoff path."

## Aircraft

- Registration: [N47863](https://openairdocs.org/deregistered/N47863-2019-01-28), registration cancelled 2019-01-28, S/N 32R-7880025, built 1977 (OpenAirDocs)
- Reported make and model: PIPER PA32R (300)
- Registry model: [Piper PA-32R-300](https://openairdocs.org/model/piper-pa-32r-300) (registry code 7103213) (OpenAirDocs)
- Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 32R-7880025
- Year built: 1977
- Airframe hours: 6156.86
- Engines: Lycoming IO-540-K1G5 reciprocating
- Damage: Substantial damage
- Fire: On-Ground
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, October 20, 2017, 50 hours before
- Departed: MTH, Marathon, FL
- Destination: GIF, WINTER HAVEN, FL
- Airport: MTH, The Florida Keys Marathon Intl, runway 07, 5,008 × 100 ft, asphalt
- Equipment: Unknown

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 65; injuries: serious; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; seat: left; flight hours: 500 total, 10 in this make and model

## Weather

- Conditions: Visual (VMC), Day
- Wind: 50° at 18 knots
- Visibility: 10 statute miles
- Lowest ceiling: 4,700 ft overcast
- Temperature: 72 °F, dew point 61 °F
- Altimeter: 30.19 inHg
- Observed at: MTH

## 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 20180125001199A](https://openairdocs.org/incident/20180125001199A), Jan 25, 2018: Piper PA-32R-300, Marathon, FL, Destroyed. Piper pa 32R-300, N47863 with four persons on board. Took off from the Florida Keys Marathon international airport (mth) during the takeoff roll the aircraft…

## Other investigations on N47863 (1)

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.

- [NTSB ERA12CA190](https://openairdocs.org/ntsb/ERA12CA190), Feb 18, 2012: Piper PA-32R-300 (N47863), Swainsboro, GA, substantial damage. Probable cause: The pilot’s failure to maintain the proper glidepath during final approach in night visual meteorological conditions, which resulted in a collision with trees.

## Docket (6 files)

The files NTSB released with the investigation on April 11, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=96656. 1.4 MB in all.

- Memorandum for Record - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 52 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40471753&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20-%20Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- Memorandum for Record – Telephone Interview, Pilot (FAA) (item 2, .PDF, 97 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40471754&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20%E2%80%93%20Telephone%20Interview,%20Pilot%20(FAA)-Master.PDF
- Witness (item 3, .PDF, 224 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40471755&FileExtension=.PDF&FileName=Witness-Master.PDF
- Photos (item 4, .PDF, 3 photos, 987 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40471756&FileExtension=.PDF&FileName=Photos-Master.PDF
- Video File A (item 5, .PDF, 37 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40471836&FileExtension=.PDF&FileName=Video%20File%20A-Master.PDF
- Video File B (item 6, .PDF, 42 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40471837&FileExtension=.PDF&FileName=Video%20File%20B-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.
