LAX06CA279 · Cessna T210G
Cessna T210G · Accident: loss of control in flight during landing
From Fresno Yosemite International Airport (FAT) to Lake Tahoe Airport (TVL)
Event
- NTSB case
- LAX06CA279
- 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 T210G
- 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
- N6821R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fresno Yosemite International Airport (FAT), Fresno, CATo Lake Tahoe Airport (TVL), S Lake Tahoe, 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
- 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- 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 › Airspeed, not maintained
- Pilot in command › Remedial action, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane ballooned in the landing flare and landed hard resulting in structural damage to the firewall. While on the approach, the pilot reviewed the automated surface observation system (ASOS) data three times, with 2 minutes separating the data. The wind intensity for the three readings was between 8 and 9 knots from directions that were from 210 degrees to 200 degrees with the final reading at 190 degrees. After review of the ASOS data the pilot elected to land on runway 18. While over the runway in ground effect, with the power reduced, the airplane abruptly gained altitude. The pilot reported that the airspeed was low and the airplane stalled and landed hard on the runway at an angle. The pilot stated that the airplane and engine had no preimpact mechanical failures or malfunctions.
Probable cause
the pilot's failure to maintain an adequate airspeed and his inadequate remedial actions during a balloon in the landing flare, which resulted in a stall and hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06CA279
- Event ID
- 20061018X01531
- Case number
- LAX06CA279
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-08-22.
- API snapshot SHA-256: 19b18d29f095763662817692bef4c67ab916d81f8af32fc6a3a44af6e3790ba3; retrieved 2026-09-22T04:31:29.189Z.