FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA98LA117 · Cessna 182N

2 Jul 1998 · BIG CREEK, ID, United States

Cessna 182N · Accident: on ground/water collision with object during landing

From Lewiston Nez Perce County Airport (LWS) to Big Creek Airport (U60)

Report a problem

Event

NTSB case
SEA98LA117
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 182N

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
N92519
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lewiston Nez Perce County Airport (LWS), Lewiston, IDTo Big Creek Airport (U60), BIG CREEK, ID
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 · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that he over flew the airstrip twice before setting up for final approach. The pilot stated that while on final approach, the airplane was high so he slipped the airplane to descend. The airplane landed within the first 1/3 of the length of the airstrip in a full stall on the main landing gear. The pilot stated that the touch down was on the left side of the centerline due to cones that were placed on the airstrip. The pilot reported that from the point of touchdown to impact with the fence, the airplane was gradually sliding to the left. The pilot tried to correct with right rudder control and braking action, however, the airplane continued to the left and collided with a fence. The pilot reported that the grass airstrip was wet and that the surface was rougher than what he had remembered from previous flights into the airstrip. The pilot reported that there were no mechanical failures or malfunctions with the airplane at the time of the accident.

Probable cause

Directional control was not maintained. A wet runway surface was a factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA98LA117
Event ID
20001211X10700
Case number
SEA98LA117
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 1998-07-03.
  • API snapshot SHA-256: 126a53bf241e772635f649f110bb3f28e158906902002595911ebb931fbb39d4; retrieved 2026-09-21T20:47:26.587Z.