The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB ERA24LA012 · Final report

Beech 300 accident near Atlanta, Georgia, October 18, 2023

On October 18, 2023 at about 7:11 pm local time, a 1986 Beech 300, registered N93GA, was substantially damaged in an accident during landing (landing roll) near Atlanta, Georgia (Dekalb-Peachtree Airport). It was a business flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The pilot’s failure to maintain a proper approach speed, which resulted in a runway overrun. Contributing to the runway overrun were the pilot’s application of full reverse at an airspeed higher than that allowed by the system, which added power and forward thrust, and the application of braking that flat-spotted the main landing gear tires.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
October 18, 2023 · about 7:11 pm local time
Place
Atlanta, Georgia · Dekalb-Peachtree Airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Beech 300 UNDESIGNAT, built 1986 · all 300s on the register
Registration
N93GA · no longer on the register · serial FA-93
Damage
Substantial damage
Flight
Business flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot performed a visual approach to the runway in calm wind conditions with the flaps extended halfway (approach flaps). Flight track information indicated that the airplane was fast crossing the runway displaced threshold, and touched down with about 4,000 ft of runway remaining at a speed about 135 knots (kts), which was 19 kts above the highest published approach speed for the airplane’s gross weight at the time of landing. The pilot reported that, after touchdown, he moved the power levers into the ground fine position to help slow the airplane, but he did not feel the “normal deceleration.” He applied the brakes and then “stood on the brakes,” adding that he did not feel the tires sliding, then applied maximum reverse thrust in an attempt to bring the airplane to a stop on the runway. The airplane rolled past the departure end of the runway, onto a displaced threshold, and then into the engineered material arresting system past the departure end of the runway. During the runway excursion, the nose landing gear wheel assembly separated and the right engine was displaced from its normal position. Postaccident examination revealed that one tire on each main landing gear exhibited flat-spotting through the tread, consistent with a sliding tire. Although the pilot commanded the propeller blade angle to move less than the flight idle low pitch stop setting during the landing roll, the propeller blades could not move to this position until the airplane slowed to about 100 kts or less, which did not occur until the airplane was more than 3,400 ft down the 5,000-ft-long runway. At speeds above 100 kts, the propeller was governed by the constant speed unit, which will not allow the pilot to command ground fine or reverse thrust settings. Thus, there were no systems failures or malfunctions that prevented movement of the propeller blades to ground fine or reverse. The application of full reverse thrust when the airplane was likely greater than 100 kts indicated airspeed likely further increased the required stopping distance by adding engine power and thrust in the forward direction. The added forward thrust, combined with the flat-spotting of several tires during the landing roll, likely cumulatively increased the required landing roll distance, resulting in insufficient runway remaining to avoid a runway overrun.

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

  1. Landing area overshoot during landing
  2. Runway excursion during landing (landing roll) defining event

The NTSB's findings

  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Incorrect use/operation
  • Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
  • Aircraft › Aircraft power plant › Engine (turbine/turboprop) › (general) › Incorrect use/operation
  • Aircraft › Aircraft systems › Landing gear system › Tire casing › Damaged/degraded

Pilot

  • Certificate: airline transport pilot, flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 6,319 hours in all; 2,610 in this make and model; 62 in the last 90 days; 19 in the last 30 days; 4,932 as pilot in command; 1,350 on instruments
  • Last flight review: September 23, 2022
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 10,459 hours
  • Last inspection: continuous airworthiness programme, December 23, 2022; 139 hours since
  • Maximum gross weight: 14,000 lb
  • Seats: 9
  • Landing gear: retractable
  • Engine 1: Pratt & Whitney Canada PT6A-60 (turboprop); 10,112 hours total
  • Engine 2: Pratt & Whitney Canada PT6A-60 (turboprop); 10,208 hours total
  • Operator: Csw Aviation LLC

The flight

  • Departed from: SAV Savannah GA at 6:15 pm
  • Flight plan: IFR
  • Runway 21L, 5,001 ft by 100 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 66°F (19°C), dew point 46°F (8°C)
  • Altimeter: 30.13 inHg
  • Observation at 2:53 pm from KPDK, 1 miles away

Weather report (METAR): KPDK 181853Z 00000KT 10SM CLR 19/08 A3013 RMK AO2 SLP202 T01940078

Injuries

FatalSeriousMinorNone
Flig1
Passengers1

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ERA24LA012.