DEN07FA071 · Beech A23A
Azusa, LLP Beech A23A · Accident: in flight collision with object while maneuvering
From Tucumcari Municipal Airport (TCC) to Animas Air Park (00C)
Event
- NTSB case
- DEN07FA071
- 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
- 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
Beech A23A
- Aircraft type
- Beechcraft 23
- 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
- N4761J
- Operator
- Azusa, LLP
- Onboard fatalities
- Unknown
- Route
- From Tucumcari Municipal Airport (TCC), Tucumcari, NMTo Animas Air Park (00C), Durango, CO
- 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 · turn to reverse direction
- 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 object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane struck a grove of trees and impacted terrain in a near-vertical attitude, just below a state highway, at the 9,186-foot level. Two witnesses reported seeing a low-flying airplane that was "barely clearing the trees." One of the witnesses said the airplane's wheels were about "20 to 50 feet above the trees" and the airplane banked south. They lost sight of the airplane as he rounded a bend in the road. According to the pilot's flight instructor, the pilot and he had flown this route numerous times. Both the pilot and the instructor were familiar with the terrain and the mountain pass. According to the Albuquerque Sectional Chart, the summit of the pass is approximately 10,000 feet msl. Engine disassembly revealed no discrepancies. Data downloaded from a Garmin GPS (Global Positioning System) MAP 195 recovered from the wreckage revealed the airplane had been cruising between 100 and 125 mph. According to NTSB's GPS Specialist's factual report, "The airplane began to slow gradually after passing over Rt. 518. This road lies in the center of a broad north-south oriented valley. The airplane had slowed to approximately 74 mph by the time it reached the coordinates of the last recorded GPS tracklog point. The airplane maintained a near straight line course during this time" and was "entering an area of rising terrain. Information concerning aircraft altitude was not available because the GPSMAP 195 does not calculate and record GPS altitude."
Probable cause
The pilot's failure to maintain a safe altitude and clearance, and his improper inflight planning/decision to postpone initiating a climbing turn to avoid obstructions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN07FA071
- Event ID
- 20070322X00316
- Case number
- DEN07FA071
- 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: 685c00c4fbfd4b05213085264a1133d0e0dac8c6926ffebee128219935e9ee41; retrieved 2026-09-20T16:47:55.128Z.