ERA17CA047 · Hawker Beechcraft Corp G58
Hawker Beechcraft Corp G58 · Accident: runway excursion during landing
From Waycross Ware County Airport (AYS) to DeKalb Peachtree Airport (PDK)
Event
- NTSB case
- ERA17CA047
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- 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
Hawker Beechcraft Corp G58
- Aircraft type
- Beechcraft 58
- 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
- N525
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Waycross Ware County Airport (AYS), Waycross, GATo DeKalb Peachtree Airport (PDK), Atlanta, GA
- Aircraft age
- About 9 years (built 2007)
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the commercial pilot, the multiengine airplane was about 5 miles from the airport when it was cleared to land on runway 3R. Then, about 1.5 miles from the airport, he accepted a landing clearance change from the air traffic controller to land on runway 3L instead of 3R. The pilot increased engine power and set up to land on runway 3L; however, the airplane was "fast" on final approach and landed "long." The pilot "stood" on the brakes, the left tire "blew out," and the airplane veered off the left side of the runway. After departing runway 3L, the airplane traveled through the grass and impacted asphalt of another runway, which was raised about 7 inches above the ground. When the nose landing gear struck the asphalt, it collapsed, and the airplane then came to rest. During the accident sequence, the fuselage and wings were substantially damaged. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The wind at the airport around the time of the accident was from 140°at 7 knots.
Probable cause
The pilot’s failure to maintain the proper airspeed during final approach and his subsequent loss of directional control during landing, which resulted in a runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17CA047
- Event ID
- 20161116X91827
- Case number
- ERA17CA047
- 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. 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: e50f9fcae17e0a0c9f2d709b17fb90b1e3e93ba544a3cdb7e22b0ce525f2ffb3; retrieved 2026-09-16T04:50:41.270Z.