FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24LA109 · Raytheon Aircraft Company B200

12 Mar 2024 · Billings, MT, United States

Teton Leasing Raytheon Aircraft Company B200 · Accident: electrical system malfunction/failure en route

From Billings Logan International Airport (KBIL) to Colstrip Airport (M46)

Report a problem

Event

NTSB case
WPR24LA109
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
Event fatalities
Unknown
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

Raytheon Aircraft Company 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
N299AV
Onboard fatalities
Unknown
Route
From Billings Logan International Airport (KBIL), Billings, MTTo Colstrip Airport (M46), Colstrip, MT
Aircraft age
About 25 years (built 1999)
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
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
Electrical system malfunction/failure
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

  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision

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 stated that shortly after departure, the airplane lost all electrical power. While descending and returning to the airport, the pilot attempted to manually extend the landing gear but could not verify they were in the down-and-locked position because the landing gear indicator lights were not operational. With the flaps retracted, the airplane touched down on the runway and the landing gear collapsed. According to the airplane’s Pilot’s Operating Handbook (POH), the engine start procedure required sequencing to ignite the engine before placing each generator online. To turn the generator on, the generator control switch must first be held upward in the spring-loaded “GEN RESET” position for a minimum of one second, then released to the “ON” position. The electrical system is designed so that the starter circuit has priority over the generator circuit, prohibiting a generator from coming online until the starter is fully disengaged. Placing the ignition and engine start switch into any position except “OFF” results in the same-side generator shutting off, and it is not possible to bring the generator online until the ignition and engine start switch is moved to the “OFF” position. The POH also instructs the pilot to unstow and pump the alternate extension handle to perform a manual gear extension. It states, “If one or more green gear-down annunciators do not illuminate for any reason and a decision is made to land in this condition,” the pilot should continue pumping the handle “until maximum resistance is felt.”

Postaccident examination of the airplane revealed that the generator caution lights were not operational and it is unlikely that the pilot tested them. Capacity testing of the battery indicated that its condition was slightly less than that of a normally functioning battery, which is likely partially the reason the battery lasted just 18 minutes after start, rather than the specified 30 minutes. Additionally, the 30-minute battery life assumes that only essential electrical equipment is operating.

No mechanical anomalies were found during the postaccident manual extension of the landing gear. The pilot stated that, during training for emergency manual landing gear extension procedures, he consistently verified illumination of three green indicator lights, confirming that the landing gear was in the down-and-locked position. During the accident flight, he was unable to obtain this visual confirmation due to the complete electrical power loss, which rendered the gear position indicator lights inoperative.

It is likely that the pilot inadvertently turned on the starter switches or did not reset the generators, which led to depletion of the battery and loss of electrical power to the airplane's systems. If the pilot had followed the emergency procedures and had continued to pump the manual landing gear extension handle, he likely could have lowered the landing gear.

Probable cause

The pilot's improper engine start, resulting in the engine starters remaining engaged and the generators not being activated, which led to the discharge of the airplane’s battery and subsequent total electrical failure after takeoff. Contributing to the accident were generator caution lights not illuminating and the pilot’s inadequate manual landing gear extension, resulting in a landing with the gear not down and locked.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24LA109
Event ID
20240312193926
Case number
WPR24LA109
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, cause areas. 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: a349d0c55d06d2619bd4fa62ed0d3af7eaa21c36bf6faadc7e6c746994e96540; retrieved 2026-09-16T18:35:24.247Z.