NTSB CAROL · Event
Event SEA04LA084
Registry · N37982
FAA Aircraft Registry record.
Make / Model
PIPER J4E
Year of manufacture
1941 · 63 years old at event
Engine
CONT MOTOR C85 SERIES (85 hp)
Seats / Engines
2 seats · 1 engine
ADS-B equipped
Yes — Mode-S A458C5
Registrant of record
MT AIR LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
A loss of engine power due to fuel exhaustion while in cruise flight as a result of inadequate preflight planning / preparation. Factors contributing to the accident were the short landing field and trees.
Factual narrative
On May 17, 2004, at about 1922 mountain daylight time, a Piper J4/E, N37982, registered to and being operated by the pilot as a 14 CFR Part 91 personal flight, experienced an un-commanded reduction of engine power. The pilot initiated a forced landing in a field about one-half of a mile north of Ferndale Airfield, Bigfork, Montana. Although the initial landing was uneventful the rollout resulted in a nose over. The aircraft was substantially damaged and the airline transport pilot, the sole occupant, was not injured. Visual meteorological conditions prevailed and no flight plan had been filed. The flight departed Ferndale, Montana, about one hour prior to the accident. In a telephone conversation and subsequent written statement, the pilot reported that while returning to land at the airport, the engine began to "surge". Carburetor heat was applied with no effect. The pilot continued towards the airport, but was not able to maintain altitude or establish visual contact with the airport due to terrain. The pilot further reported that since he was unable to reach the airport, he turned approximately 180-degrees and initiated a forced landing in a field. During the landing roll the pilot, in an attempt to avoid running into trees, applied the brakes "aggressively" which resulted in a nose over. During a follow-up telephone conversation the pilot reported, "I am convinced the engine quit running because of fuel starvation." He related that the airplane had been "topped" three days earlier and had been flown two hours previous to the day of the accident. On the day of the accident he flew for about an hour. He further revealed that he was aware that the wing tank was empty because he had observed "bubbles" in the fuel sight gauge, which extends out the bottom of the wing tank. The pilot also reported that the airplane was equipped with one 18-gallon wing tank, and a 7-gallon header tank. Post accident examination of the aircraft by maintenance personnel from Discount Aircraft Salvage, found all engine controls to be functioning properly and approximately one tablespoon of fuel was drained from the fuel gascolator. After adding approximately one gallon of fuel to the header tank, the engine was started and ran smoothly with no malfunction or failures noted. The pilot reported that while returning to land at the departure airport, the engine began to "surge". The pilot continued towards the airport but was not able to maintain altitude or establish visual contact with the airport due to terrain. The pilot further reported that since he was unable to reach the airport, he turned approximately 180-degrees and initiated a forced landing in a field. During the landing roll the pilot, in an attempt to avoid running into trees, applied the brakes "aggressively" which resulted in a nose over. In a telephone conversation and subsequent written statement, the pilot reported, "I am convinced the engine quit running because of fuel starvation." He related that the airplane had been "topped" three days earlier and had been flown two hours previous to the day of the accident. On the day of the accident he flew for about an hour. He further revealed that he was aware that the wing tank was empty because he had observed "bubbles" in the fuel sight gauge, which extends out the bottom of the wing tank. The pilot also reported that the airplane was equipped with one 18-gallon wing tank, and a 7-gallon header tank. Post accident examination of the aircraft by maintenance personnel from Discount Aircraft Salvage, found all engine controls to be functioning properly and approximately one tablespoon of fuel was drained from the fuel gascolator. After adding approximately one gallon of fuel to the header tank, the engine was started and ran smoothly with no malfunction or failures noted. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2004_SEA04LA084.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.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (fuel exhaustion, fuel starvation, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗