# NTSB GAA19CA411: Piper J3C, N92628, San Diego, CA, July 15, 2019 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 14, 2019, 18:30 local (Jul 15, 2019, 01:30 UTC) - Place: San Diego, CA - Coordinates: 32.815834, -117.139442 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.8158&lon=-117.1394&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report August 3, 2020 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 99841 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA19CA411 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/99841/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=99841 - Page: https://openairdocs.org/ntsb/GAA19CA411 ## Probable cause The pilot's failure to maintain directional control during landing, which resulted a ground loop. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [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 J3C-65, 23 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7100510), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper J3C-65, 43 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7100510), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/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: Other weather encounter](https://openairdocs.org/ntsb-events/400); cases with it: [Piper J3C-65, 4 cases](https://openairdocs.org/ntsb-events/400/sequence.md?model=7100510), [All aircraft, 1,127 cases](https://openairdocs.org/ntsb-events/400/sequence.md) - [Landing-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Piper J3C-65, 28 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7100510), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-flare/touchdown: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper J3C-65, 14 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7100510), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The pilot reported that, during his second touch-and-go landing, the airplane encountered a crosswind. He overcorrected with rudder input, and the airplane then ground looped and exited the runway to the left. The airplane sustained substantial damage to the left wing. The pilot reported that there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Factual narrative The pilot of the tail wheel equipped airplane reported that, during his second touch-and-go landing, he felt a crosswind and overcorrected with the rudder input. The airplane subsequently exited the runway to the left and ground looped. The airplane sustained substantial damage to the left wing. The pilot reported that there were no preimpact mechanical malfunctions or failures that would have precluded normal operations. ## Aircraft - Registration: [N92628](https://openairdocs.org/aircraft/N92628), registered now, S/N 16999, built 1946 (OpenAirDocs) - Reported make and model: Piper J3C (65) - Registry model: [Piper J3C-65](https://openairdocs.org/model/piper-j3c-65) (registry code 7100510) (OpenAirDocs) - Registry engine: [Continental A&C65 series](https://openairdocs.org/engine/continental-a-c65-series) (registry code 17003, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 16999 - Year built: 1946 - Engines: reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Advanced Coherent Technologies Llc - Registered owner: Advanced Coherent Technologies Llc - Airworthiness certificate: Standard, Normal - Departed: MYF, San Diego, CA - Destination: MYF, San Diego, CA - Airport: MYF, Montgomery-Gibbs Executive, runway 28R, 4,598 × 150 ft, asphalt - Equipment: Unknown ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 63; injuries: none; commercial, remote; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; seat: left ## Weather - Conditions: Visual (VMC), Day - Wind: 250° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 72 °F, dew point 61 °F - Altimeter: 29.94 inHg - Observed at: KMYF ## 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 20190714011779A](https://openairdocs.org/incident/20190714011779A), Jul 14, 2019: Piper J3C-65, San Diego, CA, Substantial damage. On July 14, 2019, at Montgomery Field, San Diego, CA, at approximately 5:00 pm PDT, pilot was allowed to do his first solo takeoff and landings in his… ## Docket (2 files) The files NTSB released with the investigation on May 19, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=99841. 276 KB in all. - Pilot Record of Memorandum (item 1, .PDF, 144 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40483804&FileExtension=.PDF&FileName=Pilot%20Record%20of%20Memorandum-Master.PDF - Accident Photo (item 2, .PDF, 132 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40483805&FileExtension=.PDF&FileName=Accident%20Photo-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.