SEA98FA023 · Aero Commander 690A
Aero Commander 690A · Accident: loss of control in flight on approach
From King County International Airport - Boeing Field (BFI) to Yakima Air Terminal McAllister Field (YKM)
Event
- NTSB case
- SEA98FA023
- 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
- 2 · 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
Aero Commander 690A
- Aircraft type
- Aero Commander 690
- 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
- N72VF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From King County International Airport - Boeing Field (BFI), Seattle, WATo Yakima Air Terminal McAllister Field (YKM)
- 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
- Approach · VFR pattern final
- 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
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight was operating into the Yakima airport at night during the period the airport operates as non-towered. Some witnesses reported the aircraft initially appeared lower than normal and that it descended and impacted the ground at a steep angle, and some witnesses reported an abrupt entry into the descent. The aircraft crashed 2.2 nautical miles east of the runway threshold, slightly right of the localizer course The pilot was 'cleared for approach' by air traffic control (ATC) and he subsequently initiated an instrument landing system (ILS) approach to runway 27. The last radar position showed the aircraft approximately on the localizer, at glide slope intercept altitude, 9 nautical miles east of the airport. Three minutes after the last radar position, the pilot reported to ATC he had broken out and had the airport in sight, and canceled instrument flight rules (IFR). ATC then terminated service and approved a frequency change.. Ceiling was 1,500 feet overcast with 6 miles visibility in mist, with no significant icing forecast. No evidence of mechanical problems was found; however, much of the aircraft was consumed by an intense post-crash fire.
Probable cause
A loss of aircraft control for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA98FA023
- Event ID
- 20001208X09378
- Case number
- SEA98FA023
- 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 1997-12-13.
- API snapshot SHA-256: 01741b4dc6dce314b6b2922c373ece0324c7634915d78d11ecd6d48386e3b2e7; retrieved 2026-09-20T22:43:50.369Z.