FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX04LA178 · Beech V35

5 Apr 2004 · Elko, NV, United States

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

From Elko Regional Airport (EKO) to Monmouth Executive Airport (BLM)

Report a problem

Event

NTSB case
LAX04LA178
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
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 V35

Aircraft type
Beechcraft 35
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
N7923M
Operator
Lee Morton
Onboard fatalities
Unknown
Route
From Elko Regional Airport (EKO), Elko, NVTo Monmouth Executive Airport (BLM), Belmar, NJ
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
Initial climb
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 control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/mush
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 › Airspeed, not attained
  • Pilot in command › Mixture, improper use of

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane collided with terrain during the takeoff initial climb. The pilot arrived at the airport the previous day and asked several questions of a locally based flight instructor, saying he was concerned about mountainous operations and leaning the mixture on the engine. A certified flight instructor answered the pilot's questions and felt that the pilot appeared to be a low-time private pilot that had not flown recently. On the accident flight departure, the pilot crossed a runway hold line while taxiing to the runway for takeoff. The air traffic controller queried the pilot and the pilot, who then requested a different runway. During the takeoff roll, the pilot queried the tower controller if there were noise abatement procedures. The airplane traveled approximately 5,000 feet down the 7,214-foot-runway prior to lifting off. It continued down the runway about 12 feet above ground level, and pilot witnesses said the engine did not sound like it was producing full power. The witnesses said the airplane was "wallowing" as it flew down the length of the remaining runway. The airplane barely cleared the airport perimeter fence and touched down about 80 yards from the fence. After the airplane collided with a series of obstacles, a post-impact fire consumed the airplane. Post accident examination by a Federal Aviation Administration inspector prior to disturbance of the wreckage revealed that the cockpit mixture control was approximately 3 inches aft of its full rich position. The engine was installed in an instrumented test cell and it ran smoothly, though it only produced a maximum of 2,550 rpm during the test run. The airport elevation is 5,140 feet msl. Based on the pilot's logbook entries, he had limited mountain flying experience and normally took a southern route when flying across country.

Probable cause

the pilot's improper mixture leaning technique and failure to attain an adequate airspeed during takeoff, which resulted in a stall/mush.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX04LA178
Event ID
20040409X00440
Case number
LAX04LA178
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: 5324d9c6ee8fbf07f1f4d51ca474e6409b0855d2f4479b4bad9d45f990abbc6e; retrieved 2026-09-21T09:18:25.833Z.