ATL06CA031 · Piper PA-23-160
Piper PA-23-160 · Accident: in flight encounter with weather en route
From Brooksville–Tampa Bay Regional Airport (BKV) to Barrow County Airport (WDR)
Event
- NTSB case
- ATL06CA031
- 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
- 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
- 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-23-160
- 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
- N4370P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Brooksville–Tampa Bay Regional Airport (BKV), Brooksville, FLTo Barrow County Airport (WDR), Winder Barrow, GA
- 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
- In flight encounter with weather
- 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
- Fuel exhaustion; Tree(s)
- 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
- Fluid, fuel › Exhaustion
- Pilot in command › Flight into adverse weather, continued
- Pilot in command › In-flight planning/decision, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot was on a visual flight rules cross country flight when he began encountering instrument conditions. The pilot continued into the instrument conditions for about 30 minutes before asking Atlanta Approach Control for directions to the nearest airport for landing. The controller directed the pilot to two different nearby airports but both were below minimums. The pilot informed the controller that he was low on fuel and needed to land as soon as possible. The controller directed the pilot to the Columbus Metropolitan Airport, Columbus, Georgia. The pilot told the controllers that he would attempt an Instrument approach. The pilot attempted four unsuccessful approaches with the controllers talking him through each approach. On the fifth approach, at five miles from the runway the pilot stated that both engine's quit due to fuel exhaustion. The pilot called "mayday" and during the forced landing the airplane collided with trees and the ground separating the right wing, half of the left wing, and coming to rest inverted. The pilot did not report any mechanical deficiencies with the airplane during the attempted approaches.
Probable cause
The pilot's inadequate decision to continue VFR flight into IMC conditions, which resulted in a loss of engine power due to fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL06CA031
- Event ID
- 20060113X00068
- Case number
- ATL06CA031
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-01-02.
- API snapshot SHA-256: 5d37d88c89d81d72bc5071714a2f58054cc10773e79c63bea83b4e60b37d73e9; retrieved 2026-09-21T09:00:52.535Z.