SEA01FA167 · Beech 58
Beech 58 · Accident: in flight collision with terrain/water while maneuvering
From Ashland Municipal Airport Sumner Parker Field (S03) to Scottsdale Airport (SDL)
Event
- NTSB case
- SEA01FA167
- 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
- 3 · 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
- Instrument Meteorological Cond
Beech 58
- Aircraft type
- Beechcraft 58
- 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
- N18414
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ashland Municipal Airport Sumner Parker Field (S03), Ashland, ORTo Scottsdale Airport (SDL), Scottsdale, AZ
- 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
- Maneuvering
- 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
- In flight collision with terrain/water
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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
- Pilot in command › Clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The aircraft made a visual flight rules (VFR) departure from the airport underneath a solid overcast, and headed in a direction that took it toward rising mountainous/hilly terrain. In the area where the pilot approached the mountainous terrain, the clouds were touching the top of the ridges in all quadrants, but the visibility underneath the overcast was extensive. As the pilot attempted to maneuver the aircraft below the overcast in the restrictive environment of the mountain valleys, he inadvertently entered the cloud base, and soon thereafter collided with the terrain.
Probable cause
The pilot's failure to maintain clearance from the terrain after inadvertently entering an area of instrument meteorological conditions (IMC) during a visual flight rules (VFR) flight. Factors include mountainous/hilly terrain and low ceilings in the area where the pilot was maneuvering.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA01FA167
- Event ID
- 20010924X01979
- Case number
- SEA01FA167
- 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: ded6288a6ebe519b3cec5900f6f5677b8e58e8ebf60db80619e561e3e6fc6815; retrieved 2026-09-20T20:22:57.693Z.