Cessna 310Q accident near Milledgeville, Georgia, August 23, 2025
On August 23, 2025 at about 10:25 pm local time, a 1971 Cessna 310Q, registered N7664Q, was destroyed in an accident during approach near Milledgeville, Georgia (Baldwin County Rgnl airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 23, 2025 · about 10:25 pm local time · cases in 2025
- Place
- Milledgeville, Georgia · Baldwin County Rgnl · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 310Q, built 1971 · all 310Qs on the register
- Registration
- N7664Q · registry record · serial 310Q0443
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Unknown or undetermined during approach defining event
The aircraft
- Maximum gross weight: 5,300 lb
- Seats: 6
- Landing gear: retractable
The flight
- Departed from: FDW Fairfield SC at 9:20 pm
- Flight plan: IFR
Weather at the time
- Light: daylight
- Wind: from 070° at 12 knots
- Visibility: 10 statute miles
- Sky: overcast at 2,500 ft
- Temperature: 32°F (0°C), dew point 32°F (0°C)
- Altimeter: 2994.00 inHg
- Observation at 6:15 am from MLJ, 6 miles away
Weather report (METAR): MLJ 232215Z AUTO 07012KT 10SM OVC025 25/22 A2994 RMK AO2
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Connections how this case links to the rest of the register
- N7664Q on the register today · the tail number may have moved to another aircraft since
- Cessna 310 1,410 registered today · the model family and its accident history
- Cessna 72,677 aircraft on the register
- Baldwin County Regional · nearest airport
- Fairfield County · departed from
- Accidents and incidents in Georgia 2,138 since 1982 · 361 in the last ten years
- Georgia 8,801 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA25FA310.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
