FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW04FA235 · Piper PA-32R-300

9 Sept 2004 · Rachel, TX, United States

Piper PA-32R-300 · Accident: loss of control in flight en route

From Stinson Municipal Airport (SSF) to McAllen Miller International Airport (MFE)

Report a problem

Event

NTSB case
FTW04FA235
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
1 · 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
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Piper PA-32R-300

Aircraft type
Piper PA-32
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
N6209J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Stinson Municipal Airport (SSF), San Antonio, TXTo McAllen Miller International Airport (MFE), Mc Allen, 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 135: Air Taxi & Commuter
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 · descent
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
Loss of control in flight
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

  • Flight/nav instruments, attitude gyro › Not operating
  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Spatial disorientation
  • Vacuum system › Failure

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

NTSB narrative

A single-engine airplane, operating in dark night instrument meteorological conditions as a Part 135 mail cargo flight, impacted terrain after an in-flight break up. Several minutes before the impact, the pilot reported to air traffic control that he had lost his vacuum pump. An on-site examination of the wreckage revealed that the vacuum pump the drive was separated from the engine and the flex coupling displayed a torsion-type separation with coupling wear consistent with engine operation after the separation. Disassembly of the model 211CC vacuum pump revealed the following. A number was assigned to each of the rotor segments and the corresponding vanes were marked and removed from their respective slots. Five of the six vanes were intact, and vane #4 was broken. Four pieces were reassembled to recreate approximately 80 percent of vane #4. Three of the four pieces were found in the mounting flange, and one piece was found in the back flange. The rotor segments were marked such that vane slot #4 is between segment 4 and segment 5. Upon examination of the walls of vane slot 4, a groove approximately .450 inches by .120 inches by .020 inches deep was found on both sides of the vane slot. These grooves corresponded in dimension and position to the portion of the vane that was missing. Three carbon pieces were found, which exhibited extensive wear, which, in two cases, were smooth and round like a "BB." The rear fracture surface of vane #4 exhibited a smooth, polished, spherical wear mark corresponding with the carbon pieces found. The pump housing had severe wear such that there were washboard marks around its entire circumference. At the bottom of the bore, a burr was found on the edge of one of the back flange discharge ports. Corresponding rotational marks were found on the pump's rotor. According to Parker Hannifin, the rule of thumb for vane wear versus service life is: .025-inches of wear for every 100 hours of operation. Using Parker's original new vane length of .845 inches, the estimated time of operation of the vanes of the accident pump was approximately 1,380 hours. According to Parker the vacuum pump had been overhauled. Parker's service letters require replacement of model 211CC vacuum pumps after 500 hours of operation or 6 years from the date of manufacture, which ever occurs first. Examination of the directional gyro revealed that the housing was intact and the gyro was free to move. No rotational marks were found on the gyro or inside the housing. The turn coordinator gyro was examined and no rotational scoring was found when removed from the housing. A small portion of the housing was fractured and missing. The attitude indicator gyro was free to move within its housing and the housing was intact. No rotational scoring was noted when the gyro was removed from the housing. The filament of the vacuum enunciator bulb # PL33[0] exhibited stretching.

Probable cause

The total failure of the vacuum pump that resulted in an inoperative attitude gyro and spatial disorientation and a subsequent loss of aircraft control by the pilot. Factors were; the prevailing instrument meteorological conditions, and the dark night light condition.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW04FA235
Event ID
20040928X01501
Case number
FTW04FA235
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: 941ae4b803f41c64722585921931abb264d19f94f7ebd2068ae4b8b24f355ab8; retrieved 2026-09-18T13:00:09.080Z.