FTW97LA297 · Beech F33A
Beech F33A · Accident: in flight collision with terrain/water en route
From Grand Junction Regional Airport (GJT) to Angel Fire Airport (AXX)
Event
- NTSB case
- FTW97LA297
- 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
- 0 · 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 F33A
- 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
- N179DD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Grand Junction Regional Airport (GJT), Grand Junction, COTo Angel Fire Airport (AXX), Angel Fire, 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 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 · climb to cruise
- 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, inadequate
- Pilot in command › Altitude/clearance, misjudged
- Pilot in command › Low altitude flight/maneuver, intentional
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said he was using a WAC (1:1,000,000) chart instead of a sectional (1:500,000) chart for navigation, and thought he was at a safe altitude for the surrounding terrain. As he approached a saddle on a mountain ridge near the Continental Divide (which he thought was 11,500 feet MSL), he realized he was well below the summit. Surrounding terrain prevented him from turning around, so he applied full power in an attempt to climb above the summit. The airplane struck a rock ledge, skidded, and came to rest inverted against an embankment at the 12,200 foot level.
Probable cause
The pilot's intentional low altitude flight over mountainous terrain, inadequate altitude to clear surrounding obstacles, and his misjudging vertical clearance. A factor was the pilot's use of an inappropriate chart for navigation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW97LA297
- Event ID
- 20001208X08616
- Case number
- FTW97LA297
- 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: 0303e4de6c10d00ecf42b93d40a455cae11c41dd32be6cccadac0a54f2f06245; retrieved 2026-09-21T11:55:56.491Z.