SEA07FA051 · Beech 200
Beech 200 · Accident: in flight collision with terrain/water en route
From Great Falls International Airport (GTF) to Bozeman Yellowstone International Airport (BZN)
Event
- NTSB case
- SEA07FA051
- 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
- Visual 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
- N45MF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Great Falls International Airport (GTF), Great Falls, MTTo Bozeman Yellowstone International Airport (BZN), Belgrade, MT
- 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 · descent
- 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
- 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 › Altitude/clearance, not maintained
- Pilot in command › Descent, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The cross-country flight was on an instrument flight rules (IFR) flight plan, approximately 42 nautical miles from the tower-controlled destination airport, when the pilot was cleared for the visual approach. Dark night visual meteorological conditions prevailed, and there was an overcast layer of clouds at 11,000 feet. After the en route radar service was terminated, the pilot contacted the local control tower and made a garbled and partially unintelligible transmission. Shortly after the time of the transmission, local law enforcement personnel received reports of a downed aircraft. The wreckage was located later that evening approximately 80 feet below the peak of a ridge that rose to an elevation of approximately 5,700 feet. From the initial point of contact with terrain, the debris path was scattered over the crest of the ridge and continued down the opposing side, in a south-southeast direction, toward the airport. The ridge was the highest obstruction between the accident location and the destination airport. The airport is located in a large valley and is surrounded by rising mountainous terrain. At night, clouds and terrain are difficult for pilots to see, and a gradual loss of visual cues can occur as flight is continued toward darker terrain. Additionally, the horizon is less visible and less distinct at night than during the day. Because the pilot was descending the airplane over rural, mountainous terrain that provided few visual ground reference cues, and because the overcast cloud layer would have prevented moonlight from illuminating the terrain, it is likely that the pilot did not see the rising terrain as the airplane continued toward it. The airplane was equipped with an Enhanced Ground Proximity Warning System; however, impact damage to the unit precluded post accident testing. It is not known how the unit was configured during the flight or what type of alerts the pilot received prior to impact. Post accident examination of the wreckage, to include both engines, did not disclose evidence of a mechanical malfunction prior to impact. Additionally, no evidence was found to suggest an in-flight structural failure.
Probable cause
The pilot's failure to maintain an adequate altitude and descent rate during a night visual approach. Dark night conditions and mountainous terrain are factors in the accident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA07FA051
- Event ID
- 20070214X00187
- Case number
- SEA07FA051
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2007-02-07.
- API snapshot SHA-256: 11c51c4ac7dfbe8f11fccda83a11e4fcb92879ba8f93fa826c680ec219192423; retrieved 2026-09-20T16:51:56.758Z.