Accident Glasair GlaStar N4579J,
ASN logo
ASN Wikibase Occurrence # 195692
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Friday 26 May 2017
Type:Silhouette image of generic GLST model; specific model in this crash may look slightly different    
Glasair GlaStar
Registration: N4579J
MSN: 5819
Year of manufacture:2012
Total airframe hrs:206 hours
Engine model:Lycoming O-320
Fatalities:Fatalities: 0 / Occupants: 1
Aircraft damage: Substantial
Location:Contra Costa County, Concord, CA -   United States of America
Phase: Landing
Departure airport:Concord, CA (CCR)
Destination airport:Concord, CA (CCR)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
The student pilot reported that the purpose of the flight was to practice landings. The takeoff was uneventful, but when the airplane was on the base leg, the engine suddenly quit without warning or making any abnormal noises. The pilot attempted to restart the engine several times without success. He initiated a forced landing onto a roadway, during which the left wing impacted a light pole. The nosewheel collapsed, and the airplane then crossed an intersection and slid to a rest.
Postaccident engine examination revealed that the carburetor was fracture-separated at the attachment flange, and the air box exhibited heavy impact damage. The carburetor was disassembled, and the needle valve and floats were observed stuck in the “up” position. Slight force was applied to the float assembly, and it moved freely. No contaminants or obvious bends in the float system were found. Although a stuck needle valve can restrict fuel from entering the carburetor bowl and lead to a loss of engine failure, impact damage precluded a determination of whether the needle was stuck before the accident or during the impact sequence. No other mechanical anomalies were found with the engine that would have precluded normal operation; therefore, the reason for the loss of engine power could not be determined.

Probable Cause: A total loss of engine power for reasons that could not be determined based on the available evidence. 

Accident investigation:
Investigating agency: NTSB
Report number: WPR17LA110
Status: Investigation completed
Duration: 8 months
Download report: Final report



FAA register:



Revision history:

27-May-2017 01:48 Geno Added
27-May-2017 06:25 Iceman 29 Updated [Time, Source, Embed code]
27-May-2017 07:17 harro Updated [Aircraft type]
07-Feb-2018 13:49 ASN Update Bot Updated [Time, Operator, Nature, Departure airport, Destination airport, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314