The U.S. aircraft register, updated daily
Accidents · NTSB SEA97LA193 · Final report

Cessna TU206G accident near Edwall, Washington, August 18, 1997

On August 18, 1997 at about 8:00 pm local time, a Cessna TU206G, registered N6620Z, was substantially damaged in an accident near Edwall, Washington. It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A fatigue failure of the engine crankshaft. Factors contributing to the accident were the rolling terrain, and the fence.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 18, 1997 · about 8:00 pm local time
Place
Edwall, Washington · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna TU206G · all TU206Gs on the register
Registration
N6620Z · no longer on the register · serial U20606347
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The private pilot stated that during climb, about 10 minutes after takeoff, he felt a strong vibration in the engine, followed by an abrupt engine stoppage a few seconds later. During the subsequent forced landing onto rolling terrain that was surrounded by obstructions, the airplane struck a fence post, hit a ditch, and flipped over. An examination of the engine revealed that the crankshaft had fractured. The fracture was the result of fatigue cracking that initiated at the surface of the aft radius of the no. 2 main bearing journal. Heavy rubbing damage in the aft radius indicated that the bearing shifted aft and scored the radius resulting in fatigue initiation at the surface. A visual inspection of the crankcase mating surfaces revealed fretting, indicating that there was relative motion between the two crankcase halves. No evidence of heat distress or lack of lubrication was found. The engine, a Continental TSIO-520, had received a 'top' overhaul about 45 operating hours before the accident.

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

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 107 hours in all; 39 in this make and model
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 2,138 hours
  • Last inspection: annual inspection, July 6, 1997; 41 hours since
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: fixed
  • Engine: Continental TSIO-520M (piston); 0 hours total

The flight

  • Departed from: SFF Spokane WA at 7:50 pm
  • Destination: MWH Moses Lake WA
  • Flight plan: none
  • Runway 0
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 160° at 15 knots
  • Visibility: 70 statute miles
  • Sky: clear
  • Temperature: 84°F (29°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Crew2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.