FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR26LA171 · Cessna 210 H

25 Apr 2026 · Redding, CA, United States

Cessna 210 H · Accident: landing gear not configured

From Nevada County Airport (GOO) to an unrecorded destination

Report a problem

Event

NTSB case
WPR26LA171
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
Event fatalities
Unknown
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 210 H

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
N6130F
Operator
Unknown
Onboard fatalities
Unknown
Route
From Nevada County Airport (GOO), Grass Valley, CATo not recorded
Aircraft age
About 58 years (built 1968)
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
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 › Psychological

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that he became distracted by converging traffic and the short runway while entering the traffic pattern. During the approach, he did not complete his before-landing checklist or extend the landing gear. He stated that because the engine rpm remained above the landing gear warning horn activation threshold during the approach, the horn did not sound. The airplane landed with the landing gear retracted and slid to rest on the runway, resulting in substantial damage to the lower fuselage. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot’s failure to extend the landing gear before landing due to distraction and his failure to conduct the before landing checklist.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR26LA171
Event ID
20260429202909
Case number
WPR26LA171
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: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: a1e463dbdbfce8f29eac068ef27eb4372fb6b6f9d5c2df068ceab386501b0359; retrieved 2026-09-16T21:21:11.518Z.