FTW87FA129 · Beech B-60
Beech B-60 · Accident: total loss of engine power (non-mechanical) en route
From San Angelo Regional Mathis Field (SJT) to San Antonio International Airport (SAT)
Event
- NTSB case
- FTW87FA129
- 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 B-60
- Aircraft type
- Beechcraft B-60
- 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
- N4314W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From San Angelo Regional Mathis Field (SJT), San Angelo, TXTo San Antonio International Airport (SAT), San Antonio, 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 (non-mechanical)
- 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; Tree(s)
- 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, fuel › Exhaustion
- Pilot in command › Complacency
- Pilot in command › Fuel consumption calculations, not performed
- Pilot in command › Refueling, disregarded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
ACFT WAS DESTROYED DURING AN ATTEMPTED OFF AIRPORT EMERGENCY LANDING FOLLOWING A DUAL ENG FAILURE WHILE LEVELING OFF AT CRZ FLT. PLT STATED THAT LEFT ENG, THEN RIGHT ENG SURGED AND QUIT AS HE WAS LEVELING OFF AT 9000' MSL. AT THE TIME OF THE ENG FAILURES THE FUEL TOTALIZER WAS READING 60 GAL, BUT THE ACFT FUEL GAUGES WERE READING EMPTY. PLT BROKE OUT OF OVC AT 3500 MSL (ABOUT 1200' AGL) AND WAS UNABLE TO FIND A SUITABLE CLEAR AREA TO LAND BEFORE COMMITTING TO AN EMERGENCY LANDING IN TREES. GEAR WAS DOWN, FLAPS WERE UP AND NEITHER ENG WAS FEATHERED AT IMPACT. PLT STATED THAT HE KNEW HE WAS OUT OF GAS WHEN BOTH ENGS QUIT AND THAT HE DID NOT ATTEMPT AN AIR START.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW87FA129
- Event ID
- 20001213X30936
- Case number
- FTW87FA129
- 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: f39521ebc1798e17a0f09a01bf6113d06b43cba701e82820752ce1e78134b0ae; retrieved 2026-09-21T16:29:25.981Z.