FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Alpine Aviation Flight 5008

23 May 2008 · Billings, MT, United States

Beech 1900C · Accident: loss of control in flight during initial climb

From Billings Logan International Airport (KBIL) to Great Falls International Airport (KGTF)

Report a problem

Event

NTSB case
SEA08FA135
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
1 · 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
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

Beech 1900C

Aircraft type
Beechcraft 1900
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
N195GA
Onboard fatalities
Unknown
Route
From Billings Logan International Airport (KBIL), Billings-Logan, MTTo Great Falls International Airport (KGTF), Great Falls, 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 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
Initial climb
Defining eventThe 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 control in flight
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

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

About one minute after takeoff on a night Instrument Flight Rules (IFR) contract cargo flight, the tower controller advised the pilot that he was squawking the wrong transponder code. Although the pilot reset the transponder to the correct code, he was advised that he was still squawking the wrong code. He then realized that he had selected the wrong transponder, and then switched to the correct one. During the time the pilot was dealing with this issue, the airplane drifted about 30 degrees right of the assigned heading, but the pilot returned to the correct heading as he was contacting the departure controller. The departure controller cleared him to continue his climb and instructed him to turn left about 120 degrees, which he did. About 40 seconds after initiating his left turn of about 120 degrees, while climbing straight ahead through an altitude about 4,700 feet above ground level (AGL), the pilot was instructed to turn 20 degrees further left. Almost immediately thereafter, the airplane began turning to the right, and then suddenly entered a rapidly descending right turn. The airplane ultimately impacted the terrain in a nearly wings-level nose-down attitude of greater than 45 degrees. At the moment of impact the airplane was on a heading about 220 degrees to the right of the its last stabilized course. The investigation did not find any indication of an airframe, control system, or engine mechanical failure or malfunction that would have precluded normal flight, and no autopsy or toxicological information could be acquired due to the high amount of energy that was released when the airplane impacted the terrain. The determination of the initiating event that led to the uncontrolled descent into the terrain was not able to be determined.

Probable cause

The pilot's failure to maintain aircraft control during the initial climb for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA08FA135
Event ID
20080530X00758
Case number
SEA08FA135
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 1e5bd34a2878e53867ec93621805316e122269efe9c7ce4d709a5345fcbecdc0; retrieved 2026-09-13T19:05:52.462Z.