FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17LA031 · Piper PA 31T UNDESIGNAT

5 Dec 2016 · Missoula, MT, United States

Piper PA 31T UNDESIGNAT · Accident: part(s) separation from aircraft en route

From Kalispell City Airport (S27) to Harry Reid International Airport (LAS)

Report a problem

Event

NTSB case
WPR17LA031
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
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
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
Instrument Meteorological Cond

Piper PA 31T UNDESIGNAT

Aircraft type
Piper PA-31
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
N909PW
Operator
Unknown
Onboard fatalities
Unknown
Route
From Kalispell City Airport (S27), Kalispell, MTTo Harry Reid International Airport (LAS), Las Vegas, NV
Aircraft age
About 39 years (built 1977)
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
En route · cruise
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
Part(s) separation from aircraft
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

  • Aircraft › Aircraft structures

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot reported that, during cruise flight, the left windshield suddenly departed the airplane. The airplane was below its published service ceiling of 29,000 ft and the windshield was not subjected to internal pressure above its limitations at the time of the failure. The pilot entered an emergency descent and landed the airplane at an airport without further incident. The lack of windshield debris in the cockpit and the glass embedded in the left propeller indicated that the left windshield blew outward. Examination of the right windshield, which remained on the airplane, revealed evidence of moisture ingression into the laminate, to include cloudiness in the vinyl layer, interlayer cracking, delamination around the edges of the windshield, and corrosion of the aluminum retainer. Remnants of the left windshield were insufficient to establish if the laminate exhibited the same evidence of moisture ingression. Examination of the right windshield showed that the discrepancies were consistent with delamination as defined in the manufacturer's service manual. The discrepant areas had only progressed up to ½ inch into the daylight opening. The cloudiness, interlayer cracking, and delamination noted along the upper and lower edges of the right windshield were visible to the pilot before the accident flight. However, the delamination of the right windshield would not have necessitated immediate replacement based on the published service information, and although it is impossible to determine the condition of the left windshield before the flight, it was likely similar to that of the right windshield.

The left windshield aluminum retainer exhibited corrosion around the periphery that was more extensive than that on the right windshield. The corrosion of the aluminum retainer is impossible to see with the windshields installed in the airplane, since the fuselage windshield frame covers the entire flange area.

Windshields were designed in a manner to transfer their internal stresses equally around the windshield into the airframe structure. The corrosion of the aluminum retainer eliminated the load path for the internal windshield stresses to be transferred to the airframe. For each of the corroded areas on the aluminum retainer, there would have to be a redistribution of the internal stresses toward the intact areas, which would cause significant stress concentrations in the windshield laminate. These stress concentrations could be high enough to exceed the capabilities of the laminate in local areas. If coupled with a fracture of one glass layer, the stress concentration would be intensified even more adjacent to the corroded retainer areas. The corroded retainer on the left windshield led to areas of stress concentration within the windshield laminate.

The precise initiation of the left windshield failure could not be conclusively determined. The little amount of glass remaining suggested that the fracture of the glass layers initiated in the aft portion of the windshield near the center. It is possible there was a peel chip that began the event, or simply that the stress concentrations adjacent to the corroded retainer were high enough to cause failure of the windshield laminate.

Probable cause

Failure of the left windshield due to moisture ingression into the windshield laminate, which deteriorated the strength of the windshield.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17LA031
Event ID
20161206X34431
Case number
WPR17LA031
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: 7c1ab3050836f5ccc26e71c6d8b5693d20723e5c6bf692d9ff0bb50d1dd71606; retrieved 2026-09-16T04:52:51.204Z.