FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA02LA006 · Cessna 182P

13 Oct 2001 · Sulfur Creek, ID, United States

Cessna 182P · Accident: on ground/water collision with terrain/water during takeoff

From Sulfur Creek, ID to Indian Creek US Forest Service Airport (S81)

Report a problem

Event

NTSB case
SEA02LA006
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 182P

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
N20877
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sulfur Creek, IDTo Indian Creek US Forest Service Airport (S81), Indian 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
Takeoff · rejected takeoff
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During the takeoff roll, the pilot over-rotated, causing the aircraft's tail cone to strike the runway surface. He then maintained this excessive pitch attitude as the aircraft continued to roll down the runway. The pilot eventually became convinced that he would not be able to ensure a safe takeoff if he continued. He therefore aborted the takeoff. During the abort, he allowed the aircraft to drift to the side of the runway, where one of the main gear encountered soft terrain. After encountering the soft terrain, the aircraft veered off the side of the runway surface, where the nose wheel encountered soft/wet terrain conditions. Soon thereafter, the nose wheel sank into the terrain and the aircraft nosed over.

Probable cause

The pilot's failure to maintain directional control during the aborted takeoff. Factors include the pilot's excessive rotation attitude, and soft/wet terrain conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA02LA006
Event ID
20011018X02108
Case number
SEA02LA006
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: 76222d87a6366800d04c05efb10c1126e18d16b93b5dd82cda44b6be73397aea; retrieved 2026-09-22T11:31:11.436Z.