SEA99LA164 · Cessna 182Q
Cessna 182Q · Accident: on ground/water collision with object during landing
From Rogue Valley International-Medford Airport (MFR) to 5S2
Event
- NTSB case
- SEA99LA164
- 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 182Q
- 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
- N22WR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rogue Valley International-Medford Airport (MFR), Medford, ORTo 5S2
- 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
- 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
- On ground/water collision with object
- 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 › Directional control, not maintained
Approximate · Estimated position: the centre of Crescent Lake, OR, the place the record names. Not the accident site.
NTSB narrative
The pilot flew over the airport to check the wind, and the windsock appeared to indicate that the wind was calm. She therefore continued around the pattern and landed on the end of the runway that was asphalt covered. During the flare, the aircraft dropped in from about four feet above the surface and bounced back into the air. Before it touched down again, it encountered a sudden crosswind from the right, which lifted the right wing higher into the air. Because the aircraft was in a left bank, it started to drift off the left side of the runway, and the pilot was unable to maintain enough directional control to keep it from departing the runway and impacting some nearby trees.
Probable cause
The pilot's failure to maintain directional control during a bounced landing. Factors include a sudden wind shift, a crosswind gust, and tall trees growing along the side of the airstrip.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA99LA164
- Event ID
- 20001212X19885
- Case number
- SEA99LA164
- 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. 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: f98ddd95175de51ee61c6ee59dc1168b1249fe12166c85988aca3cf689c77186; retrieved 2026-09-22T14:07:53.579Z.