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

Cessna T210H accident near Santa Rosa, California, September 6, 2023

On September 6, 2023 at about 4:05 am local time, a 1968 Cessna T210H, registered N2210R, was substantially damaged in an accident during landing (flare/touchdown) near Santa Rosa, California (Charles M Schulz - Sonoma Coun 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 configure the landing gear during the landing approach.

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

What the record shows

Date
September 6, 2023 · about 4:05 am local time
Place
Santa Rosa, California · Charles M Schulz - Sonoma Coun · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna T210H, built 1968 · all T210Hs on the register
Registration
N2210R · registry record · serial T210-0360
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

After flying about 200 miles from his home airport, the pilot performed an uneventful night landing. After taxiing to the end of the runway he decided to perform another takeoff and landing for night currency. There was no traffic in the pattern, and after takeoff he retracted the landing gear. Once at pattern altitude, he stabilized the airplane in preparation for landing on the longest runway. During the final approach he adjusted the throttle, mixture, flaps, and propeller, but missed the step to extend the landing gear. The pilot stated that during the landing he did not recall hearing the gear warning horn, although it had worked during the preflight inspection. The airplane landed gear-up about midfield down the runway and sustained substantial damage to the lower fuselage structure. Following the accident, the pilot secured the airplane by shutting off the fuel selector valve and turning off the airplane’s master switch (which also controlled its external lights). The airport served air carrier operations and was located within Class D airspace until 2000 local, one hour before the accident, when the air traffic control tower closed, and the airspace reverted to Class G (uncontrolled). About the time of the accident, an Embraer E175 air carrier flight was inbound for landing on the accident runway, but from the opposite direction. A member of the airport operations department was performing a routine wildlife runway inspection and observed the accident. He warned the inbound air carrier flight that the runway was obstructed, and the crew initiated a missed approach, and diverted to another airport. The first officer from the air carrier flight stated that he heard the accident airplane make position announcements while in the pattern, but that had it not been for the announcement by airport operations personal that the runway was obstructed, they would likely have continued the approach and landed with the unlit airplane still occupying the runway. The airport typically served about 218 air carrier flight takeoffs and landings per week during the period of the accident, 13 of which were due to operate after the control tower was closed.

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. Landing gear not configured during landing (flare/touchdown) defining event

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot
  • Aircraft › Aircraft systems › Landing gear system › Gear extension and retract sys › Not used/operated
  • Personnel issues › Action/decision › Action › Forgotten action/omission › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 689 hours in all; 296 in this make and model; 53 in the last 90 days; 11 in the last 30 days; 642 as pilot in command
  • Last flight review: October 1, 2022
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 2,958 hours
  • Last inspection: annual inspection, December 1, 2022; 120 hours since
  • Maximum gross weight: 3,400 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Continental IO-520C (piston); 2,791 hours total

The flight

  • Departed from: STS Santa Rosa CA at 4:00 am
  • Flight plan: none
  • Runway 14/3, 6,000 ft by 150 ft

Weather at the time

  • Light: night
  • Wind: from 180° at 4 knots
  • Sky: clear
  • Temperature: 61°F (16°C), dew point 54°F (12°C)
  • Altimeter: 29.87 inHg
  • Observation at 8:53 pm from KSTS

Weather report (METAR): METAR KSTS 060353Z AUTO 18004KT 10SM CLR 16/12 A2987 RMK AO2

Injuries

FatalSeriousMinorNone
Flight crew1

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

5 documents, released by the NTSB on April 30, 2024. 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.