SEA01TA050 · Beech 200
Washington State Patrol Aviation Section Beech 200 · Accident: overrun during landing
From Yakima Air Terminal McAllister Field (YKM) to Olympia Regional Airport (OLM)
Event
- NTSB case
- SEA01TA050
- 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
- Government
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Beech 200
- Aircraft type
- Beechcraft 200
- 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
- N222KA
- Onboard fatalities
- Unknown
- Route
- From Yakima Air Terminal McAllister Field (YKM), Yakima, WATo Olympia Regional Airport (OLM), Olympia, WA
- 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
- Public Aircraft
- 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 › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The aircraft was on an instrument landing system (ILS) approach to runway 17. Reported visibility at the time was 1/4 mile in fog, below the published minimum approach visibility of 1/2 mile. The pilots reported that on the approach, the copilot called the approach lights in sight 100 feet above decision height (DH), and the runway in sight at decision height. The pilot visually acquired the runway a few seconds later and continued toward the runway for landing. Several passengers reported that the airplane subsequently floated or landed long, and the pilot reported that as the aircraft settled in for landing, he observed the touchdown zone markers at the departure end approaching rapidly. The airplane subsequently overran the runway, coming to a stop in the dirt 442 feet beyond the departure end. The aircraft's right main landing gear collapsed during the overrun.
Probable cause
The pilot's failure to attain the proper touchdown point for landing. A factor was weather conditions below published approach minimums.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA01TA050
- Event ID
- 20010301X00529
- Case number
- SEA01TA050
- 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: f851b413a4b014c498a6156658be15a8c253f43f59abd5a56b72bdceac583306; retrieved 2026-09-18T21:20:50.194Z.