FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA99LA145 · Cessna 182J

22 Aug 1999 · YELLOW PINE, ID, United States

Cessna 182J · Accident: on ground/water collision with terrain/water during landing

From Johnson Creek Airport (3U2) to Krassel US Forest Service Airport (24K)

Report a problem

Event

NTSB case
SEA99LA145
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 182J

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
N2808F
Operator
Unknown
Onboard fatalities
Unknown
Route
From Johnson Creek Airport (3U2), JOHNSON CREEK, IDTo Krassel US Forest Service Airport (24K)
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 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 › Planned approach, misjudged
  • Pilot in command › Proper touchdown point, not attained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The aircraft crossed the landing threshold a little high and floated down the runway before touching down. When the aircraft touched down (approximately midfield), the pilot applied maximum braking and intentionally ground-looped in an effort to stop. The aircraft skidded off the end of a 1,500 foot runway, down an 85 foot embankment, and nosed over. The aircraft sustained substantial damage to the firewall and both wings. There were no mechanical malfunctions or failures reported by the pilot at the time of the accident.

Probable cause

Misjudged approach resulting in landing long. Factors include an intentional ground-loop, excessive airspeed and an embankment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA99LA145
Event ID
20001212X19653
Case number
SEA99LA145
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 1999-08-23.
  • API snapshot SHA-256: 600bd6b5fbc584e8655b5a7cf8c7ce28b9486a6d051d671ff19b76fefcd5fb10; retrieved 2026-09-21T20:25:06.442Z.