NTSB CAROL · Event
Event SEA04LA113
Registry · N27135
FAA Aircraft Registry record.
Make / Model
PIPER J3L-65
Year of manufacture
1940 · 64 years old at event
Engine
LYCOMING 0-145B SERIES (65 hp)
Seats / Engines
2 seats · 1 engine
Last airworthiness date
19570904
ADS-B equipped
Yes — Mode-S A2AD12
Registrant of record
BARR MYRON
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's failure to maintain clearance from the trees while maneuvering at a very low level in hilly terrain. Factors include hilly terrain, and thickly forested slopes in the area where the pilot was maneuvering.
Factual narrative
On June 21, 2004, approximately 1250 Pacific daylight time, a Piper J-3, N27135, impacted a number of trees during low-level maneuvering about three miles south of Glenoma, Washington. The private pilot, who was the sole occupant, received serious injuries, and the aircraft, which is owned and operated by the pilot, sustained substantial damage. The 14 CFR Part 91 personal pleasure flight, which departed Chehalis-Centralia Municipal Airport, Chehalis, Washington, about one hour prior to the accident, was being operated in visual meteorological conditions. No flight plan was filed, but the pilot's ultimate destination is believed to have been Thun Field, Puyallup, Washington. According to witnesses, the aircraft was observed flying very low and slow through the thickly forested hilly terrain just east of the east end of Riffe Lake. The witnesses said that the airplane made a steeply banked turn, reversed course, and then disappeared behind some trees. When the aircraft did not reappear, some of the witnesses went searching for the aircraft, and found that it had impacted a number of trees along the slope of a steep incline. A post-accident inspection of the aircraft and its engine did not reveal any evidence that there had been any malfunction or anomaly in the flight control system or in the operation of the engine. It was further determined that the aircraft had taken on 8.25 gallons of aviation fuel approximately 70 minutes prior to the accident. As of this date, the pilot, who was severely injured in the crash, has no recollection of the accident sequence, and is still unable to complete an NTSB Form 6120.1/2. Just prior to the accident, the aircraft was observed flying very low and slow through the hilly terrain just east of the east end of Riffe Lake. The airplane then made a steeply banked turn, reversed course, disappeared behind a line of trees, and then impacted a number of trees along the slope of a steep incline. A post-accident inspection of the aircraft and its engine did not reveal any evidence that there had been any malfunction or anomaly in the flight control system or in the operation of the engine. It was further determined that the aircraft had taken on 8.25 gallons of aviation fuel approximately 70 minutes prior to the accident. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2004_SEA04LA113.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.