ERA25LA061 · Beech B300
Barrel King Beech B300 · Accident: loss of control on ground during landing
From DeKalb Peachtree Airport (PDK) to an unrecorded destination
Event
- NTSB case
- ERA25LA061
- 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
- Ongoing
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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 B300
- 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
- N907EJ
- Operator
- Barrel King
- Onboard fatalities
- Unknown
- Route
- From DeKalb Peachtree Airport (PDK), Atlanta, GATo not recorded
- Aircraft age
- About 27 years (built 1997)
- 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
- Loss of control on ground
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On November 28, 2024, about 1019 eastern standard time, a Beech B300, N907EJ, was substantially damaged when it was involved in an accident near Franklin, North Carolina. The airline transport pilot was not injured. The airplane was operated as a Title 14?Code of Federal Regulations Part 91 personal flight. The pilot stated that prior to departure he exercised ground fine pitch of the propeller blades to allow for normal deceleration while taxiing and both worked, “…perfectly fine and in tandem.” The flight departed en route to the destination airport and although Federal Aviation Administration (FAA) Automatic Dependent Surveillance-Broadcast (ADS-B) data ended when the flight was about 3 nautical miles south-southeast of the destination airport, which was equipped with Virtower, an airport operations tracking system. The Virtower system tracked the airplane flying east of the airport then turning left consistent with entering the downwind leg of the airport traffic pattern for runway 7. The pilot noted the last automated weather observing system (AWOS) report he received as he overflew the airport was that the wind was from 360° at 12 knots with gusts to 18 knots which was verified by the windsock. He also reported encountering light to moderate terrain induced turbulence on approach and landing. The pilot reported the airplane was on the final approach leg of the airport traffic pattern, with the propeller controls set to 1,500 rpm, and the flaps to full. The pilot reported that the airplane was at 114 knots indicated airspeed at 50 ft, while the Virtower data reflected the airplane’s groundspeed was 130 knots just past the runway threshold. The pilot indicated that the flight touched down just past the aiming point marking which was confirmed by video evidence, reporting the speed at touchdown as 112 knots, which was his calculated Vref speed plus 10 knots. The Virtower data reflected that the groundspeed was 120 knots just before the aiming point marking. The pilot reported that after touchdown, left aileron input remained for crosswind control and he pushed each propeller control full forward and selected Beta propeller blade angle. He did not feel a reduction in the overall speed of the airplane while in Beta, and then applied maximum reverse for both propellers. The Virtower data reflected that after touchdown the airplane remained on the runway centerline until after 1018:29 when the airplane was at 110 knots groundspeed. Between that data point and the next Virtower data point at 1018:33 when the groundspeed was 90 knots, the airplane’s ground track began to veer to the right which the pilot reported he sensed as asymmetric thrust by the left engine/propeller, despite full left deflection of rudder, and maximum braking. Video evidence that depicted a portion of the landing roll and the accident sequence showed gray colored smoke trailing the left main landing gear while on the runway. The airplane departed the right side of the runway onto grass, crossed a taxiway, hit a ditch and a taxiway sign which collapsed the nose landing gear. The pilot shut down the engines and removed electrical power to the airplane. A weather observation taken at the destination airport about 4 minutes before the accident reported the wind from 320° at 7 knots, gusting to 15 knots, winds variable 290° to 360°, while an observation taken about 1 minute after the accident reported the wind from 340° at 7 knots, winds variable 320° to 020°. Preliminary examination of the airplane revealed that the inboard tire of the left main landing gear exhibited flat spotting through the tread, consistent with a sliding tire. The airplane was equipped with a Garmin primary flight display installed at the pilot and co-pilot’s positions and a multi-function display; all contained a Secure Digital (SD) card. The airplane was also equipped with a cockpit voice recorder (CVR). The SD cards and CVR were retained and shipped to the NTSB’s Vehicle Recorders Division for read-out.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ERA25LA061
- Event ID
- 20241128195558
- Case number
- ERA25LA061
- 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: 899aa23d2589240bfe7c960b329542103f704d0294ee066435a0aeba6c8cb940; retrieved 2026-09-16T19:30:35.090Z.