FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Air Transport Cessna 421C accident

3 Dec 2002 · Tajique, NM, United States

Cessna 421C · Accident: in flight collision with terrain/water en route

From Alamogordo White Sands Regional Airport (ALM) to Albuquerque International Sunport (ABQ)

Report a problem

Event

NTSB case
FTW03FA055
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
1 · 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
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 421C

Aircraft type
Cessna 421
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
N3855C
Onboard fatalities
Unknown
Route
From Alamogordo White Sands Regional Airport (ALM), Alamogordo, NMTo Albuquerque International Sunport (ABQ), Albuquerque, NM
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 135: Air Taxi & Commuter
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
En route · descent
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 collision with terrain/water
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

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Prior to departing on the first leg of the flight, the dispatcher advised the pilot that he needed him to check the weather. After advising the pilot that he would be flying an additional leg, the dispatcher again advised the pilot that he needed him to check the weather, which the pilot did, as observed by the dispatcher. After reaching 14,500 feet at 2028 the pilot contacted Albuquerque Approach Control, advising the controller that he had information "Yankee" and was requesting a lower altitude. The controller instructed the pilot to proceed via his own navigation and to descend at pilot's discretion. The pilot replied "Roger." From 2034 to 2041 the controller made four attempts to contact the pilot, each without success. At 2039 and 2042 the controller asked two other aircraft in the area to try establishing radio communication with the pilot; neither were successful. At 2033:19 the last radar return with altitude information was received from the aircraft, with a reported altitude of 10,200 feet MSL. A primary radar contact, with no transponder or altitude information, was received at 2033:32, 2.2 nautical miles southeast of the accident site, putting it on a straight line between the last radar contact and destination airport. The accident site was located at the 9,012 foot level of a mountain range, 19 nautical miles southeast of the destination airport. Post-accident examination revealed no anomalies with the airframe or engines which would have prevented normal operations. At 1956, the weather observation facility located at the destination airport reported a few clouds at 800 feet, scattered clouds at 2,500 feet, and overcast clouds at 4,200 feet. The remarks section stated rain ended at 35 minutes past the hour, and mountains obscured northeast to southeast. At 2024, the same weather facility reported scattered clouds at 600 feet and overcast clouds at 4,200 feet.

Probable cause

The pilot's failure to maintain terrain clearance. Factors contributing to the accident were the high mountains, mountain obscuration, the dark night condition, and the pilot's improper in-flight planning/decision making.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW03FA055
Event ID
20021212X05597
Case number
FTW03FA055
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2002-12-04.
  • API snapshot SHA-256: 0adaeb7d4df264d4539cfcdccd25084910ffd30c7610f0318eb9da847c4768f5; retrieved 2026-09-18T13:03:38.649Z.