Houston Charter Service Piper PA-32R accident
Piper PA-32R · Accident: fire en route
From William P. Hobby Airport (HOU) to Dallas Love Field (DAL)
Event
- NTSB case
- FTW87FA197
- 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
- Charter & commuter
- 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-32R
- 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
- N8159S
- Operator
- Houston Charter Service
- Onboard fatalities
- Unknown
- Route
- From William P. Hobby Airport (HOU), Houston, TXTo Dallas Love Field (DAL), Dallas, 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 · 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
- Fire
- 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
- Company/operator management › Maintenance, inadequate
- Exhaust system › Leak
- Exhaust system, clamp › Loose
- Ignition system, ignition harness › Burned
- Pilot in command › Precautionary landing, discontinued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT NOTICED SMOKE IN THE COCKPIT & STARTED TO MAKE A PRECAUTIONARY LNDG AT MEXIA, TX, WHICH WAS NEARBY. HOWEVER, DRG THE DSCNT TO LND, THE SMOKE DISSIPATED, SO HE ELECTED TO CONT TO THE DESTN. DRG THE CLIMB BACK TO ALT, SMOKE REAPPEARED & WAS FOLLOWED BY LOSS OF ENG POWER. THE PLT THEN TRIED TO MAKE A FORCED LNDG AT MEXIA; HOWEVER, THERE WAS INSUFFICIENT ALT TO REACH THE ARPT. WHILE LNDG ABOUT 1 MI FROM THE ARPT, THE ACFT ROLLED THRU A BARBED WIRE FENCE & WAS DAMAGED. AN EXAM OF THE ACFT REVEALED A RETAINING NUT WAS MISSING FROM A CLAMP NEAR 2 MATING SURFACES OF THE EXHAUSTSYS NEAR THE #6 CYLINDER. SUBSEQUENTLY, GASES FROM THE EXHAUST SYS BURNED THRU A VACUUM HOSE & EXTENSIVELY BURNED A NUMBER OF WIRES IN THE IGNITION SYS. THE ACFT HAD BEEN FLOWN 176 HRS SINCE THE LAST ENG & AIRFRAME INSPN.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW87FA197
- Event ID
- 20001213X31802
- Case number
- FTW87FA197
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: 6e90ce4db4a7e948753560f03312b8112ef9e662eba32c8e692e6f83a8398c38; retrieved 2026-09-18T19:38:39.870Z.
- The NTSB's operator name is blank for N8159S; the operator shown is the name the NTSB records it doing business as.