BFO88FA008 · Piper PA-32-260B
Piper PA-32-260B · Accident: airframe, component or system failure en route
From Lima, OH to Smith Reynolds Airport (INT)
Event
- NTSB case
- BFO88FA008
- 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
- 3 · 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
- Instrument Meteorological Cond
Piper PA-32-260B
- 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
- N4832S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lima, OHTo Smith Reynolds Airport (INT), Winston-Salem, NC
- 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
- Airframe, component or system failure
- 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
- Pilot in command › Emergency procedure, not followed
- Pilot in command › Flight/navigation instrument(s), misread
- Pilot in command › Spatial disorientation
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
THE ACFT WAS ON A NIGHT IFR FLIGHT AT 7000 FT MSL IN IMC WHEN THE PLT REPORTED THE DIRECTIONAL GYRO WAS INOPERATIVE. THE ACFT WAS OUTBOUND FROM THE PULASKI VOR ON V45 HEADED SOUTHEAST. THE PLT FURTHER REPORTED THE TURN&BANK AND THE MAG COMPASS WERE OPERATIVE. SHORTLY AFTERWARDS THE PLT WAS UNABLE TO MAINTAIN THE CORRECT COURSE. THE ACFT EVENTUALLY REVERSED COURSE. WHILE ATC WAS TRYING TO HELP THE PLT RETURN TO THE CORRECT COURSE THE ACFT DESCENDED AND COLLIDED WITH THE GROUND. WITNESSES NEAR THE ACCIDENT SITE REPORTED POOR VISIBILITY, LOW CLOUDS, AND FOG. THE AIRCRAFT'S IMC CAPABILITY COULD NOT BE ACCURATELY DETERMINED DUE TO THE EXTENSIVE FIRE AND IMPACT DAMAGE. EXAMINATION OF THE ENGINE DRIVEN VACUUM PUMP DID NOT REVEAL CONCLUSIVE EVIDENCE OF FAILURE. THE ACFT WAS EQUIPPED WITH A STANDBY VACUUM SYSTEM, HOWEVER, OPERATION OF THE SYSTEM COULD NOT BE CONFIRMED. THE PLT HAD FLOWN THE FIRST LEG (4.0 HRS.) TO DROP OFF PAX AND WAS RETURNING TO HIS HOME BASE. THE ACFT HAD FLOWN ABOUT 3 HRS. ON THIS LEG.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record BFO88FA008
- Event ID
- 20001213X32484
- Case number
- BFO88FA008
- 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. 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: f41f99a5d7716e865d2829f5c4ee67e51b97168b20eda14fa6494551658124c0; retrieved 2026-09-21T03:53:37.339Z.