FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC01FA058 · Beech B200

22 Dec 2000 · Rangeley, ME, United States

Mountain Air Service Beech B200 · Accident: in flight collision with terrain/water on approach

From Portland International Jetport (PWM) to Steven A. Bean Municipal Airport (8B0)

Report a problem

Event

NTSB case
NYC01FA058
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
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 B200

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
N30EM
Onboard fatalities
Unknown
Route
From Portland International Jetport (PWM), Portland, METo Steven A. Bean Municipal Airport (8B0), Rangeley, ME
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 turn to base
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
Destroyed

Cause areas

  • Pilot in command › Altitude/clearance, 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 pilot and passenger departed on a night IFR flight. Weather en route was a mixture of instrument and visual meteorological conditions. When the airplane was 17 miles southwest of its destination, the pilot was cleared for an instrument approach. At 9 miles, the pilot reported the airport in sight, and canceled his IFR clearance. The airplane continued to descend towards the airport on a modified left base until radar contact was lost at 3,300 feet msl. The pilot was in radio contact with his wife just prior to the accident. He advised her that he was on base for runway 32. Neither the pilot's wife, nor ATC received a distress call from the pilot. The airplane was located the next morning about 100 feet below the top of a mountain. The accident site was 7.9 miles from the airport, and approximately 1,200 feet above the airport elevation. Ground based weather radar recorded light snow showers, in the general vicinity of the accident site about the time of the accident, and satellite imagery showed that the airplane was operating under a solid overcast. A level path was cut through the trees that preceded the main wreckage. Examination of both engines and the airframe revealed no pre impact failures or malfunctions.

Probable cause

The pilot-in-command's failure to maintain sufficient altitude while maneuvering to land, which resulted in a collision with terrain. Factors in the accident were the dark night, mountainous terrain, snow showers, clouds, and the pilot's decision to cancel his IFR clearance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC01FA058
Event ID
20010109X00069
Case number
NYC01FA058
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, coordinates. 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: aa9406cde4532dac3bf1adf2b00b90e548abae79397ec464cb225bd40c6abca7; retrieved 2026-09-20T20:43:16.605Z.