LAX95LA250 · Cessna 170
Cessna 170 · Accident: loss of control on ground/water during landing
From Rogue Valley International-Medford Airport (MFR) to O22
Event
- NTSB case
- LAX95LA250
- 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 170
- Aircraft type
- Cessna 170
- 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
- N3981V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rogue Valley International-Medford Airport (MFR), Medford, ORTo O22
- 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 on ground/water
- 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 › Compensation for wind conditions, inadequate
- Pilot in command › Directional control, not maintained
- Pilot in command › Wrong runway, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
COLUMBIA AIRPORT HAS TWO RUNWAYS AVAILABLE FOR USE. RUNWAY 17-35 IS ASPHALT AND 4,670 FEET LONG, AND RUNWAY 29-11 IS A SHORTER TURF RUNWAY 2,000 FEET LONG. THE PILOT STATED THAT WHILE INBOUND TO THE AIRPORT HE ATTEMPTED TO CONTACT THE AIRPORT ON THE CTAF FOR AN AIRPORT ADVISORY; HOWEVER, COULD NOT GET A RESPONSE. HE THEN LISTENED TO THE AIRPORT WEATHER FROM THE AUTOMATED WEATHER OBSERVING SYSTEM (AWOS) AND LEARNED THAT THE WINDS WERE FROM 280 DEGREES AT 6 KNOTS. THE PILOT ELECTED TO LAND ON RUNWAY 17. THE PILOT SAID THAT DURING THE LANDING ROLL, A STRONG WIND GUST CAME FROM THE RIGHT REAR AND HE LOST DIRECTIONAL CONTROL. THE PILOT NOTED THAT HE COULD NOT REGAIN CONTROL, EVEN WITH FULL RUDDER AND BRAKE APPLICATION. THE AIRCRAFT GROUND LOOPED INTO A DITCH, DAMAGING THE FUSELAGE STRUCTURE AT THE LANDING GEAR ATTACH POINTS.
Probable cause
the pilot's selection of the wrong runway for the existing wind conditions; his inadequate compensation for the resulting crosswind situation; and his failure to maintain directional control of the aircraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX95LA250
- Event ID
- 20001207X03998
- Case number
- LAX95LA250
- 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-07-13.
- API snapshot SHA-256: 99cae5a36b619822cd30819e2bfcc55e105b8bb37223d2f08cdbbf47c83e02a4; retrieved 2026-09-22T23:37:57.255Z.