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

Piper PA-32-301 accident near King Salmon, Alaska, June 28, 2012

On June 28, 2012, a Piper PA-32-301, registered N8470Y, was substantially damaged in an accident during enroute (cruise) near King Salmon, Alaska. It was flown under charter and air-taxi rules (Part 135). No one was hurt; 1 person was 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
June 28, 2012 · cases in 2012
Place
King Salmon, Alaska · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-32-301 · all PA-32-301s on the register
Registration
N8470Y · registry record · serial 32-8206012
Damage
Substantial damage
Flight
Flight · charter and air-taxi rules (Part 135)

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

The pilot reported that, while in level cruise flight, a bird struck the right wing tip. The airplane sustained substantial damage to the right wing.

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

  • Aircraft › Aircraft structures › Wing structure › Ribs/bulkheads (on wing) › Damaged/degraded other cases naming the airframe structure
  • cause Environmental issues › Physical environment › Object/animal/substance › Animal(s)/bird(s) › Effect on equipment

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; multi-engine sea; single-engine land; instrument: airplane
  • Flight time: 40,888 hours in all; 30,000 in this make and model; 68 in the last 90 days; 20 in the last 30 days
  • Last flight review: May 22, 2012
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 14,765 hours
  • Last inspection: 100-hour inspection, June 26, 2012
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Lycoming IO-540 SER (piston); 0 hours total
  • Operator: Peninsula Airways INC

The flight

  • Departed from: Egegik AK at 7:10 pm
  • Destination: PAKN King Salmon AK
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 210° at 4 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 1,600 ft
  • Temperature: 48°F (9°C), dew point 43°F (6°C)
  • Altimeter: 29.80 inHg
  • Observation at 6:54 pm from PAKN

Injuries

FatalSeriousMinorNone
Flight crew1

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

1 document, released by the NTSB on August 8, 2012. 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.

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/ANC12CA063.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.