# NTSB SEA04LA161: Piper PA-28-140, N4195J, Irby, WA, August 14, 2004

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Limited investigation · Final report
- Date: August 14, 2004, 09:00 local (16:00 UTC)
- Place: Irby, WA
- Coordinates: 47.366664, -118.833335
- Nearby events: https://openairdocs.org/map.md?lat=47.3667&lon=-118.8333&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Highest injury: Minor injuries
- Injuries: 1 minor
- Status: Completed, report December 3, 2004
- Report: Approved by Office Director
- Parties: FAA/FSDO
- NTSB case key (mKey): 59935
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA04LA161
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/59935/pdf
- Page: https://openairdocs.org/ntsb/SEA04LA161

## Probable cause

Loss of engine power for unknown reasons.  Trees and rough/uneven terrain were factors.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Loss of engine power, go-around (vfr)
  - reason for occurrence undetermined (cause)
- Forced landing, emergency descent/landing
- On ground/water collision with object, emergency descent/landing
  - object - tree(s) (contributing factor)
  - terrain condition - rough/uneven (contributing factor)

## Analysis

The pilot reported that he was attempting to land on the private dirt airstrip which is about 1,500 feet in length and 25 feet wide with surrounding hilly terrain.  The first landing attempt resulted in a go-around due to the aircraft altitude and airspeed were too high on final approach.  During the second attempt, the pilot stated that he was unsure if the landing gear touched the surface before the end of the airstrip and the initiation of the go-around.  The pilot stated that when he pushed in the throttle to go-around, the engine produced no power.  The pilot lowered the nose of the airplane, however the airspeed decreased and the aircraft collided with the terrain and trees.  During the on-site inspection of the engine and subsequent engine run, no evidence of a mechanical failure or malfunction was found.

## Factual narrative

On August 14, 2004, about 0900 Pacific daylight time, a Piper PA-28-140, N4195J, registered to and operated by the pilot as a 14 CFR Part 91 personal flight, collided with trees following a loss of engine power at a private airstrip located near Irby, Washington.  Visual meteorological conditions prevailed at the time and no flight plan was filed.  The aircraft was substantially damaged and the private pilot, the sole occupant, received minor injuries.  The aircraft departed from Colville, Washington, about one hour prior to the accident.

During a telephone interview and subsequent written statement, the pilot reported that he was attempting to land on the private dirt airstrip which is about 1,500 feet in length and 25 feet wide with surrounding hilly terrain.  Field elevation was reported as 1,600 feet mean sea level (MSL).  The pilot stated that the first landing attempt resulted in a go-around due to the aircraft altitude and airspeed were too high on final approach.  During the second attempt, the pilot stated that he was unsure if the landing gear touched the surface before the end of the airstrip and the initiation of the go-around.   The pilot stated that when he pushed in the throttle, the engine produced no power.  The pilot lowered the nose of the airplane, however the airspeed decreased and the aircraft collided with the terrain and trees.

A Federal Aviation Administration Inspector from the Spokane, Washington, Flight Standards District Office responded to the accident site and reported that the aircraft came to rest in a gully to the south, and approximately 30 yards past the west end of the east/west oriented airstrip.   The accident site is about 25 feet lower than the runway surface.  Wreckage debris consisting of the right side main landing gear and the nose gear were noted beginning about 64 yards from the fuselage.  The fuselage appeared to have skidded across the rough terrain on the nose and cowling, rotating to the right with the nose of the airplane coming to rest in a northerly direction and the fuselage resting against several trees.

The Inspector reported that fuel was found in both wing fuel tanks and the fuel selector was in the left tank position.  Throttle and mixture control continuity was established from the cockpit to the engine.  The propeller remained attached to the crankshaft.  The top spark plugs were removed and normal operating signatures were noted.  The crankshaft was rotated through about 30 degrees and all pistons traveled appropriately.  The left magneto was removed and rotated by hand verifying spark when activated by impulse coupling.  Flight control continuity was verified.

The wreckage was recovered from the accident site and transported to Discount Salvage, Deer Park, Washington.  With the engine still installed in the airframe, the engine was prepared for an engine run.  A new propeller was installed as the accident propeller blades were bent, and an auxiliary fuel source was applied.  The engine was then started and ran smoothly at idle power.  The rpm was then increased to approximately 1500 rpm on two occasions.  The engine ran smoothly and did not hesitate when the throttle was advanced.

Maintenance records indicated that the last annual inspection was accomplished on January 6, 2004.  On June 14, 2004, the engine had been removed for a teardown inspection as a result of a propeller strike.  The pilot reported that the propeller strike had occurred at the same airstrip as the accident.  The engine was reinstalled after the teardown inspection and repair on August 4, 2004.  The pilot reported a total flight time of about four hours had been accumulated since the teardown inspection.

At the time of the accident, the pilot reported a temperature of 88 degrees F.  The nearest weather reporting facility located in Moses Lake, Washington, at the Grant County Airport, positioned 20 nautical miles southwest of the accident site, reported at 0852 an altimeter setting of 29.92" Hg.  Density altitude calculated for the conditions indicated approximately 3,874 feet.

## Aircraft

- Registration: [N4195J](https://openairdocs.org/deregistered/N4195J-2013-08-08), registration cancelled 2013-08-08, S/N 28-22536, built 1966 (OpenAirDocs)
- Reported make and model: Piper PA-28-140
- Registry model: [Piper PA-28-140](https://openairdocs.org/model/piper-pa-28-140) (registry code 7102802) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 28-22536
- Airframe hours: 2668
- Engines: Lycoming O-320-E2A 150 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Dwight E. Kramer
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, January 6, 2004, 20 hours before
- Departed: 63S, Colville, WA
- Destination: Odessa, WA

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 55; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; last flight review August 12, 2003; seat: left; flight hours: 432 total, 416 in this make and model, 432 as pilot in command

## Weather

- Conditions: Visual (VMC), Day
- Wind: 3 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 82 °F, dew point 41 °F
- Altimeter: 29.92 inHg
- Observed at: MWH, 20 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20040814018929A](https://openairdocs.org/incident/20040814018929A), Aug 14, 2004: Piper PA28140, Irby, WA, Substantial damage. (-23) The pilot stated that on the second attempt to land at his private east-west airstrip near Irby, WA he made a decision to go around and the engine did…

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
