# NTSB GAA19CA504: Cessna 182, N58628, Oakland, CA, August 4, 2019 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 4, 2019, 10:00 local (17:00 UTC) - Place: Oakland, CA - Coordinates: 37.724166, -122.211669 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.7242&lon=-122.2117&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed, report February 11, 2020 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 100114 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA19CA504 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/100114/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=100114 - Page: https://openairdocs.org/ntsb/GAA19CA504 ## Probable cause The pilot's premature full retraction of the flaps during a go-around and his subsequent improper decision to turn with a minimal climb gradient, which resulted in an off-airport landing and a landing gear collapse. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: configuration](https://openairdocs.org/ntsb-findings/01062017): Aircraft › Aircraft oper/perf/capability · Capability exceeded (probable cause); cases with it: [Cessna 182P, 2 cases](https://openairdocs.org/ntsb-findings/01062017/cases.md?model=2075816), [All aircraft, 80 cases](https://openairdocs.org/ntsb-findings/01062017/cases.md) - [Flight control system: tE flap control system](https://openairdocs.org/ntsb-findings/01022750): Aircraft › Aircraft systems · Incorrect use/operation (probable cause); cases with it: [Cessna 182P, 3 cases](https://openairdocs.org/ntsb-findings/01022750/cases.md?model=2075816), [All aircraft, 74 cases](https://openairdocs.org/ntsb-findings/01022750/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 182P, 18 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2075816), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 182P, 8 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=2075816), [All aircraft, 1,391 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md) - [Performance/control parameters: configuration](https://openairdocs.org/ntsb-findings/01062017): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 182P, 2 cases](https://openairdocs.org/ntsb-findings/01062017/cases.md?model=2075816), [All aircraft, 80 cases](https://openairdocs.org/ntsb-findings/01062017/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: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Cessna 182P, 10 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2075816), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Approach-VFR go-around: Miscellaneous/other](https://openairdocs.org/ntsb-events/900); cases with it: [Cessna 182P, 5 cases](https://openairdocs.org/ntsb-events/900/sequence.md?model=2075816), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md) - [Approach-VFR go-around: Loss of lift](https://openairdocs.org/ntsb-events/500); cases with it: [Cessna 182P, 2 cases](https://openairdocs.org/ntsb-events/500/sequence.md?model=2075816), [All aircraft, 252 cases](https://openairdocs.org/ntsb-events/500/sequence.md) - [Landing: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Cessna 182P, 18 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=2075816), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Cessna 182P, 10 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2075816), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Cessna 182P, 6 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=2075816), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) ## Analysis The pilot reported that, during landing, the airplane bounced multiple times. He added power and reduced the flaps to go around, but the airplane would not climb more than 25 ft. He waited to see if the situation would improve, but he was approaching the end of the runway. He turned the airplane right; however, the airplane still did not climb, so he reduced power and conducted an off-airport landing, during which the airplane bounced a few times, and the nose landing gear collapsed. He added that it was possible that "putting the flaps up un-incrementally could have prevented" the airplane from climbing. The airplane sustained substantial damage to the fuselage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The airport's automated weather observation station reported that, about 4 minutes after the accident, the wind was from 250° at 7 knots. The pilot landed the airplane on runway 28. The Federal Aviation Administration's Airplane Flying Handbook, FAA-H-8083-3B, contained a section titled, "Go-Arounds (Rejected Landings)," which stated, in part, the following: Caution must be used in retracting the flaps. Depending on the airplane's altitude and airspeed, it is wise to retract the flaps intermittently in small increments to allow time for the airplane to accelerate progressively as they are being raised. A sudden and complete retraction of the flaps could cause a loss of lift resulting in the airplane settling into the ground. ## Factual narrative The pilot reported that, during landing, the airplane bounced multiple times. He added power and reduced the flaps to go around, but the airplane was not climbing more than 25 ft. He waited to see if the situation would improve, but he ran out of runway. He turned right, still unable to climb, reduced power, and landed off airport. The airplane bounced a few times and the nose landing gear collapsed. He added that it was possible that "putting the flaps up un-incrementally could have prevented" his ability to climb. The airplane sustained substantial damage to the fuselage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The airport's automated weather observation station reported that, about 4 minutes after the accident, the wind was from 250° at 7 knots. The pilot landed the airplane on runway 28. Federal Aviation Administration's Airplane Flying Handbook, FAA-H-8083-3B, contains a section titled "Go-Arounds (Rejected Landings)" which states: Caution must be used in retracting the flaps. Depending on the airplane's altitude and airspeed, it is wise to retract the flaps intermittently in small increments to allow time for the airplane to accelerate progressively as they are being raised. A sudden and complete retraction of the flaps could cause a loss of lift resulting in the airplane settling into the ground. ## Aircraft - Registration: [N58628](https://openairdocs.org/aircraft/N58628), registered now, S/N 18262186, built 1973 (OpenAirDocs) - Reported make and model: Cessna 182 (P) - Registry model: [Cessna 182P](https://openairdocs.org/model/cessna-182p) (registry code 2075816) (OpenAirDocs) - Registry engine: [Continental O-470 series](https://openairdocs.org/engine/continental-o-470-series) (registry code 17026, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 18262186 - Year built: 1973 - Engines: Continental O-470 SERIES 235 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Oakland Flyers - Registered owner: Suburban Air Corporation - Airworthiness certificate: Standard, Normal - Departed: PRB, Paso Robles, CA - Destination: OAK, Oakland, CA - Flight plan: VFR/IFR - Airport: OAK, Metropolitan Oakland Intl, runway 28R, 5,458 × 150 ft, asphalt - Equipment: ADS-B ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 54; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: basicmed; last flight review April 9, 2019; seat: left; restraint: 3-point; flight hours: 1,445 total, 135 in this make and model, 1,356 as pilot in command, 16.3 in the last 90 days, 8.3 in the last 30 days, 1.2 in the last 24 hours ## Weather - Conditions: Instrument (IMC), Day - Wind: 250° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: 800 ft broken - Temperature: 64 °F, dew point 57 °F - Altimeter: 30.00 inHg - Observed at: KOAK ## 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 20190804017629A](https://openairdocs.org/incident/20190804017629A), Aug 4, 2019: Cessna 182P, Oakland, CA, Substantial damage. Pilot performed an instrument approach to runway 28R. Pilot bounced the aircraft and failed to land the aircraft on 28R. Pilot tried a go-around and aircraft… ## Docket (3 files) The files NTSB released with the investigation on October 29, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=100114. 5.0 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40477259&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Record of Conversation - Pilot (item 2, .PDF, 68 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40477260&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Pilot-Master.PDF - Accident Photo (item 3, .PDF, 1 photo, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40477261&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.