# NTSB CEN16LA322: Piper J5C, N30313, Sandusky, MI, August 10, 2016 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: August 10, 2016, 07:30 local (12:30 UTC) - Place: Sandusky, MI - Coordinates: 43.45222, -82.842498 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=43.4522&lon=-82.8425&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: Serious injuries - Injuries: 1 serious, 1 minor - Status: Completed, report January 18, 2017 - Report: Approved by Office Director - NTSB office: Central Region - Parties: FAA - NTSB case key (mKey): 93837 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN16LA322 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/93837/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=93837 - Page: https://openairdocs.org/ntsb/CEN16LA322 ## Probable cause The pilot's improper landing flare, which resulted in a bounced landing, and a subsequent loss of control followed by a runway excursion. ## 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 J5A, 6 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7100702), [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 J5A, 3 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7100702), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Performance/control parameters: descent rate](https://openairdocs.org/ntsb-findings/01062037): Aircraft › Aircraft oper/perf/capability · Not attained/maintained; cases with it: [Piper J5A, 1 case](https://openairdocs.org/ntsb-findings/01062037/cases.md?model=7100702), [All aircraft, 242 cases](https://openairdocs.org/ntsb-findings/01062037/cases.md) - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained; cases with it: [Piper J5A, 1 case](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=7100702), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092); cases with it: [Piper J5A, 1 case](https://openairdocs.org/ntsb-events/092/sequence.md?model=7100702), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper J5A, 7 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7100702), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Piper J5A, 4 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7100702), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) ## Analysis After completing one full-stop landing on the grass runway in calm wind conditions, the private pilot decided to complete another landing in the opposite direction. During the landing, the tailwheel-equipped airplane bounced multiple times and became airborne again. The airplane then veered to the right and impacted a ditch next to the runway. The pilot stated that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. It is likely that the pilot failed to control the airplane's descent rate and landing flare, which led to the bounced landing. He was then unable to recover and exited the side of the runway. ## Factual narrative On August 10, 2016, about 0730 eastern daylight time, a Piper J5C airplane, N30313, impacted a ditch after landing at Sandusky City Airport (Y83), Sandusky, Michigan. The private rated pilot sustained minor injuries and the pilot rated passenger sustained serious injuries. The airplane was registered to and operated by a private individual under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed at the time of the accident and no flight plan was filed. The flight departed from Dupont-Lapeer Airport (D95), Lapeer, Michigan, about 0630. The pilot stated that they arrived at Y83 and completed one full stop landing on runway 18. They departed runway 18, entered the traffic pattern, and intended to land on runway 36. The pilot noted that the touchdown was normal, but the airplane veered to the right and impacted a ditch. The pilot noted that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. The pilot had no other memory of the accident sequence. The pilot rated passenger, seated in the rear seat, stated that the approach was stable, but during the landing the airplane "bounced pretty good," enough for the airplane became airborne again. The airplane bounced 2 to 3 times and veered right. The airplane began to gain altitude and then dropped into the ditch. He did not recall the right wing contacting anything prior to the impact with the ditch. The passenger had no other memory of the accident sequence. The responding Federal Aviation Administration (FAA) inspector conducted a postaccident examination of the airplane and found no anomalies that would have precluded normal operation. He reported that the left wing and fuselage sustained substantial damage during the impact sequence. ## Aircraft - Registration: [N30313](https://openairdocs.org/deregistered/N30313-2016-12-19), registration cancelled 2016-12-19, S/N 5-170, built 1940 (OpenAirDocs) - Reported make and model: PIPER J5C - Registry model: [Piper J5A](https://openairdocs.org/model/piper-j5a) (registry code 7100702) (OpenAirDocs) - Registry engine: [Continental C85 series](https://openairdocs.org/engine/continental-c85-series) (registry code 17008, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 5-170 - Year built: 1940 - Airframe hours: 3169.8 - Engines: LYCOMING O-235-C 115 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, July 16, 2016 - Departed: D95, LAPEER, MI - Destination: Y83, Sandusky, MI - Airport: Y83, Sandusky City, runway 36, 2,300 × 150 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 65; injuries: minor; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review August 2, 2016; seat: front; restraint: lap only; flight hours: 660 total, 68 in this make and model, 522 as pilot in command, 18 in the last 90 days, 6.5 in the last 30 days - Pilot-rated passenger; age 61; injuries: minor; commercial, private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; seat: rear; restraint: lap only ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 7 statute miles - Lowest ceiling: none - Temperature: 63 °F, dew point 63 °F - Altimeter: 30.09 inHg - Observed at: KBAX, 21 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 20160810016649A](https://openairdocs.org/incident/20160810016649A), Aug 10, 2016: Piper J5A, Sandusky, MI, Substantial damage. On August 10, 2016, about 0730 local, NC30313, a Piper J5A with one pilot and one passenger departed lapeer county airport (D95) en route to Sandusky City… ## Other investigations on N30313 (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 NYC74FNA31](https://openairdocs.org/ntsb/NYC74FNA31), Jan 6, 1974: Piper J5A (N30313), Westford, MA, substantial damage ## Docket (4 files) The files NTSB released with the investigation on August 25, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=93837. 8.0 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 366 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40443730&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Wreckage Diagrams and Flight Track (item 2, .PDF, 2.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40443731&FileExtension=.PDF&FileName=Wreckage%20Diagrams%20and%20Flight%20Track-Master.PDF - Correspondence - Pilot Rated Passenger (item 3, .PDF, 222 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40443732&FileExtension=.PDF&FileName=Correspondence%20-%20Pilot%20Rated%20Passenger-Master.PDF - Photos (Courtesy of FAA) (item 4, .PDF, 4 photos, 4.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40443733&FileExtension=.PDF&FileName=Photos%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.