ERA24LA012 · Beech 300 UNDESIGNAT
CSW Aviation Beech 300 UNDESIGNAT · Accident: runway excursion during landing
From Savannah Hilton Head International Airport (SAV) to an unrecorded destination
Event
- NTSB case
- ERA24LA012
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Beech 300 UNDESIGNAT
- Aircraft type
- Beechcraft 300
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N93GA
- Operator
- CSW Aviation
- Onboard fatalities
- Unknown
- Route
- From Savannah Hilton Head International Airport (SAV), Savannah, GATo not recorded
- Aircraft age
- About 37 years (built 1986)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Runway excursion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft power plant
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA012
- Event ID
- 20231019193271
- Case number
- ERA24LA012
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: c53d64bff7fe973401b40ccfc6776cb95ea6ea904412170d1edf17027e9f16f6; retrieved 2026-09-16T18:14:02.884Z.