- Date
- July 4, 1986, 06:10 local (12:10 UTC)
- Place
- Ashland, MT
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Maneuvering
- Aircraft
- N40660Piper J-3
- Weather
- Visual (VMC) · Day
- Status
- Completed
- Report
- Approved by Office Director
- FAA report
- 19860704030359A
- Case key
- 17003
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Sequence of events
NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.
Analysis
Plt did not possess a plt certificate or medical certificate. The plt stated that he fueled the acft with the 'last gas in the storage tank.' The plt preflighted the acft and took off. Shortly after takeoff the engine lost power. The plt executed a landing in an alfalfa field and struck an irregation ditch. After the accident the plt stated in the NTSB accident report that 'this accident could have been prevented by changing filter on bulk tank and letting water settle in tank before draining sump and gascolator'.
Aircraft
- Registration
- N40660
- Reported as
- Piper J-3
- Category
- Airplane
- Serial number
- 7421
- Airframe hours
- 5,153
- Engine
- Continental C-85-8, 85 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Aerial application · Part 137
- Registered owner
- Kirk E. Green
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · December 1, 1985
- Departed
- 3U3 · Ashland, MT
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Seat
- Front
- Flight hours
- 480 total · 480 in this make and model · 474 as pilot in command · 25 in the last 90 days · 1 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- Calm
- Visibility
- 50 statute miles
- Lowest ceiling
- None
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.