Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

March 20, 2017 · Swearingen SA226 TC · N158WA

Boise, ID

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
March 20, 2017
Injury Outcomes
No injuries (1 uninjured)
Location
Boise, ID
Aircraft
Swearingen SA226 TC (1981)
Tail Number
N158WA
Injuries
None
Aircraft Damage
Substantial
NTSB Number
WPR17LA078

The airline transport pilot reported that he performed a preflight inspection of the airplane before departing on the repositioning flight. The takeoff roll was normal; however, just after the airplane lifted off, he heard a "pop" and felt a vibration. The pilot initially thought that one of the tires had blown, but as the vibration continued, he determined that he might have a problem with one of the propellers. The pilot subsequently returned to the airport and landed without further incident. When the pilot shut down the left engine after landing, he noticed that the tip of one of the propeller blades was missing. Further examination of the blade revealed that about 4 inches of the blade tip had separated and penetrated the side of the fuselage. Airport personnel later found additional pieces of propeller blade material on the runway, as well as what appeared to be the blade of a screwdriver and pieces of the handle. Maintenance personnel reported that a mechanic had been working on the airplane just before the flight and had been called away from the task he was performing before it was completed; the airplane was subsequently returned to service. The mechanic left a screwdriver on the nose of the airplane in the windshield wiper area, in a position that the pilot could not see. It is likely that, during the takeoff roll, the screwdriver became dislodged from the area of the windshield wiper and impacted the left propeller.

NTSB Probable Cause

Company maintenance personnel's failure to remove a screwdriver that was left lodged in the windshield wiper area of the forward fuselage during maintenance and subsequently became dislodged on takeoff/initial climb and collided with a left propeller blade.

Full Narrative

On March 20, 2017, about 0405 mountain daylight time, a Swearingen SA226TC, N158WA, was substantially damaged due to foreign object damage to the airplane's fuselage during initial takeoff/climb from Boise Air Terminal/Gowen Field (BOI), Boise, Idaho. The airline transport pilot was not injured. The airplane was registered to and operated by Western Airlines LC of Boise as a 14 Code of Federal Regulations Part 91 positioning flight. Visual meteorological conditions prevailed at the time, and an instrument flight rules flight plan was filed and active. The flight was originating at the time and destined for Salt Lake International Airport (SLC), Salt Lake City, Utah. In a written statement submitted to the National Transportation Safety Board investigator-in-charge, the pilot reported that prior to departing on the repositioning flight, he reviewed the maintenance data for the airplane (the Can) and found everything to be up to date. The subsequent preflight inspections, inclusive of the interior and exterior of the airplane revealed no anomalies. The pilot stated that at 0400 he called BOI ground control, obtained taxi clearance, and taxied to runway 10L where he began the takeoff roll. The pilot reported that everything was normal, rotated at 105 knots; shortly thereafter he heard a "pop", followed by a vibration. Thinking that he had a blown tire, he waited a few seconds to see if the frequency of the vibration would change as the tire rotation slowed. However, the vibration remained the same, which led him to think that there might be an issue with the propeller. The pilot radioed the BOI tower controller, advised him of his intension to return to the airport, and was instructed to turn right for Runway 10L. The pilot stated that on the downwind leg he thought there might be a problem with a propeller. However, after he inspected both propeller spinners to determine which propeller might be damaged, he determined that both were running smooth. The pilot further stated that as he had no indication as to which propeller was damaged and the vibration was light and not changing, he elected not to shut the engine down. The pilot then landed uneventfully, taxied to parking, and shut the right engine down first. The pilot then shut the left engine down. During the last few rotations of the propeller he observed the spinner wobble slightly; he then noticed that the tip of one of the blades was missing. The pilot stated that after having exited the airplane he observed that about four inches of one of the propeller blade tips was missing, as well as having observed two holes in the fuselage, [both caused by pieces of the propeller blade tip]. About 10 minutes later airport operations personnel delivered another piece of the propeller [blade], and what appeared to be the blade of a screwdriver and two pieces of a screwdriver handle. A further examination of the airplane revealed a third hole in the fuselage further back [of the left] wing root just below the window. During a postaccident inspection of the airplane, a Federal Aviation Administration aviation safety inspector reported that maintenance had been performed on the airplane prior to the flight, and that the mechanic was called away from the task he was performing prior to it being completed. The inspector stated that a screwdriver was left on the nose of the airplane under the windshield wiper and out of sight of the pilot. Subsequently, on takeoff roll the screwdriver became dislodged and impacted the left propeller; remnants of two pieces of a propeller blade were found to have penetrated the left side fuselage and came to rest inside the cabin of the airplane. The screwdriver was subsequently located lying on the surface of the departure runway.

Flight

Event TypeAccident
Event Time03:05 PDT
Nearest AirportBoise Air Terminal/Gowen Field (0nm E)
Runway10L
Runway Length10000 ft
Runway Width150 ft
Flight Plan FiledIFR
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftSwearingen SA226 TC
Tail NumberN158WA
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines2
Engine TypeTurboprop
Engine DetailsHoneywell · TPE-331-10UA · Turboprop · 940 | Honeywell · TPE-331-10UA · Turboprop · 940
Seats3

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 62 · Second Class · None

Conditions

ConditionsVMC
LightDark Night
Wind170° @ 7 kt
Visibility10 sm
CeilingOvercast 12000 ft
Temperature / Dew Point48 / 45 C
Altimeter30.05 inHg
Observation Time09:53
Weather SourceWFAC

Appendix: Source Data