Aviation Crash Map

Beechcraft F35 N4224B

10 June 2015 · Everett, Washington, United States · Fatal

Summary

On 10 June 2015 at about 16:09 local time, a Beechcraft F35 registered N4224B was involved in an accident near Everett, Washington, United States. 2 people were on board and one died, one was seriously injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 16:09
Classification
Accident
Location
Everett, Washington, United States
Nearest airport
Snohomish County (Paine Fld) (PAE)
Coordinates
47.8914, -122.2842
Aircraft
Beechcraft F35
Registration
N4224B
Category
Airplane
Year built
1955
Engines
1
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Instructional
Phase of flight
Not recorded
Route
Everett → Everett
Aircraft damage
Substantial
Weather
VMC
Light
Day
NTSB number
WPR15FA181

People

1 person died.

On board Died Serious Minor Uninjured
2 1 1 0 0

Probable cause

The partial loss of engine power during takeoff due to debris within the fuel servo, which restricted fuel flow throughout the engine fuel system and resulted in a partial loss of engine power.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

The pilot receiving instruction reported that following a normal taxi and pre takeoff engine run up, the flight instructor initiated the takeoff sequence for a local instructional flight. He noted that during the takeoff, the flight instructor retracted the landing gear and the airplane began a slow climb, however, it seemed like the airplane had no power to climb. The pilot receiving instruction further stated he saw the flight instructor managing the fuel and verifying the throttle position as the airplane began to descend. Subsequently, the airplane impacted a grassy wetland area on the departure end of the runway. Postaccident examination of the airplane revealed erratic fuel flow from the fuel nozzles. Further examination of the engine revealed that the fuel servo inlet fuel screen was installed 180-degrees opposite of the manufacturer's installation instructions, which would allow for unfiltered debris to flow throughout the fuel system. The engine was installed on a test cell and during the first 5 engine run attempts, it was noted that the engine was not firing on all cylinders, and would not produce rpm over 1,500. The fuel servo unit was removed and a carburetor was subsequently installed. The engine started and ran successfully at various power settings for about 23 minutes prior to being shut off utilizing the engine test cell fuel shut off. Disassembly of the fuel servo revealed a significant amount of debris in two of the fuel diaphragm housings, and on the diaphragm assemblies, one of which regulates fuel to the fuel injectors. The mixture control valve and idle valve exhibited evidence of corrosion. The idle valve was found seized within its respective galley. Upon removal, corrosion was observed within the galley. The debris observed within the fuel servo was removed and visually, the debris was composed of two optically different particle types. The debris was predominately larger grey white particles mixed with lesser amounts of smaller dark brown particles. X-ray fluorescence spectrometer examination of several different areas of the grey white particles indicated compositions consistent with aluminum alloys. The white appearance and crumbling nature of the particles was indicative of heavily oxidized aluminum. Spectra of the dark brown particles were consistent with low alloy steels. The appearance and dark color was indicative of heavy oxidization of the particles. The source of the debris within the fuel servo and whether the misinstalled fuel screen allowed the debris to enter the servo could not be determined. It is likely that the debris within the fuel servo was distributed throughout the engine fuel system, which allowed for restricted fuel flow to each of the fuel injectors, which would result in an erratic running engine and partial loss of engine power.

Quoted verbatim from the NTSB record.

Other Beechcraft F35 accidents

Date Aircraft Location Operator Outcome Died
27 Jul 2015 Beechcraft F35
N988RH
Riverside, California, United States - Fatal 1
30 Mar 2016 Beechcraft F35
N4212B
Long Island, North Carolina, United States - Minor injuries -
7 Feb 2018 Beechcraft F35
PT-AVO
Itaituba, Brazil Conal Construtora Nacional de Avioes Ltd Fatal 3
27 Jul 2010 Beechcraft F35
N3858B
Enid, Oklahoma, United States - No injuries -
24 Dec 2010 Beechcraft F35
N3448B
Syracuse, New York, United States - No injuries -
5 Jul 2020 Beechcraft F35
N4219B
Ravenna, Texas, United States - Minor injuries -

All 139 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
29 Jan 2015 Piper PA 12
N918TF
Ridgefield, Washington, United States Nicolai Jane G No injuries -
3 Nov 2015 MD Helicopters 369D
N510PA
Sedro-Woolley, Washington, United States Olympic Air Inc No injuries -
11 Jun 2015 Beechcraft RC 45J
N585PB
Everett, Washington, United States Historic Flight Foundation No injuries -
10 Feb 2015 Van's RV7-UNDESIGNAT
N513BW
Belfair, Washington, United States Brooks D Wolfe Minor injuries -
16 Jun 2015 Rockwell S 2R
N8420V
Washtucna, Washington, United States - Serious injuries -
28 Apr 2015 Cessna 170B
N1296D
Centralia, Washington, United States - Serious injuries -

All 170,864 records in United States