FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17LA104 · Evolution Air LLC LANCAIR EVOLUTION

15 May 2017 · Firebaugh, CA, United States

Evolution Air LLC LANCAIR EVOLUTION · Accident en route

From Livermore Municipal Airport (LVK) to Marana Regional Airport (AVQ)

Report a problem

Event

NTSB case
WPR17LA104
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
Visual Meteorological Cond

Evolution Air LLC LANCAIR EVOLUTION

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
N846PM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Livermore Municipal Airport (LVK), Livermore, CATo Marana Regional Airport (AVQ), Marana, AZ
Aircraft age
About 1 year (built 2016)
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
Miscellaneous/other
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 pilot reported that, while in cruise flight at 25,000 ft, the airplane's windshield shattered, immediately followed by a rapid decompression of the cabin. The pilot shut down the engine, entered an emergency descent, and navigated to a nearby airport. During the approach for landing, the pilot received an anomalous landing gear indication and chose to perform a gear-up landing. The airplane touched down with an 8-knot tailwind and slid along the runway until it impacted a fence, continued across a road, and came to rest in dirt. Both wings were substantially damaged. Postaccident testing showed that the relay modules responsible for opening and closing circuits to the left main landing gear were dislodged when the windshield shattered, resulting in the anomalous gear indication. The landing gear system functioned normally once the modules were reinstalled. A portion of the windshield that remained attached to the frame exhibited a fracture consistent with pure tension loading, likely from internal pressurization. Due to the curvature at that location, the fracture area was likely one of high stress on the windshield. Examination of the windshield fragments and frame did not show any evidence of impact from a foreign object, but showed significant structural flexing of the fuselage due to delaminated wet-layup plies during construction, as evidenced by extensive cracking at the aft engine cowling. However, the absence of an airplane structural analysis from the manufacturer precluded further review of the structural flexing of the fuselage. A material and bond evaluation showed that the windshield frame material did not exceed its glass transition temperature, indicating that the acrylic windshield was likely intact at the time of the failure; however, further analysis of the bond between the windshield and window frame could not be performed, as the manufacturer did not provide bond strength design values for either section. Several other factors in the construction of the windshield may have contributed to increased stresses at the location of a key fracture, which may have caused cracks to initiate and grow. In particular, parallel grinding marks around the edges of the windshield were inconsistent with the use of a dual-action grinder with 40-grit sandpaper as prescribed by the windshield installation instructions. These grinding marks may have introduced stress concentrations at the edge of the windshield and may have contributed to one of the primary windshield fractures. The overall appearance and mechanical behavior of the adhesive during the examination suggests that the bond strength between the windshield and frame was relatively low. Thus, the presence of disbonded areas may have affected the stress state on the windshield and contributed to increased stress at the primary fracture area. Finally, the overall composite layup varied from the specified layup schedule for the fuselage skin at two locations on the windshield frame. Alterations in the material used in the fuselage skin can change the elastic response to a given load. The change in the layup schedule and elastic response may have increased the stress at the location of the primary fracture area.

Probable cause

A failure in the windshield, frame, or windshield-to-frame bond, which resulted in a rapid decompression during cruise flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17LA104
Event ID
20170516X85801
Case number
WPR17LA104
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: b91151900db9d0ee0915c44e0ad55d6f0b0cf3f12be61759c7962a04e1dd99e0; retrieved 2026-09-16T05:17:25.396Z.