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

Piper PA-22-108 accident near Custer, South Dakota, September 8, 2000

On September 8, 2000 at about 2:20 pm local time, a Piper PA-22-108, registered N4730Z, was destroyed in an accident near Custer, South Dakota (Custer State Park Airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot not maintaining clearance from the tree. Factors relating to this accident were the pilot's inadequate preflight planning and preparation, the high density altitude, the inadequate rate of climb, the pilot's improper in-flight decision to fly into rising terrain, the rising terrain, the blind canyon, and the tree.

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

What the record shows

Date
September 8, 2000 · about 2:20 pm local time
Place
Custer, South Dakota · Custer State Park Airport · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Piper PA-22-108 · all PA-22-108s on the register
Registration
N4730Z · no longer on the register · serial 22-8276
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

A witness watched the airplane take off on runway 33 (4,000 feet by 50 feet, dry asphalt) at the Custer State Park Airport (3V0). "About halfway down the runway, he got airborne. He then pushed the nose over, as if he was trying to pick up more airspeed." The witness said he keyed his microphone and asked the pilot, "You got trouble there?" The pilot responded, "No, just a little trouble climbing." The witness called the pilot again and said, "Turn into the wind, if you think it will help you out." The witness said that the pilot's response back was something like, "I got my hands full right now. Don't call me back." The witness said he watched the airplane until it went around the edge of a ridge beyond the end of the runway, where he lost sight of it. "A few minutes later, I saw smoke coming over the ridge." Several witnesses at a campground in the park saw the airplane flying westbound through the canyon along the state park road. One witness said the airplane was below the tops of the mountains and trees making up the canyon walls. Another witness saw the airplane bank hard to the left. "While banking the turn, his right wing was way up and his left wing tipped ... close to [the] ground." The witness said the next thing he realized, the airplane had crashed. An examination of the airplane wreckage revealed no anomalies. The temperature and altimeter for the Custer County Municipal Airport, (field elevation 5,602 feet), 11 miles southwest of the accident site, were 60 degrees F and 29.95 inches of Mercury, respectively. 3V0 rests in a valley at a field elevation of 3,980 feet. The terrain rises off the end of runway 33 into a 4,400-foot ridge, 1.4 miles north of the airport. A second 4,800-foot ridge, forming the north side of a canyon, begins 4 miles north of the airport. The canyon runs east to west and is characterized by steep walls and sharp turns. A fire fighter pilot at 3V0 said the winds were out of the west at 20 knots. The fire fighter pilot said that runway 33 slopes uphill, and that the winds coming off the hills to the west present difficulties to airplanes that don't have the power to climb. "We takeoff on 33 and settle over the valley there. If you keep going, you get into rising terrain and then into the canyon. If you can't climb there, it's done." The results of FAA toxicology testing of specimens received from the pilot showed the presence of 0.85 (ug/ml) cyanide in the blood. Normal blood cyanide concentrations are less than 0.15 ug/ml, while lethal concentrations are greater than 3 ug/ml. Entering the "Climb Speeds and Rates vs. Standard Altitude" chart in the airplane's Owner's Handbook with a density altitude of 7,001 feet, provides a rate of climb of approximately 315 feet per minute.

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; instrument: airplane
  • Flight time: 721 hours in all; 10 in the last 90 days; 7 in the last 30 days; 607 as pilot in command
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 2,596 hours
  • Last inspection: annual inspection, November 1, 1999
  • Maximum gross weight: 1,650 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-235-C1B (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: 3V0 at 2:10 pm
  • Flight plan: none
  • Runway 33, 4,000 ft by 50 ft

Weather at the time

  • Light: daylight
  • Wind: from 250° at 7 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 140°F (60°C), dew point 70°F (21°C)
  • Altimeter: 29.00 inHg
  • Observation at 1:53 pm from CUT, 11 miles away

Injuries

FatalSeriousMinorNone
Crew1
Passengers1

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.