FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09CA044 · Cessna T210M

21 Nov 2008 · Hanford, CA, United States

Cessna T210M · Accident: landing gear not configured

From Crater Lake-Klamath Regional Airport (LMT) to Hanford Municipal Airport (HJO)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
WPR09CA044
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna T210M

Aircraft type
Cessna 210
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N732XS
Onboard fatalities
Unknown
Route Narrative disagrees
From Crater Lake-Klamath Regional Airport (LMT), Klamath Fall, ORTo Hanford Municipal Airport (HJO), Hanford, CA
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Landing gear not configured
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that while on a right downwind to runway 32 he accomplished the before-landing checklist from memory; however, "I forgot to say 'three green.'" The pilot said that he touched down about one-third of the way down the runway with the landing gear retracted and came to rest in an upright position on the runway at about the mid-field point. When asked if he had heard the gear warning horn prior to touching down, the pilot stated that he did not, as he had his headset on. An airframe and power plant mechanic reported that the airplane had sustained substantial damage to the lower fuselage. The pilot reported that no anomalies existed with the airplane prior to or during the flight.

Probable cause

The failure of the pilot to use the before-landing checklist and extend the landing gear prior to landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09CA044
Event ID
20081122X11050
Case number
WPR09CA044
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2008-11-22.
  • API snapshot SHA-256: 247e7d92d2fd9e8af65c155a6b3608ef298401a5d82ae7743c1fe2b5f24351ff; retrieved 2026-09-15T10:34:08.941Z.