FTW94LA026 · Rockwell 114
Rockwell 114 · Accident: total loss of engine power (non-mechanical) en route
From Ennis Municipal Airport (F41) to AAP · Houston, TX
Event
- NTSB case
- FTW94LA026
- 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
Rockwell 114
- Aircraft type
- Rockwell 114
- 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
- N1237W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ennis Municipal Airport (F41), Ennis, TXTo AAP · Houston, 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; Wire, transmission
- 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
- Other person › Maintenance, not performed
- Pilot in command › Operation with known deficiencies in equipment, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE EN ROUTE ON A CROSS COUNTRY FLIGHT, THE AIRPLANE EXPERIENCED A FUEL EXHAUSTION INDUCED POWER LOSS. THE PILOT BECAME AWARE OF THE CRITICAL FUEL STATE ABOUT 3 MINUTES PRIOR TO THE FAILURE. THE AIRPLANE COLLIDED WITH POWER LINES, TREES, AND ROUGH TERRAIN DURING THE ENSUING NIGHT FORCED LANDING ON A ROAD. THE PILOT'S PREFLIGHT HAD INDICATED HE HAD ADEQUATE FUEL TO COMPLETE THE FLIGHT AND HE SHOULD HAVE HAD 2 HOURS REMAINING AT THE TIME OF THE ACCIDENT. IT WAS DETERMINED THAT THE AIRPLANE HAD A HISTORY OF FUEL LEAKS FROM THE TANKS AND THE STRAINER. THE AIRPLANE OWNER HAD BRIEFED THE PILOT ON THE LEAKS, BUT THE PILOT STATED THAT ALL HE HAD EXPERIENCED WAS UNEVEN TANK BURN WHEN THE FUEL SELECTOR WAS PLACED ON THE BOTH POSITION.
Probable cause
WAS THE OWNER'S FAILURE TO PERFORM CORRECTIVE MAINTENANCE ON THE AIRPLANE'S FUEL SYSTEM AND THE PILOT'S DECISION TO OPERATE IT WITH KNOWN MAINTENANCE DEFICIENCIES. A FACTOR WAS THE LACK OF SUITABLE TERRAIN ONTO WHICH A FORCED LANDING COULD BE EXECUTED.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW94LA026
- Event ID
- 20001211X13735
- Case number
- FTW94LA026
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1993-11-08.
- API snapshot SHA-256: dd6c531a467583cb60e1855cfbfdaf92430a8ceae9d1463f77cf9ddfa85a8cd3; retrieved 2026-09-21T22:45:57.194Z.