FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA01LA012 · Cessna 172P

2 Nov 2000 · WALDRON ISLAND, WA, United States

Cessna 172P · Accident: overrun during landing

From OLY · Olympia, WA to Waldron Airstrip (90WA)

Report a problem

Event

NTSB case
SEA01LA012
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 172P

Aircraft type
Cessna 172
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
N65923
Operator
Unknown
Onboard fatalities
Unknown
Route
From OLY · Olympia, WATo Waldron Airstrip (90WA)
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
Overrun
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 › Distance/speed, improper

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

NTSB narrative

The private pilot reported that upon arrival in the area of the private 2,700 foot long, gravel airstrip, he executed a descending 360-degree turn to lose altitude, and then lined up to land to the southeast under light and variable wind conditions. He reported sequentially lowering the flaps to 30 degrees on the approach and then experienced a rapid descent rate. The touchdown was reported as within the first third of the runway at 60 knots. He then applied braking but felt the aircraft was not decelerating adequately. He then applied heavier braking during which the brakes locked and the aircraft continued off the upwind end of the runway impacting trees. A commuter pilot who landed at the airstrip about one hour later reported, 'Skid marks were present in the gravel approximately the last 500 feet of the runway to where the aircraft was resting in the trees' and the airstrip was 'not for the inexperienced' pilot. The aircraft flight manual for the Cessna 172P provided a 'Short Field' landing distance planning table which showed that at sea level and a weight of 2,400 pounds (maximum gross weight) and 10 degrees Centigrade, a ground roll distance of 530 feet was expected with a total distance of 1,265 feet to clear a 50 foot obstacle. The landing criteria were based upon no wind, flaps 30 degrees, power off, and maximum braking on a level, dry, paved runway. No mechanical malfunction of the aircraft's brakes or wheels was noted following the accident.

Probable cause

The pilot's improper distance/speed during the approach, which lead to an overrun during the landing roll and subsequent collision with trees. A factor was the trees beyond the upwind end of the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA01LA012
Event ID
20001212X22339
Case number
SEA01LA012
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: 395f3a561f7e8b30189e9daf556da7b5b567d888a36a8e216f98edd1240c0128; retrieved 2026-09-22T12:20:43.766Z.