DFW05CA068 · Beech BE77
Beech BE77 · Accident: total loss of engine power (non-mechanical) en route
From Houston Southwest Airport (AXH) to Texas Gulf Coast Regional Airport (LBX)
Event
- NTSB case
- DFW05CA068
- 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 BE77
- Aircraft type
- Beechcraft 77
- 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
- N6717S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Houston Southwest Airport (AXH), Houston, TXTo Texas Gulf Coast Regional Airport (LBX), ANGLETON/LAKE J, 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
- 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 › In-flight planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 700-hour pilot was unable to restart the engine after the engine stopped producing power approximately 30 minutes after take-off, while in cruise flight for a short cross-country flight. The pilot elected to perform an emergency landing on a feeder road for a four-lane State Highway. During the landing roll on the feeder road, the left wing was sheared off just outboard of the wing-walk area, when it collided with a signpost on the shoulder of the road. The airplane continued the rollout and came to rest upright in a muddy field. Approximately one fourth cup of blue liquid resembling avgas was drained from the right wing fuel tank, and no fuel was observed in the left wing fuel tank. Approximately one teaspoon of blue liquid was drained from the carburetor.
Probable cause
The loss of engine power as result of fuel exhaustion due to the pilot's improper in-flight planning. A contributing factor was the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW05CA068
- Event ID
- 20050226X00235
- Case number
- DFW05CA068
- 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: 4043bf9880b183249cb828f926bdd309c53053f003e5d107facf8f4dbf1659a9; retrieved 2026-09-22T06:16:46.562Z.