# NTSB ERA25LA061: Beech B300, N907EJ, Franklin, NC, November 28, 2024 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 3 · Limited · Preliminary report - Date: November 28, 2024, 10:19 local (15:19 UTC) - Place: Franklin, NC - Coordinates: 35.223074, -83.415684 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=35.2231&lon=-83.4157&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Investigation ongoing - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: FAA/ FSDO - NTSB case key (mKey): 195558 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA25LA061 - NTSB preliminary report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/195558/pdf - Page: https://openairdocs.org/ntsb/ERA25LA061 ## Preliminary report 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 runwayonto 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. ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Raytheon B300, 2 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7150007), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Raytheon B300, 2 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7150007), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Raytheon B300, 1 case](https://openairdocs.org/ntsb-events/094/sequence.md?model=7150007), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) ## Aircraft - Registration: [N907EJ](https://openairdocs.org/aircraft/N907EJ), registered now, S/N FL-161, built 1997 (OpenAirDocs) - Reported make and model: BEECH B300 - Registry model: [Raytheon B300](https://openairdocs.org/model/raytheon-b300) (registry code 7150007) (OpenAirDocs) - Registry engine: [Pratt & Whitney PT6A series](https://openairdocs.org/engine/pratt-whitney-pt6a-series) (registry code 52032, turbo-prop) (OpenAirDocs) - Category: Airplane - Serial number: FL-161 - Year built: 1997 - Airframe hours: 6742 - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Barrel King LLC - Registered owner: Barrel King LLC - Airworthiness certificate: Standard, Commuter - Last inspection: September 23, 2024 - Departed: PDK, Atlanta, GA - Destination: Same as departure - Airport: 1A5, Macon County, runway 07, 5,000 × 100 ft, asphalt - Equipment: Electronic primary flight display, Electronic multifunction display, Auto-pilot, ADS-B, Stall warning system ## Weather - Conditions: Visual (VMC), Day - Wind: 340° at 9 knots, gusting 16 - Visibility: 10 statute miles - Lowest ceiling: 3,700 ft broken - Temperature: 54 °F, dew point 46 °F - Altimeter: 29.87 inHg - Observed at: K1A5, 0.22 nm away - METAR: K1A5 281510Z AUTO 34009G16KT 10SM SCT028 BKN037 OVC050 12/08 A2987 RMK AO2 T01150077 ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20241128021749A](https://openairdocs.org/incident/20241128021749A), Nov 28, 2024: Raytheon Aircraft Company B300, Franklin, NC, Substantial damage. On November 28, 2024, about 1019 eastern standard time, a Beech B300 departed runway 7 during landing rollout at Macon County Airport (1A5). The aircraft… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.