# NTSB ERA25FA008: Cessna 336, N336LV, Savannah, GA, October 14, 2024 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Field · Preliminary report - Date: October 13, 2024, 22:30 local (Oct 14, 2024, 02:30 UTC) - Place: Savannah, GA · Residential Area - Coordinates: 32, -81 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.0000&lon=-81.0000&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) - Highest injury: Fatal - Injuries: 1 fatal, 1 minor - Status: Investigation ongoing - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: Hartzell Propeller, Continental, Textron, Textron Aviation, FAA/FSDO - NTSB case key (mKey): 195304 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA25FA008 - NTSB preliminary report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/195304/pdf - Page: https://openairdocs.org/ntsb/ERA25FA008 ## Preliminary report On October 13, 2024, about 2230 eastern daylight time, a Cessna 336, N336LV, was destroyed when it was involved in an accident near Savannah, Georgia. The commercial pilot was fatally injured, and a pilot-rated passenger sustained minor injuries. The flight was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Radar data indicated that the flight departed Miami Executive Airport (TMB), Miami, Florida enroute to Savannah International Airport (SAV), Savannah, Georgia. According to air traffic control (ATC) communication information provided by the Federal Aviation Administration, the pilot contacted ATC while flying at an altitude of 7,000 feet, and stated that he was inbound to SAV and had obtained the current weather conditions there. The pilot was cleared to descend to 2,000 feet for an approach to runway 28 at SAV. Shortly thereafter, the pilot requested a direct approach due to fuel concerns, which ATC approved. The pilot subsequently reported a loss of engine power, declared an emergency, and later advised ATC that both engines had lost power. ATC provided the pilot with radar vectors to Hunter Army Airfield (SVN), Savannah, Georgia, which was located about 3 miles from the airplane's position at that time. The pilot acknowledged these instructions, reported seeing the airport’s runway lights, but expressed concern about reaching the runway. The final transmission from the pilot indicated that he would not be able to reach the runway. The airplane subsequently impacted terrain in a residential area about 2 nautical miles northeast of SVN. All major components of the airplane were located at the accident site. The cockpit and instrument panel were destroyed by impact forces. The fuselage exhibited extensive impact and crush damage. The left wing had separated outboard of the inboard fuel tank, which was intact but empty. The outboard section of the left wing, found along the wreckage path, revealed a breached fuel tank with trace amounts of fuel observed. The right wing separated outboard of the inboard fuel tank, which remained intact and contained trace amounts of fuel. The outboard section of the right wing was partially attached via control cables, and a trace amount of fuel was observed within the tank. Both engines remained attached to the fuselage and exhibited impact damage. The vertical stabilizer, rudder, and horizontal stabilizer were partially attached and showed signs of impact damage. The wreckage was recovered and retained for further examination. ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) (defining event); cases with it: [Cessna 336, 1 case](https://openairdocs.org/ntsb-events/192/sequence.md?model=2075602), [All aircraft, 804 cases](https://openairdocs.org/ntsb-events/192/sequence.md) - [Emergency descent: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341); cases with it: [Cessna 336, 1 case](https://openairdocs.org/ntsb-events/341/sequence.md?model=2075602), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 336, 3 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2075602), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Aircraft - Registration: [N336LV](https://openairdocs.org/aircraft/N336LV), registered now, S/N 336-0176, built 1964 (OpenAirDocs) - Reported make and model: CESSNA 336 - Registry model: [Cessna 336](https://openairdocs.org/model/cessna-336) (registry code 2075602) (OpenAirDocs) - Registry engine: [Continental IO-360 series](https://openairdocs.org/engine/continental-io-360-series) (registry code 17025, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 336-0176 - Year built: 1964 - Airframe hours: 2928 - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, March 1, 2024 - Departed: TMB, Miami, FL - Destination: SAV, Savannah, GA - Flight plan: IFR - Airport: SVN, Hunter Aaf - Equipment: ADS-B ## Weather - Conditions: Visual (VMC), Night/dark - Wind: 200° at 8 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 68 °F, dew point 55 °F - Altimeter: 30.05 inHg - Observed at: SAV, 13 nm away - METAR: METAR KSAV 140153Z 20008KT 10SM CLR 20/13 A3005 RMK AO2 SLP173 T02000128 ## 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 20241013022369A](https://openairdocs.org/incident/20241013022369A), Oct 13, 2024: Cessna 336, Savannah, GA, Destroyed, 1 fatal. N336LV, a Cessna 336 skymaster, s/n 336-0176, departed miami executive airport (tmb) at approximately 1816 hours with a scheduled landing at Savannah… 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.