WPR09CA478 · Cessna T210J
Cessna T210J · Accident: system/component malfunction/failure (non-power) during landing
From Corvallis Municipal Airport (KCVO) to Albany Municipal Airport (S12)
Event
- NTSB case
- WPR09CA478
- 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 T210J
- 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
- N899KM
- Operator
- Deborah Criger
- Onboard fatalities
- Unknown
- Route
- From Corvallis Municipal Airport (KCVO), Corvallis, ORTo Albany Municipal Airport (S12), Albany, OR
- 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
- 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
- System/component malfunction/failure (non-power)
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After an uneventful touchdown for a full-stop landing, the pilot initially raised the nose of the airplane for the purpose of aerodynamic braking. She then lowered the nose wheel to the runway, and began to apply the wheel brakes. At that time she discovered that there was no resistance from the left brake pedal, and that the left brake was not working. Although she applied the right brake hard, that wheel began to skid, and the airplane departed the right side of the end of the runway. After departing the runway, the airplane's horizontal stabilizer impacted a runway sign support box. An inspection of the left brake master cylinder by a Federal Aviation Administration Airworthiness Inspector determined that it contained only residual hydraulic fluid near its bottom, and that fluid had been leaking past the shaft that protrudes from the master cylinder and connects to the brake pedal.
Probable cause
The malfunction of the left main wheel brake during landing due to inadequate hydraulic fluid in the left brake pedal master cylinder due to leakage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09CA478
- Event ID
- 20091013X34003
- Case number
- WPR09CA478
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2009-09-14.
- API snapshot SHA-256: 8586b26d5f87adf2862a41240ac50ab629de05f359a57f238ec9cd8bfd44cd35; retrieved 2026-09-15T13:24:15.618Z.