FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05CA235 · Cessna T210M

14 Jul 2005 · TwentyninePalms, CA, United States

Cessna T210M · Accident: overrun during landing

From General William J Fox Airfield (WJF) to Bauer Airport (61CA)

Report a problem

Event

NTSB case
LAX05CA235
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
N210NS
Operator
Billy D. Bouldin · private individual
Onboard fatalities
Unknown
Route
From General William J Fox Airfield (WJF), Lancaster, CATo Bauer Airport (61CA), 29 Palms, 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 · landing roll
First occurrenceThe 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
Overrun
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

  • Pilot in command › Wind information, not verified
  • Pilot in command › Wrong runway, selected

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

NTSB narrative

The airplane overran the runway's end and skidded into a block wall during a downwind landing. Prior to takeoff, the pilot had spoken with the airstrip's owner who reported that the wind was calm. Upon arriving at the airport, the pilot made a straight-in approach to runway 09 without first verifying the local wind direction. Runway 27 was available for use. The airport was equipped with windsocks that were at the approach ends of both runways, and witnesses said the winds were from the west at approximately 15 knots. The pilot said that during rollout about midway down the runway, the airplane seemed to accelerate. There was insufficient remaining runway on the 2,000-foot-long dirt airstrip to go-around, so the pilot applied brakes. The airplane impacted the block wall at 20 mph. The pilot reported that there were no mechanical malfunctions.

Probable cause

the pilot's failure to verify the current local wind condition that resulted in his selection of the wrong runway and an inadvertent downwind landing, a runway overrun and a ground collision with objects. A factor in the accident was the short runway and its dirt surface, which reduced brake effectiveness.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05CA235
Event ID
20050907X01404
Case number
LAX05CA235
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 6823f00ff8e035c35d29faef6a3650bfbd9f0c93f9e1e9971b94aaee289259d4; retrieved 2026-09-22T05:39:30.530Z.