FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW83LA160 · Beech K35

18 Mar 1983 · TORREON, NM, United States

Beech K35 · Accident: in flight encounter with weather en route

From 4AC · Albuquerque, NM to Four Corners Regional Airport (FMN)

Report a problem

Event

NTSB case
FTW83LA160
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
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 K35

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
N5395E
Operator
Unknown
Onboard fatalities
Unknown
Route
From 4AC · Albuquerque, NMTo Four Corners Regional Airport (FMN), Farmington, NM
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
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
In flight encounter with weather
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
Fuel exhaustion
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

  • Pilot in command › Flight into known adverse weather, initiated
  • Pilot in command › Fuel tank selector position, improper
  • Pilot in command › Fuel tank selector position, selected
  • Pilot in command › Weather evaluation, disregarded

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

NTSB narrative

THE PILOT, WHO WAS NOT CERTIFICATED, STATED THAT PRIOR TO DEPARTURE HE RECEIVED A WX BRIEFING BY TELEPHONE FROM THE FSS. ENROUTE, AFTER MAKING SEVERAL HEADING CHANGES TO AVOID WX HE FOUND HIMSELF SURROUNDED BY LOW CEILING AND PRECIPITATION. HE DECIDED TO MAKE A PRECAUTIONARY LANDING ON A PAVED ROAD. ON THE FINAL TURN, THE ENGINE QUIT DUE TO FUEL EXHAUSTION. THE PILOT HAD SWITCHED TO HIS AUXILIARY TANK JUST PRIOR TO DECIDING TO LAND AND NEGLECTED TO SWITCH BACK TO THE MAIN TANKS.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record FTW83LA160
Event ID
20001214X42445
Case number
FTW83LA160
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: 58127d4c2768b52fbf245d1e578a75d623cca7924a89c5e3f3cfcb71b0fda107; retrieved 2026-09-23T22:45:22.614Z.