LAX98LA291 · Cessna T210R
Cessna T210R · Accident: hard landing
From Minden-Tahoe Airport (MEV) to an unrecorded destination
Event
- NTSB case
- LAX98LA291
- 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
- 0
- 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 T210R
- 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
- N6153U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Minden-Tahoe Airport (MEV), MINDEN-TAHOE, NVTo not recorded
- 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
- 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
- Hard landing
- 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 › Aborted landing, delayed
- Pilot in command › Recovery from bounced landing, delayed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Although the windsock indicated runway 09, the pilot elected to land downwind because of obstructions on the departure end of runway. He touched down at 80 knots with 30 degrees flaps, about 150 feet beyond the runway threshold. After the aircraft bounced several times, he added 'some' power to stabilize the oscillations. Now nearing the departure end of the runway, he became concerned that he would not be able to stop. He applied power to abort the landing and raised his flaps to 20 degrees. During the abort, the aircraft stuck a car that was traveling along the airport boundary. After striking the vehicle, the elevator controls became jammed. The pilot reduced power and made a forced landing. A witness estimated winds as from the east at 10 knots gusting to 15. Skid marks were visible near the left side of the departure end of the runway. A postaccident inspection showed the flaps were at 10 degrees.
Probable cause
the pilot's delayed response in recovering from a bounced landing combined with his delayed decision to abort the landing. The pilot's inadequate compensation for tailwind conditions and inadvertently raising the flaps to 10 degrees were factors in this accident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX98LA291
- Event ID
- 20001211X11101
- Case number
- LAX98LA291
- 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. 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: 7880d1c46d69c7fe521fcbc4c7fe1c372427bfc5cc0ab8a36ae50a5e5505a6fa; retrieved 2026-09-21T20:41:45.173Z.