FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN89FA152 · Beech E33

2 Jul 1989 · Angel Fire, NM, United States

Beech E33 · Accident: in flight collision with object during takeoff

From Angel Fire Airport (AXX) to Phoenix Sky Harbor International Airport (PHX)

Report a problem

Event

NTSB case
DEN89FA152
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
0
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 E33

Aircraft type
Beechcraft 33
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
N20CF
Operator
Fitch, Paul S. · private individual
Onboard fatalities
Unknown
Route
From Angel Fire Airport (AXX)To Phoenix Sky Harbor International Airport (PHX), 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
Takeoff
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); Stall/mush
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 › Aborted takeoff, not performed
  • Pilot in command › Airspeed, not obtained
  • Pilot in command › Planning/decision, improper
  • Pilot in command › Rotation, premature

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

NTSB narrative

THE PLT AND 3 PAX BOARDED THE ACFT AT ANGEL FIRE, NM (ELEV 8382 FT MSL) TO RETURN TO PHOENIX, AZ. DENSITY ALT WAS APRX 11,582 FT MSL. THE ACFT, WHICH HAD JUST BEEN SERVICED, HAD 54 GAL OF FUEL ON BOARD AND WAS APRX 30 LBS OVER ITS MAX GROSS WEIGHT LIMIT. THE PLT ELECTED TO TAKE OFF ON RWY 17 (8900 FT X 75 FT, 0.643% UPHILL GRADIENT). HE ROTATED 3 TIMES BEFORE THE ACFT FINALLY LIFTED OFF NEAR THE DEPARTURE END. NUMEROUS WITNESSES OBSERVED THE ACFT FLYING LOW THROUGH THE VALLEY TOWARDS GRADUALLY RISING TERRAIN. IT FINALLY STRUCK TREES AND CRASHED APRX 5 MI FROM THE ARPT AT AN ELEV OF 8813 FT MSL. ONE PAX WAS FATALLY INJURED WHILE ATTEMPTING TO EVACUATE THE BURNING ACFT. PERFORMANCE CHARTS INDICATED THE ACFT WAS CAPABLE OF TAKING OFF UNDER THE PREVAILING CONDITIONS. THE PLT LATER REPORTED THAT TURBULENCE AND DOWNDRAFTS DEGRADED THE ACFT'S CLIMB PERFORMANCE. HE ALSO INDICATED THE ACFT WAS ON THE VERGE OF STALLING THROUGHOUT THE SHORT FLT.

Probable cause

IMPROPER PLANNING/DECISION BY THE PILOT, HIS PREMATURE ROTATION FOR TAKEOFF AND SUBSEQUENT FAILURE TO OBTAIN OR MAINTAIN SUFFICIENT SPEED TO CLIMB, AND HIS FAILURE TO ABORT THE TAKEOFF (WHILE THERE WAS SUFFICIENT RWY REMAINING). CONTRIBUTING FACTORS WERE: THE PILOT ALLOWED THE AIRCRAFT GROSS WEIGHT TO EXCEED THE MAXIMUM LIMIT, HIGH DENSITY ALTITUDE, UPHILL RUNWAY GRADIENT, DOWNDRAFT, TURBULENCE, AND TREES.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN89FA152
Event ID
20001213X28790
Case number
DEN89FA152
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. 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: ee92a4b2449bf91076a373ca8bb4fac64fb0d7f4771c5fb77057cf333078992a; retrieved 2026-09-21T03:15:26.094Z.