The U.S. aircraft register, updated daily
Accidents · NTSB ANC26LA038 · Final report

Textron Aviation INC B300C accident near Salcha, Alaska, May 5, 2026

On May 5, 2026 at about 8:47 pm local time, a 2019 Textron Aviation INC B300C, registered N67RF, was substantially damaged in an accident during enroute (cruise) near Salcha, Alaska (Fairbanks International Airpor airport). It was a public-use flight (federal) under public-use (government) rules. No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

An in-flight collision with a bird during cruise flight.

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

What the record shows

Date
May 5, 2026 · about 8:47 pm local time · cases in 2026
Place
Salcha, Alaska · Fairbanks International Airpor · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 4 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Textron Aviation INC B300C, built 2019
Registration
N67RF · registry record · serial FM-80
Damage
Substantial damage
Flight
Public-use flight (federal) · public-use (government) rules

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

The flight crew reported that, during cruise flight, the airplane encountered a flock of geese. The geese passed on all sides of the airplane, and a slight vibration was felt as they passed. The crew performed a visual inspection of the engines and wings; no damage was observed. Flight control continuity was checked, and all controls operated normally. Engine indications remained within normal parameters. The crew continued the flight to the destination airport and the airplane landed safely. A post-flight inspection of the airplane revealed that a bird had impacted the leading edge of the right horizontal stabilizer, resulting in substantial damage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

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. Birdstrike during enroute (cruise) defining event

The NTSB's findings

  • Environmental issues › Physical environment › Object/animal/substance › Animal(s)/bird(s) › Effect on equipment
  • Environmental issues › Physical environment › Object/animal/substance › Animal(s)/bird(s) › Ability to respond/compensate

Pilot

  • Certificate: airline transport pilot, private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 2,652.8 hours in all; 224.1 in this make and model; 64 in the last 90 days; 25 in the last 30 days; 2,157.1 as pilot in command
  • Last flight review: June 23, 2025
  • Medical certificate: None (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 593 hours in all; 229 in this make and model; 95 in the last 90 days; 29 in the last 30 days; 280 as pilot in command
  • Last flight review: July 24, 2025
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

Other crew

  • Seat: left
  • Injury: no injuries

Other crew

  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,593.1 hours
  • Last inspection: approved inspection programme, February 9, 2026
  • Maximum gross weight: 16,500 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine 1: Pratt & Whitney PT6A-60A (turboprop); 3,593 hours total
  • Engine 2: Pratt & Whitney PT6A-60A (turboprop); 3,593 hours total

The flight

  • Departed from: FAI Fairbanks AK at 7:32 pm
  • Destination: FAI Fairbanks AK
  • Flight plan: VFR
  • Runway 20R, 11,800 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 320° at 15 knots, gusting 27
  • Visibility: 10 statute miles
  • Sky: broken clouds at 5,500 ft; a few clouds at 3,500 ft
  • Temperature: 50°F (10°C), dew point 36°F (2°C)
  • Altimeter: 29.56 inHg
  • Observation at 12:41 pm from ABI, 52 miles away

Weather report (METAR): PABI 052041Z 32015G27KT 10SM FEW035 BKN055 BKN100 BKN200 10/02 A2956 RMK AO2 PK WND 18031/2019 WSHFT 2027 SHRA VC W-N VIRGA DSNT NE SW T01000017 $

Injuries

FatalSeriousMinorNone
Flight crew4

Photographs from the investigation 2 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

2 documents, released by the NTSB on October 27, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 10 pages View Download
2 Photos PDF, 3 pages · our copy View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ANC26LA038.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.