FTW90LA035 · Beech V35
Beech V35 · Accident: total loss of engine power (mechanical failure) en route
From Lubbock Preston Smith International Airport (LBB) to Airpark East Airport (1F7)
Event
- NTSB case
- FTW90LA035
- 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 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
- N27007
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lubbock Preston Smith International Airport (LBB), Lubbock, TXTo Airpark East Airport (1F7), DALLAS AIRPARK, TX
- 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
- Total loss of engine power (mechanical failure)
- 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
- Fluid, oil › Loss, total
- Lubricating system, oil cooler › Undertorqued
- Other maintenance personnel › Maintenance, annual inspection, inadequate
- Other maintenance personnel › Maintenance, overhaul, major, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRCRAFT ENGINE FAILED, AFTER A COMPLETE LOSS OF OIL, DUE TO AN UNDERTORQUED OIL COOLER TO ENGINE ASSEMBLY THAT PERMITTED THE OIL TO BYPASS THE SEAL. THE ENGINE HAD BEEN IN SERVICE 162 HOURS SINCE OVERHAUL AND 3 HOURS SINCE ANNUAL INSPECTION. THE PILOT EXECUTED A FORCED LANDING TO ROUGH TERRAIN THAT CAUSED THE MAIN GEAR TO SHEAR, NOSE GEAR TO COLLAPSE, AND THE AIRCRAFT TO NOSE OVER.
Probable cause
IMPROPER OVERHAUL OF THE AIRCRAFT ENGINE BY MAINTENANCE PERSONNEL THAT LED TO THE COMPLETE LOSS OF ENGINE OIL DUE TO AN UNDERTORQUED OIL COOLER ASSEMBLY. FACTORS IN THE ACCIDENT WERE THE FAILURE OF MAINTENANCE PERSONNEL TO DETECT THE CONDITION DURING THE ANNUAL INSPECTION AND THE UNSUITABLE TERRAIN FOR THE FORCED LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW90LA035
- Event ID
- 20001213X29804
- Case number
- FTW90LA035
- 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: bea6afd5d29056a5e1a68d80d871db3e2dfe61fdd29f8adf31ed00b2fae7efed; retrieved 2026-09-21T23:58:59.718Z.