BFO90LA004 · Piper PA-23-150
Piper PA-23-150 · Accident: airframe, component or system failure en route
From 19J · Homerville, GA to Charlottesville Albemarle Airport (CHO)
Event
- NTSB case
- BFO90LA004
- 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
- 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-150
- 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
- N2224P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 19J · Homerville, GATo Charlottesville Albemarle Airport (CHO), Charlottesville, VA
- 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
- Substantial
Cause areas
- Propeller system/accessories › Undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE IN CRUISE FLT AT 6,500 FT, AT A POWER SETTING OF 2500 RPM WITH 21 INCHES MP, THE PLT STATED HE WAS UNABLE TO SYNCHRONIZE THE LEFT PROP. HE STATED THE PROP THEN DECREASED TO 1500 RPM, SURGED TO 3000, THEN DROPPED BACK TO 1500. HE ATTEMPTED TO FEATHER THE PROP BUT WAS UNABLE TO DO SO. UNABLE TO MAINTAIN ALT WITH POWER FROM THE RIGHT ENG, THE PLT MADE A FORCED LANDING ON AN INTERSTATE. DURING THE LANDING ROLL, THE LEFT WING CONTACTED AN EMBANKMENT AND THE ACFT VEERED OFF THE SIDE OF THE INTERSTATE. A FIRE STARTED IN THE RIGHT ENGINE AND THE RIGHT WING WAS DESTROYED. POST ACCIDENT INSPECTION OF THE LEFT PROPELLER FAILED TO REVEAL ANY REASON WHY THE FLUCTUATION IN RPM HAD OCCURRED. NOR DID IT REVEAL WHY THE PROP WOULD NOT FEATHER. WATER WAS FOUND THROUGHOUT THE LEFT ENGINE FUEL SYSTEM. THE PROPS HAD BEEN OVERHAULED PRIOR TO THIS FLT. THE LEFT PROP GOVERNOR WAS BENCH TESTED AND ALTHOUGH CAPABLE OF OPERATION WAS FOUND TO BE OPERATING SLIGHTLY OUT IT'S SPECIFIED OPERATING RANGE.
Probable cause
THE LOSS OF PROPELLER CONTROL WHICH RESULTED IN ENGINE SHUTDOWN AND SUBSEQUENT FORCED LANDING ON UNSUITABLE TERRAIN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO90LA004
- Event ID
- 20001213X29544
- Case number
- BFO90LA004
- 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: f60ff0ad33b0af46ccccf55bda284327a71a0891abe6a35980860d0c2ca99b7f; retrieved 2026-09-21T23:59:52.969Z.