FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW04LA059 · Piper PA-23-160

9 Jan 2004 · Fort Worth, TX, United States

Piper PA-23-160 · Accident: partial loss of engine power (mechanical failure) during initial climb

From Hicks Air Field (T67) to an unrecorded destination

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
FTW04LA059
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

Piper PA-23-160 Possible conflict

Aircraft type
Piper PA-23
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
N3289P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hicks Air Field (T67), Fort Worth, TXTo not recorded
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
Initial climb
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
Partial 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
Substantial

Cause areas

  • Owner/pilot mechanic › Maintenance, installation, improper
  • Pilot in command › Directional control, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Prior to departure, the airplane's fuel tanks were topped-off with 72 gallons of 100LL aviation fuel. On the take-off roll, when the airplane's airspeed increased to 85 miles per hour (mph) (red-line on the airspeed indicator), the pilot rotated, and the airplane began to climb. When the airspeed increased to 95 mph (blue-line on the airspeed indicator), the airplane suddenly yawed to the right and the airspeed decreased. The pilot said it, "felt like my right engine stopped working." In 3 to 4 seconds, the airplane was over a row of hangars. The pilot lowered the nose of the airplane in an attempt to gain airspeed. But, there was insufficient altitude to clear the hangars and subsequently the airplane collided with one of them, then impacted two parked aircraft. Examination of the right engine revealed that the mixture control cable was disengaged from the carburetor mixture control arm and the cotter pin used to secure the tension nut on the mixture cable was not installed. The mixture control swivel, stud, and a segment of the mixture control cable were examined at the NTSB's Material's Laboratory, Washington DC. According to a Safety Board metallurgist, examination of some of the components indicated wear damage. But, the mixture control cable did not exhibit any longitudinal gouge marks or wear damage that would have been consistent with it being separated during the accident sequence. In addition, the engine was test-run and it operated at various power settings up to 1,500 RPM. The engine ran continuously and without hesitation for approximately 10 minutes. The propeller was actuated and operated normally. Both magnetos were checked and no anomalies were noted. The engine driven fuel pump produced suction and exhaust, and oil was noted draining from the forward crankshaft area. The pilot reported a total of 377 flight hours, of which, 41 hours were in twin-engine aircraft. He also reported a total of 10 hours in the same make and model airplane. A weight and balance computation was made using the airplane's original factory weight and balance. Based on the calculations, the airplane was within weight and balance limits.

Probable cause

The pilot's failure to maintain control and the partial loss of engine power as a result of an improperly installed mixture control linkage.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW04LA059
Event ID
20040113X00054
Case number
FTW04LA059
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: 0a59863b3726d15963ef91f6df0204a1f3e449cefc92c36ee8f370f16aea5bb4; retrieved 2026-09-22T08:02:14.756Z.