CHI03LA076 · Cessna T210L
Cessna T210L · Accident: loss of control in flight on approach
From Cherry Capital Airport (TVC) to Oakland Southwest Airport (Y47)
Event
- NTSB case
- CHI03LA076
- 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 T210L
- 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
- N123JL
- Operator
- Charles J. Hass · private individual
- Onboard fatalities
- Unknown
- Route
- From Cherry Capital Airport (TVC), Traverse City, MITo Oakland Southwest Airport (Y47), New Hudson, MI
- 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
- Approach · VFR pattern final
- 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/mush
- 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, inadequate
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 sustained substantial damage when it impacted terrain while on approach to land. The pilot stated that he was a little high on final approach, so he reduced the throttle and lowered the nose. He reported that when the airplane was 200 to 300 feet from the end of the runway, at a ground speed of 83 knots, the nose of the airplane veered to the left. The pilot reported he was unable to realign the nose of the airplane using the rudder, and then the left wing stalled. He reported he was able to get the wings almost level prior to the airplane impacting ground. The airplane came to rest approximately 50 to 70 feet south of the runway, and 50 to 60 feet prior to the approach end of the runway. Examination of the airplane showed control surface continuity.
Probable cause
The pilot's failure to maintain aircraft control which resulted in the airplane stalling while on final approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI03LA076
- Event ID
- 20030304X00277
- Case number
- CHI03LA076
- 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: 62c615a6d024230792d042cb38ba716def7d248a9317e32bccc90b46490a146a; retrieved 2026-09-21T19:31:56.862Z.