The U.S. aircraft register, updated daily
Accidents · NTSB GAA19CA523 · Final report

Cessna A185 accident near San Carlos, California, September 3, 2019

On September 3, 2019 at about 1:40 am local time, a 1980 Cessna A185, registered N34GE, was substantially damaged in an accident during landing near San Carlos, California (San Carlos airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain directional control during the landing roll, which resulted in a ground loop.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 3, 2019 · about 1:40 am local time
Place
San Carlos, California · San Carlos · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna A185 F, built 1980 · all A185s on the register
Registration
N34GE · no longer on the register · serial 18504129
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 the landing roll, the airplane encountered a wind gust from the left and then started to veer left. The pilot corrected with full application of right rudder, but it did not stop the left veer. The airplane ground looped to the left, and the right wing stuck the ground. The airplane sustained substantial damage to the right wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

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

  1. Loss of control on ground during landing defining event

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,344 hours in all; 207 in this make and model; 40 in the last 90 days; 13 in the last 30 days
  • Last flight review: June 20, 2018
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 6,128.4 hours
  • Last inspection: annual inspection, June 1, 2019
  • Maximum gross weight: 3,362 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental IO-550-D (piston); 690 hours total

The flight

  • Departed from: CPU San Andres CA
  • Destination: SQL San Carlos CA
  • Flight plan: none
  • Runway 30, 2,621 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 260° at 8 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 81°F (27°C), dew point 54°F (12°C)
  • Altimeter: 29.88 inHg
  • Observation at 1:55 am from KSQL

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

2 documents, released by the NTSB on January 3, 2020. 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.

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.