FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA03CA138 · Beech F90

16 Jul 2003 · Sunriver, OR, United States

Beech F90 · Accident: overrun during landing

From McClellan Airfield (MCC) to Sunriver Airport (S21)

Report a problem

Event

NTSB case
SEA03CA138
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

Beech F90

Aircraft type
Beechcraft 90
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
N299KP
Operator
Terry J. Wallace · private individual
Onboard fatalities
Unknown
Route
From McClellan Airfield (MCC), Sacramento, CATo Sunriver Airport (S21), Sunriver, 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
Landing
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(cfi) › Distance, misjudged

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airline transport pilot reported that while landing on runway 18, he inadvertently touched down approximately halfway down the 5,455 foot long, asphalt covered runway. The pilot said that after the initial touchdown, he applied maximum braking and full reverse power. The airplane continued off the end off the runway, eventually coming to rest approximately 35 feet beyond the runway threshold. During the overrun, the airplane's right main gear collapsed, and the right wing struck the ground. In a subsequent written report, the pilot reported that the aircraft's right main wheel brake locked up during the landing roll. He also reported that he was landing with a tailwind. Runway 18 is serviced by a 2-box, 3 degree VASI.

Probable cause

The pilot's misjudgment of distance while landing, which resulted in a runway overrun. Factors include rough uneven terrain and a tailwind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA03CA138
Event ID
20030929X01609
Case number
SEA03CA138
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, coordinates. 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: 24195a1cc774c5f5950a06f2b6ae2ecafa67d0c3193c2f6deecbde5f9c775003; retrieved 2026-09-22T08:59:56.910Z.