BFO93FA082 · Piper PA-32-300
Piper PA-32-300 · Accident: in flight collision with object en route
From an unrecorded airport to Logan County Airport (6L4)
Event
- NTSB case
- BFO93FA082
- 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
- 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
Piper PA-32-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
- N45087
- Operator
- William M. Charles · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Logan County Airport (6L4), LOGAN COUNTY, WV
- 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 · climb to 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
- In flight collision with object
- 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
- Wire, static
- 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 › Proper altitude, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
SHORTLY AFTER TAKEOFF AT ABOUT 2345 EASTERN DAYLIGHT TIME, THE AIRPLANE STRUCK A STATIC WIRE AND COLLIDED WITH TERRAIN AT AN ELEVATION OF 1,900 FEET MEAN SEA LEVEL. THE POWER COMPANY REPORTED THAT THE POSITION OF THE STATIC WIRE IS ABOUT 280 FEET ABOVE THE TERRAIN AT AN ALTITUDE OF 1,690 FEET MEAN SEA LEVEL. THE ACCIDENT SITE WAS LOCATED ABOUT 1.2 MILES FROM THE AIRPORT. THE DEPARTED AIRPORT'S ELEVATION WAS 730 FEET MEAN SEA LEVEL. THE AIRPLANE WAS DESTROYED BY POST IMPACT FIRE. NO AIRFRAME OR ENGINE ANOMALIES WERE NOTED. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME OF ACCIDENT AND PATCHES OF GROUND FOG WERE REPORTED AROUND THE AREA. THE COMMERCIAL PILOT'S LOG BOOK WAS NOT RECOVERED.
Probable cause
FAILURE OF THE PILOT TO ATTAIN SUFFICIENT ALTITUDE TO REMAIN CLEAR OF RISING TERRAIN AND OBJECTS. FACTORS RELATED TO THE ACCIDENT WERE DARKNESS AND RISING TERRAIN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO93FA082
- Event ID
- 20001211X12293
- Case number
- BFO93FA082
- 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-05-12.
- API snapshot SHA-256: 3460f0d109019b4bb160724d57b1c8f54956f2c19befeb0ea535a63349ddd05f; retrieved 2026-09-21T00:33:43.264Z.