FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Grand Air Express Aerostar 601 accident

27 Jan 1996 · MOUNT STORM, WV, United States

Aerostar 601 · Accident: loss of engine power en route

From Gerald R. Ford International Airport (GRR) to Norfolk International Airport (ORF)

Report a problem

Event

NTSB case
BFO96LA040
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
0 · 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
Charter & commuter
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

Aerostar 601

Aircraft type
Aerostar 601
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
N162GA
Onboard fatalities
Unknown
Route
From Gerald R. Ford International Airport (GRR), Grand Rapids, MITo Norfolk International Airport (ORF), Norfolk, VA
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 135: Air Taxi & Commuter
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
Loss of engine power
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

  • Airframe › Ice
  • Reason for occurrence undetermined

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot stated that the airplane was in cruise flight at 8,000 feet MSL, when the right engine lost power. He advised ATC of the loss of power and received radar vectors toward an airport. The pilot said he maintained the best single-engine rate-of-climb speed, but the airplane's altitude 'drifted down.' When the airplane entered clouds, it began to accumulate structural icing and would not maintain sufficient altitude. The airplane impacted mountainous terrain about 16 miles northwest of the airport. The pilot stated that he had departed on the cargo flight with 5 hours of fuel on board for what he estimated to be a 2 1/2 hour flight. Also, he reported that conditions were dark and foggy, when the accident occurred. Postaccident examination of the engines and their systems revealed no evidence of preimpact mechanical malfunction. Examination of the airplane wreckage revealed no evidence of preimpact failure of the airframe or its systems. During a postaccident engine test run, the right engine started normally and operated satisfactorily.

Probable cause

loss of power in the right engine for undetermined reason(s), and the accumulation of structural ice on the airplane, which resulted in an increased rate of descent and a subsequent forced landing before the pilot could reach an alternate airport. Factors relating to the accident were: the adverse weather (icing) conditions, darkness, fog, and the lack of suitable terrain in the emergency landing area.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record BFO96LA040
Event ID
20001208X05103
Case number
BFO96LA040
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: 93a5f62eb7cb2749336d2e11736151edb9d65b36f37b64e7c6e2ef060443273e; retrieved 2026-09-18T17:54:16.817Z.