Globe GC 1B accident near Puyallup, Washington, July 5, 2014
On July 5, 2014 at about 10:13 pm local time, a 1946 Globe GC 1B, registered N3773K, was substantially damaged in an accident during approach (VFR pattern base) near Puyallup, Washington (Pierce County -Thun Field). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 5, 2014 · about 10:13 pm local time · cases in 2014
- Place
- Puyallup, Washington · Pierce County -Thun Field · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Globe GC 1B NO SERIES, built 1946 · all GC 1Bs on the register
- Registration
- N3773K · registry record · serial 1466
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (total) during approach (VFR pattern base) defining event
The NTSB's findings
- cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng cyl section › Failure other cases naming the engine
- cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng cyl section › Incorrect service/maintenance other cases naming the engine
- Environmental issues › Physical environment › Object/animal/substance › (general) › Contributed to outcome
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 2,059 hours in all; 779 in this make and model; 30 in the last 90 days; 9 in the last 30 days; 1,960 as pilot in command
- Last flight review: January 13, 2013
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,432 hours
- Last inspection: annual inspection, October 20, 2013; 30 hours since
- Maximum gross weight: 1,970 lb
- Seats: 2
- Landing gear: fixed
- Engine: Continental Motor IO-360-KB3B (piston); 1,393 hours total
The flight
- Departed from: 2S1 Vashon WA at 9:55 pm
- Destination: PLU Puyallup WA
- Flight plan: none
- Runway 34, 3,650 ft by 60 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: scat at 2,400 ft
- Temperature: 75°F (24°C), dew point 64°F (18°C)
- Altimeter: 30.10 inHg
- Observation at 10:15 pm from PLU
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
9 documents, released by the NTSB on April 4, 2016. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Materials Laboratory Factual Report | PDF, 13 pages | View Download |
| 3 | Test and Research | PDF, 6 pages | View Download |
| 4 | Maintenance Record Excerpts | PDF, 6 pages | View Download |
| 5 | Mechanic Letter | PDF, 1 page | View Download |
| 6 | Metal Analysis | PDF, 2 pages | View Download |
| 7 | Oil Analysis | PDF, 1 page | View Download |
| 8 | Jpi Engine Information | PDF, 1 page | View Download |
| 9 | Statement of Party Representatives to NTSB Investigation | PDF, 14 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N3773K on the register today · the tail number may have moved to another aircraft since
- Globe GC-1 Swift 425 registered today · the model family and its accident history
- Globe 425 aircraft on the register
- Engine: Continental Motor IO-360-KB3B 1,854 aircraft carry this series today · as the NTSB recorded it
- Pierce County/Thun Field · nearest airport
- Vashon Municipal · departed from
- Accidents and incidents in Washington 2,713 since 1982 · 361 in the last ten years
- Washington 10,663 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR14LA284.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
