# NTSB ATL06CA031: Piper PA-23-160, N4370P, Phenix City, AL, January 2, 2006 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Data collection · Final report - Date: January 1, 2006, 18:36 local (Jan 2, 2006, 00:36 UTC) - Place: Phenix City, AL - Coordinates: 32.421112, -85.248054 - Nearby events: https://openairdocs.org/map.md?lat=32.4211&lon=-85.2481&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Highest injury: Serious injuries - Injuries: 1 serious, 1 minor, 1 uninjured - Status: Completed, report March 28, 2006 - Report: Approved by Office Director - Parties: Birmingham FSDO-09 - NTSB case key (mKey): 63041 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ATL06CA031 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/63041/pdf - Page: https://openairdocs.org/ntsb/ATL06CA031 ## 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. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight encounter with weather, cruise - normal - weather condition - low ceiling - in-flight planning/decision - inadequate, pilot in command (cause) - flight into adverse weather - continued, pilot in command (cause) - Loss of engine power(total) - nonmechanical, approach - fluid,fuel - exhaustion (cause) - Forced landing, emergency descent/landing - In flight collision with object, emergency landing - object - tree(s) ## Analysis 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. ## Factual 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 approach's 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 approach's. ## Aircraft - Registration: [N4370P](https://openairdocs.org/deregistered/N4370P-2007-12-18), registration cancelled 2007-12-18, S/N 23-1871, built 1960 (OpenAirDocs) - Reported make and model: Piper PA-23-160 - Registry model: [Piper PA-23-160](https://openairdocs.org/model/piper-pa-23-160) (registry code 7102304) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 23-1871 - Airframe hours: 4071 - Engines: Lycoming O-320 160 horsepower reciprocating; Lycoming O-320 160 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Roy T. Dawes - Airworthiness certificate: Standard, Normal - Last inspection: Annual, March 1, 2005 - Departed: BKV, Brooksville, FL - Destination: WDR, Winder Barrow, GA - Airport: runway 5, 6,998 × 150 ft, concrete ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 48; injuries: serious; private; airplane ratings: multi-engine land; medical: class 3, with waivers/limitations; last flight review February 1, 2004; seat: left; flight hours: 600 total, 600 in this make and model, 600 as pilot in command, 30 in the last 90 days, 12 in the last 30 days, 5 in the last 24 hours ## Weather - Conditions: Instrument (IMC), Dusk - Wind: 70° at 6 knots - Visibility: 1.5 statute miles - Lowest ceiling: 400 ft overcast - Temperature: 61 °F, dew point 57 °F - Altimeter: 29.97 inHg - Observed at: CSG, 5 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20060101000839A](https://openairdocs.org/incident/20060101000839A), Jan 1, 2006: Piper PA23160, Pheonix City, AL, Substantial damage. (-23) VFR flight with flight following. While deviating around the weather to remain in VFR condition pilot stated he hit a wall of clouds and called atlanta… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.