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

Cessna P210N accident near Tonopah, Nevada, December 14, 2003

On December 14, 2003 at about 6:50 pm local time, a Cessna P210N, registered N4674A, was destroyed in an accident near Tonopah, Nevada. It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot's failure to follow approved instrument flight procedures, and his failure to maintain clearance from obstacles/terrain, which resulted in an in-flight collision with terrain. Factors associated with the accident are snow and low clouds.

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

What the record shows

Date
December 14, 2003 · about 6:50 pm local time
Place
Tonopah, Nevada · map
Type
Accident
Injuries
2 people were killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Cessna P210N · all P210Ns on the register
Registration
N4674A · registry record · serial P21000813
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

The private pilot and one passenger departed on a Title 14, CFR Part 91, personal VFR cross-country flight from an airport near the pilot's residence in Tucson, Arizona, to an airport near Florence, Oregon, with a fuel stop in Tonopah, Nevada. Approaching Tonopah, the pilot reported deteriorating weather, and requested a GPS approach to the airport. He was issued a clearance for the GPS Runway 15 approach. No further communications occurred with the accident airplane. Due to mountainous terrain, the approach is not monitored on radar. The airplane was cleared for the approach at 1042. Special weather observation taken at Tonopah at 1024, reported 10 miles visibility, with scattered clouds at 1,900', and broken clouds at 7,000' and 8,000'. A special observation taken at 1042, reported 2 miles visibility in light snow, with few clouds at 2,000', and broken clouds at 2,800'. A special observation taken at 1049, reported 1 mile visibility in light snow and mist, and a vertical visibility (VV) of 1,700'. The METAR observation taken at 1056, reported 1 mile visibility in light snow and mist, with a VV of 1,200'. A special observation taken at 1106, reported three-quarter mile visibility in light snow and mist, with broken clouds at 800', and an overcast at 1,600'. The forecast for the area, valid for the time of arrival included active AIRMET's for IFR conditions, specifically mountains obscured by snow and mist, visibility below 3 miles, and ceilings below 1,000'. The Tonopah GPS Runway 15 instrument approach is a non-precision approach with an MDA of 5820' msl, which is 394' above the airport elevation. The approach is north of Tonopah, with a southerly inbound course, and is bounded by mountain peaks ranging from 7,000' to 9,000'. Initial radar data indicates the airplane started the approach at the appropriate location and altitude, then descended below radar coverage, and did not execute a missed approach. The airplane impacted a rock face north of the airport. During the search, Sheriff's personnel interviewed witnesses who observed the airplane flying low, in and out of cloud bases. The airplane was observed northeast of the airport along a highway proceeding westbound, where it intercepted another highway northbound. The airplane then reversed course south along the highway, and turned southwest along the west side of the San Antonio Mountains. After turning south along the mountains the airplane entered an easterly oriented canyon which terminates at Lime Mountain Peak, elevation 7,102' msl. Prior to reaching Lime Mountain Peak, the airplane turned north into a canyon leading to San Antonio Peak, elevation 7,727' msl. The airplane impacted a steep wall on the south side of San Antonio Peak, about 7,500' msl. An examination of the airplane indicated the flaps were extended 10-20 degrees, the landing gear was in the down position, and the engine was producing power.

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: 3,400 hours in all
  • Last flight review: April 3, 2002
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 2,406 hours
  • Last inspection: annual inspection, October 20, 2003
  • Maximum gross weight: 4,016 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Continental TSIO-520-AF (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: TUS Tucson AZ at 2:00 pm
  • Destination: TPH Tonopah NV
  • Flight plan: IFR

Weather at the time

  • Light: daylight
  • Wind: from 210° at 3 knots
  • Visibility: 1 statute miles
  • Temperature: 32°F (0°C), dew point 28°F (-2°C)
  • Altimeter: 29.87 inHg
  • Observation at 5:49 pm from KTPH, 12 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.