SEA96LA013 · Cessna TR182
Cessna TR182 · Accident: airframe, component or system failure en route
From Vernal Regional Airport (VEL) to U42
Event
- NTSB case
- SEA96LA013
- 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 TR182
- Aircraft type
- Cessna 182
- 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
- N4664S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Vernal Regional Airport (VEL), Vernal, UTTo U42
- 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
- En route · cruise
- 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
- Airframe, component or system failure
- 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
- Hydraulic system, line › Chafed
- Other maintenance personnel › Maintenance, installation, improper
- Throttle/power lever, cable › Not secured
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that the landing gear did not come down on final approach, and that he was unable to obtain a safe gear indication using either normal or emergency extension. The pilot reported that a 38-knot left crosswind component existed for the landing. The airplane's maximum demonstrated crosswind is 18 knots. The right main gear collapsed on landing roll and the aircraft departed the right side of the runway. A post-accident inspection revealed that a nylon wire tie securing the throttle cable had broken, and that a hole had been chafed in the hydraulic pressure outlet line between the main hydraulic power pack and the landing gear selector valve. The chafed hole was in the area of the unsecured throttle cable. The hydraulic line had been repaired in 1980 by splicing in an additional piece and was 1/2 inch longer than a new hydraulic line. A new hydraulic line, when installed, had adequate clearance with the throttle cable.
Probable cause
maintenance personnel improperly installed a landing gear system hydraulic line and the throttle cable which resulted in chaffing and subsequent loss of hydraulic fluid disabling the landing gear extention systems.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA96LA013
- Event ID
- 20001207X04795
- Case number
- SEA96LA013
- 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 1995-10-28.
- API snapshot SHA-256: da8abc7a51852968934cac39127488735d9711892fb62a421d09e2e9724ae62f; retrieved 2026-09-22T23:05:39.597Z.