Cessna 182 accident near Oakland, California, August 4, 2019
On August 4, 2019 at about 5:00 pm local time, a 1973 Cessna 182, registered N58628, was substantially damaged in an accident during landing (flare/touchdown) near Oakland, California (Metropolitan Oakland Intl airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 4, 2019 · about 5:00 pm local time
- Place
- Oakland, California · Metropolitan Oakland Intl · map
- Type
- Accident
- Injuries
- No one was hurt; 3 people were on board or involved.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Cessna 182 P, built 1973 · all 182s on the register
- Registration
- N58628 · registry record · serial 18262186
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Abnormal runway contact during landing (flare/touchdown) defining event
- Miscellaneous/other during approach (VFR go-around)
- Loss of lift during approach (VFR go-around)
- Off-field or emergency landing during landing
- Abnormal runway contact during landing
- Landing gear collapse during landing
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Configuration › Capability exceeded
- cause Aircraft › Aircraft systems › Flight control system › TE flap control system › Incorrect use/operation
- cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Configuration › Incorrect use/operation
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 1,445 hours in all; 135 in this make and model; 16.3 in the last 90 days; 8.3 in the last 30 days; 1,356 as pilot in command
- Last flight review: April 9, 2019
- Medical certificate: BasicMed
- Seat: left
- Injury: no injuries
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 2,950 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental O-470 SERIES (piston); 0 hours total
The flight
- Departed from: PRB Paso Robles CA at 4:00 pm
- Destination: OAK Oakland CA
- Flight plan: VFR then IFR
- Runway 28R, 5,458 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 250° at 7 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 800 ft
- Temperature: 64°F (18°C), dew point 57°F (14°C)
- Altimeter: 30.00 inHg
- Observation at 5:04 pm from KOAK
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on October 29, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Record of Conversation - Pilot | PDF, 1 page | View Download |
| 3 | Accident Photo | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
