LAX08CA297 · Bellanca 7GCBC
Bellanca 7GCBC · Accident: collision with terrain/object (non-CFIT) while maneuvering
From U42 · Salt Lake City, UT to 36U · Heber City, UT
Event
- NTSB case
- LAX08CA297
- 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
- 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
Bellanca 7GCBC
- Aircraft type
- Bellanca 7
- 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
- N11698
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From U42 · Salt Lake City, UTTo 36U · Heber City, UT
- 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 · low-altitude flying
- Defining eventThe 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
- Collision with terrain/object (non-CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The pilot said that he was flying the airplane about 8,500 feet msl on an eastbound heading. He entered a canyon, and not believing he had sufficient clearance to cross over the ridge, began a 360-degree turn to gain altitude. During the turn the pilot reported feeling the airplane sink; he then attempted to guide the airplane westbound down the canyon and away from terrain. The airplane continued to descend and impacted terrain at the 8,300-foot level. The pilot said that he did not perceive any preimpact mechanical malfunction or failure.
Probable cause
The pilot's selection of an inadequate altitude to enter a box canyon, which resulted in an in-flight collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08CA297
- Event ID
- 20081003X17544
- Case number
- LAX08CA297
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: f4fee3403464ba4dc8831e3ecec7a1347274117a3fbc4afe7f6cfd452220e1de; retrieved 2026-09-15T10:17:42.987Z.