Plane Crash List

Cessna 310Q N7664Q

23 August 2025 · Milledgeville, Georgia, United States · Fatal

Summary

On 23 August 2025 at about 22:25 local time, a Cessna 310Q registered N7664Q was involved in an accident near Milledgeville, Georgia, United States. One person was on board and one died. The aircraft was destroyed. No probable cause has been published yet; this accident is still under investigation.

The record

Date
at 22:25
Classification
Accident
Location
Milledgeville, Georgia, United States
Nearest airport
Baldwin County Rgnl (MLJ)
Coordinates
33.1454, -83.3675
Aircraft
Cessna 310Q
Registration
N7664Q
Category
Airplane
Year built
1971
Engines
2
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Personal
Phase of flight
Not recorded
Route
Fairfield → Unknown
Aircraft damage
Destroyed
Weather
VMC
Light
Day
NTSB number
ERA25FA310

People

1 person died.

On board Died Serious Minor Uninjured
1 1 0 0 0

Probable cause

The NTSB has not published a probable cause for this record. The investigation is still open; a final report usually follows one to two years after the accident.

Nothing about the cause is stated here that is not in the source record.

Read the full NTSB narrative

On August 23, 2025, about 1825 eastern daylight time, a Cessna 310Q, N7664Q was destroyed when it was involved in an accident near Milledgeville, Georgia. The commercial pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations personal flight. According to a witness, the pilot, who was based in Hilton Head, South Carolina, had flown to Fairfield County Airport (FDW), Winnsboro, South Carolina to obtain an instrument flight rules (equipment) recertification. Once completed, the pilot departed runway 4 at FDW about 1723 on an instrument flight rules (IFR) flight plan to Baldwin County Regional Airport (MLJ), Milledgeville, Georgia, about 130 nautical miles to the south-southwest. Preliminary air traffic control communications and ADS-B data provided by the Federal Aviation Administration showed that after departure the pilot made a right turn and flew east for about 6 miles then made a left 360° turn to the southwest while climbing to an en route cruising altitude of about 10,000 ft mean sea level (msl). Altitudes, ground speeds and headings were consistent throughout the en route portion of the flight. As the airplane approached the initial approach fix (IBUDY) for the RNAV GPS 10 arrival to MLJ, the pilot was in communications with the Atlanta radar approach controller. The pilot was issued a descent to 4,000 ft, provided the MLJ altimeter, and asked to verify that he was in receipt of the weather. The pilot responded with confirmation and was subsequently cleared for the RNAV Runway 10 Approach; the controller instructed the pilot to pass over IBUDY at or above 3,000 ft, which was acknowledged. There were no further transmissions from the pilot. About 10 seconds after the last communications and 6 miles east IBUDY, the airplane entered a left turn towards the south and descended. The controller advised the pilot “Low altitude alert, six four Quebec, check your altitude immediately.” The airplane continued on a track of about 120° and descended until flight track data was lost at 1821, about 6 nm west of the approach end of runway 10 at MLJ. During the descent, the airplane’s ground speed increased from 140 kts to 179 kts. Reported weather conditions around the time of the accident showed overcast conditions around 2,200 to 2,500 ft with clouds extending to 10,000 ft. There was no precipitation activity in the area. There was a 10 to 15 knot tailwind during the last portion of the flight and the freezing level was above 15,000 ft with no reported PIREPs in the region. The airplane initially impacted the tops of 78-ft pine trees, then level terrain before coming to rest at an elevation of 462 ft. The wreckage path was oriented on a magnetic heading of 151° and the debris field was 135 ft wide and 660 ft long. The airplane wreckage was highly fragmented. There was no evidence of a post impact fire observed at the accident site and no evidence of an inflight fire was observed on the airplane wreckage. Tree and ground impact evidence was consistent with a slight airplane nose down wings level attitude. Subsequent examination of the wreckage revealed that all major components of the airplane were accounted for. Elevator, rudder, and aileron flight control continuity were confirmed from the control surfaces through the cockpit controls; the control cables were traced through tensile overload breaks in the cables that exhibited a “broomstraw” appearance. The elevator trim position was measured through the actuator and corresponded to a trim setting about 5° nose up. The flap handle was in the up (retracted) position. The fuel system components that were undamaged contained fluid with the smell and consistency of aviation fuel that was absent of contamination. The landing gear selector was in the up (retracted) position and the landing gear actuators indicated that all 3-landing gear were retracted at the time of impact. The instrument panel analog gauges and electronic primary flight instruments were all severely damaged by impact forces and their readings could not be observed; there was no non-volatile memory available for download. Both engines separated from their respective wing mounts during the accident sequence. They were discovered on the last 1/3 of the wreckage path and were impact damaged. The spark plugs remained in their respective locations and the magnetos were impact-separated and located along the wreckage path. Both propeller assemblies separated from their respective engines and were located within the wreckage path. Both 3-bladed metal propellers showed chordwise scraping on several of the blades with leading edge gouging and bends. One blade on each of the hubs, was separated and discovered within the wreckage field. The remaining propeller blades remained attached to their respective hubs. The wreckage was retained for further examination.

Quoted verbatim from the NTSB record.

Other Cessna 310 accidents

Date Aircraft Location Operator Outcome Died
29 May 2025 Cessna 310
VH-NXA
Lake Evella Aerodrome, Australia - No injuries -
1 Apr 2025 Cessna 310Q
N8242Q
Midvale, Ohio, United States Birds Eye View Inc Fatal 1
11 Apr 2025 Cessna 310R
N8930N
Boca Raton, Florida, United States - Fatal 3
24 Jun 2025 Cessna 310
N5045Q
Fayetteville, Tennessee, United States - No injuries -
30 Dec 2024 Cessna 310
N6979T
Peebles, Ohio, United States - Fatal 1
20 Dec 2024 Cessna 310
PT-JCZ
Manicore, Brazil Patrimonial Celta LTDA Fatal 2

All 1,745 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
20 Mar 2025 Cirrus SR22
N969SS
LaFayette, Georgia, United States - Fatal 2
18 Aug 2025 Thrush S2R-T660
N7001B
Albany, Georgia, United States Thrush Aircraft LLC Minor injuries -
10 Jan 2025 Boeing 757
N589NW
Atlanta, Georgia, United States Delta Air Lines Inc Serious injuries -
21 Mar 2025 Bell 206
N5QV
Chamblee, Georgia, United States Helicopters Inc Serious injuries -
11 Oct 2025 Cessna 172
N4390L
Sandersville, Georgia, United States Aero Science International LLC Minor injuries -
21 Jul 2025 Embraer-Empresa Brasileira de ERJ 170-200 LR
N229JQ
Jacksonville, Georgia, United States Delta Air Lines Inc Serious injuries -

All 170,864 records in United States