CHI95FA011 · Beech 58
Aviation Resources Beech 58 · Accident: in flight collision with object en route
From Hector International Airport (FAR) to Walker Municipal Airport (Y49)
Event
- NTSB case
- CHI95FA011
- 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
- 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
- N258CH
- Operator
- Aviation Resources
- Onboard fatalities
- Unknown
- Route
- From Hector International Airport (FAR), Fargo, NDTo Walker Municipal Airport (Y49), Walker, MN
- 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
- En route · cruise
- 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 object
- 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
- Tree(s)
- 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 obtained/maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FLIGHT DEPARTED FARGO, NORTH DAKOTA ON OCTOBER 7, 1994, AT 2010 CENTRAL DAYLIGHT TIME WITH THE INTENDED DESTINATION OF WALKER, MINNESOTA. THE AIRPLANE WENT MISSING AND WAS FOUND DESTROYED ON OCTOBER 14, 1994, 10 MILES SOUTHEAST OF THE INTENDED DESTINATION. THERE IS NO INDICATION THAT THE PILOT-IN-COMMAND OBTAINED A WEATHER BRIEFING. THE FLIGHT WAS CONDUCTED ON A DARK NIGHT. RESIDENTS IN THE AREA OF THE ACCIDENT STATED THAT IFR CONDITIONS PREVAILED AT THE APPROXIMATE TIME OF THE ACCIDENT. THE AIRPLANE IMPACTED TREES ON HIGH TERRAIN ON A COURSE CONSISTENT WITH A HEADING TO THE AIRPORT OF INTENDED LANDING.
Probable cause
the pilot-in-command's failure to obtain/maintain clearance. Factors were a dark night, low ceiling, high terrain, and weather service not used by the pilot-in-command.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI95FA011
- Event ID
- 20001206X02395
- Case number
- CHI95FA011
- 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 1994-10-08.
- API snapshot SHA-256: 314de84e90ef750891efb0dacf06f4c1e1864a50880510eeec1ced2e47c7c553; retrieved 2026-09-20T23:58:50.612Z.