SEA06CA034 · Cessna 182G
Cessna 182G · Accident: on ground/water collision with terrain/water during takeoff
From 2OR7 · Sweet Home, OR to Corvallis Municipal Airport (CVO)
Event
- NTSB case
- SEA06CA034
- 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 182G
- 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
- N3199S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 2OR7 · Sweet Home, ORTo Corvallis Municipal Airport (CVO), Corvallis, 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
- Takeoff · roll/run
- 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 terrain/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 › Directional control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, when he began his departure roll, he had a clear view of the unlighted 2,100-foot-long by 20-foot-wide asphalt paved runway. Illumination was provided by street lights on parallel streets and the airplane's lights. Shortly after the takeoff roll began, the pilot "realized he could no longer see the runway edges." As soon as he made this realization, he felt the left main tire start to drag in the muddy ground next to the runway. He applied hard right rudder in an unsuccessful attempt to bring the left main tire back onto the pavement. He then realized that all of the wheels were off the pavement, pulled back on the yoke to keep the nose wheel up, and reduced power to abort the takeoff. After a "very short pause," he felt "the front of the plane dig in," and the airplane nosed over and came to rest inverted.
Probable cause
The pilot's failure to maintain directional control during the takeoff roll, which resulted in the airplane exiting the paved runway surface, encountering muddy terrain and nosing over. Contributing factors were the night light condition and the muddy terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA06CA034
- Event ID
- 20060106X00022
- Case number
- SEA06CA034
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2005-12-28.
- API snapshot SHA-256: fa6158f39aed2878d8efb365a713ed687d8fd675d168e3863011085c2bd4550a; retrieved 2026-09-21T18:50:43.527Z.