FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX02FA166 · SOCATA TB-21

16 May 2002 · New River, AZ, United States

The New Avex SOCATA TB-21 · Accident: in flight collision with terrain/water en route

From Sedona Airport (SEZ) to Phoenix Deer Valley Airport (DVT)

Report a problem

Event

NTSB case
LAX02FA166
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
Visual Meteorological Cond

SOCATA TB-21

Aircraft type
Socata TB-21
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
N328CG
Operator
The New Avex
Onboard fatalities
Unknown
Route
From Sedona Airport (SEZ), Sedona, AZTo Phoenix Deer Valley Airport (DVT), Phoenix, AZ
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
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 › Altitude/clearance, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

During a sales demonstration flight, the pilot descended into the upsloping face of mountainous terrain about 17 nm north of the destination airport. The accident occurred under dark, nighttime, visual meteorological conditions, and after about a 22-minute flight. Illumination of the moon's visible disk was 19 percent. No roads or ground structures were in the vicinity to provide ground reference or to illuminate the accident area terrain. The direct course between the departure and destination airports (71 nm apart) was 180 degrees magnetic. Recorded radar data indicated that during the last 3 minutes of flight, the airplane's average ground track was 176 degrees, and its average ground speed was 168 knots. The radar ground track ended near the centerline of the direct course between the departure and destination airports, and about 1/4-mile north of the initial point of impact (IPI). The wreckage distribution path was 640 feet long on a magnetic bearing of 177 degrees. An examination of the impact ground scars disclosed that the airplane was in controlled flight in a shallow descent when it collided with the terrain. Review of the radar derived accident airplane's flight track in conjunction with the associated underlying terrain and the ambient lighting conditions revealed that the terrain would have been, at best, marginally visible to the pilot. Initially during the descent, the lights of the greater Phoenix area would have been visible to the pilot in the distance, but the area would have disappeared from the pilot's view seconds before impact. The airplane was equipped with an autopilot, a KLN 94 global positioning satellite receiver, and a KMD 550 multifunction color display that, if operated in the topographic mode, had the capability to display terrain elevation information. During the wreckage examination of the airframe's structure and the engine, no evidence of any preimpact failures or malfunctions was found. The avionics components were found too impact-damaged to provide data. Accordingly, the investigation was unable to ascertain if the pilot was using the multifunction display to receive topographic data while descending toward the destination airport. The KLN 94 and the KMD 550 Pilot's Guides state: "CAUTION NEVER USE THE TOPOGRAPHIC ELEVATION DISPLAYED ON THIS EQUIPMENT AS YOUR SOLE REFERENCE FOR TERRAIN AVOIDANCE."

Probable cause

the pilot's failure to maintain an adequate terrain clearance altitude during a cruise descent that resulted in controlled flight into terrain (CFIT). Factors in the accident were the rising mountainous terrain, the dark nighttime lighting condition, and the pilot's loss of situational awareness regarding terrain proximity.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX02FA166
Event ID
20020531X00794
Case number
LAX02FA166
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2002-05-17.
  • API snapshot SHA-256: 04a11ff941548a611049a7851a53ea81f54437ac0ddb0d85c8f16ba1adb8a1a6; retrieved 2026-09-20T20:01:30.709Z.