WPR14LA284 · Globe GC 1B
Globe GC 1B · Accident: loss of engine power (total) on approach
From Vashon Municipal Airport (2S1) to Pierce County-Thun Field (PLU)
Event
- NTSB case
- WPR14LA284
- 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
Globe GC 1B
- Aircraft type
- Globe GC-1
- 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
- N3773K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Vashon Municipal Airport (2S1), Vashon, WATo Pierce County-Thun Field (PLU), Puyallup, WA
- Aircraft age
- About 68 years (built 1946)
- 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
- Approach · VFR pattern base
- 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
- Loss of engine power (total)
- 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 power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot/owner of the airplane was conducting a local personal flight. The pilot reported that, while the airplane was in the traffic pattern at the destination airport, the engine made a loud "bang" and experienced a loss of power. His attempts to regain engine power were unsuccessful, and the airplane descended and then collided with an embankment located on the airport property before the runway.
Examination of the engine revealed a large mechanically formed hole on the top side of the No. 3 piston, and the cylinder head had sustained significant mechanical damage. The exhaust valve head was separated from its stem and lodged in the exhaust valve seat perpendicular to its normal seated position. The stem was not located. Numerous pieces of the No. 3 cylinder's fractured piston and piston rings and other metal debris were found throughout the engine.
A metallurgical examination revealed that only the No. 3 cylinder's liberated valve head fragment remained, and the nature of the fracture could not be determined due to the subsequent damage sustained from the head battering against the piston crown. The mating valve stem was missing, and there were no remnants of its material in the cylinder. The valve stem seat keepers and the exhaust rocker arm were significantly damaged. Although the damage to the keepers and rocker arm may have occurred after the exhaust valve failed, the wear marks on the interior surfaces of the No. 3 exhaust retainer suggested that the valve seat keepers were not properly aligned, which may have resulted from their being installed improperly at one point or the valve stem being undersized; however, without the missing valve stem to examine, this could not be conclusively determined. There were no indications of foreign material or contamination in or on the No. 3 cylinder assembly components.
A review of the engine's maintenance records and invoices indicated that, about 30 hours before the accident, the Nos. 3 and 5 cylinders underwent repairs due to exhaust anomalies noted during the airplane's most recent annual inspection. The logbook entry for this maintenance action stated, in part, that both the Nos. 3 and 5 cylinders were removed and that the exhaust guides and valves were replaced with new parts.
The next and last maintenance entry in the engine's logbook indicated that, about 19 flight hours following the previous maintenance, the pilot changed the oil and found metal flakes in the oil filter. He sent a sample of the oil to a laboratory for analysis, and the results showed that it contained a high quantity of metal, some of which was identified as metal consistent with valve keys (keepers) material. The oil/material analysis report recommended contacting the engine manufacturer's service representative; however, the pilot did not do so.
Probable cause
The failure of the exhaust assembly in the No. 3 cylinder for reasons that could not be determined due to the damage incurred to the fractured parts. Also causal to the accident was maintenance personnel’s improper installation of the cylinder.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14LA284
- Event ID
- 20140708X15409
- Case number
- WPR14LA284
- 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: 0c872df5015ae46a1006f84994d4db2875c79076dd88b5ff6add12b3449157c8; retrieved 2026-09-16T00:50:59.526Z.