ANC04FA015 · Cessna P210N
Cessna P210N · Accident: in flight encounter with weather while maneuvering
From Tucson International Airport (TUS) to Tonopah Airport (TPH)
Event
- NTSB case
- ANC04FA015
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 2 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Cessna P210N
- Aircraft type
- Cessna 210
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N4674A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tucson International Airport (TUS), Tucson, AZTo Tonopah Airport (TPH), Tonopah, NV
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- In flight encounter with weather
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Clearance, not maintained
- Pilot in command › IFR procedure, not followed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC04FA015
- Event ID
- 20031219X02064
- Case number
- ANC04FA015
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: b5ac46f87ff79b9998b929ffb219a498bb2fd6b173aa9c39ec742cf705b8f478; retrieved 2026-09-20T18:43:09.079Z.