DEN08FA003 · Raytheon Aircraft Company C90A
Scenic Aviation Raytheon Aircraft Company C90A · Accident: in flight collision with terrain/water en route
From Chinle Municipal Airport (E91) to San Luis Valley Regional Airport/Bergman Field (ALS)
Event
- NTSB case
- DEN08FA003
- 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
- 3 · 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
- Instrument Meteorological Cond
Raytheon Aircraft Company C90A
- Aircraft type
- Beechcraft 90
- 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
- N590GM
- Operator
- Scenic Aviation
- Onboard fatalities
- Unknown
- Route
- From Chinle Municipal Airport (E91), Chinle, AZTo San Luis Valley Regional Airport/Bergman Field (ALS), Alamosa, 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
- 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
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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
The pilot contacted air traffic control, using the wrong call sign, requesting radar flight following. The airplane initially climbed to 13,500 feet, descended to 11,500 feet, climbed to 13,500 feet, and then began a descent until it impacted terrain at 11,900 feet. One minute prior to impact, the pilot asked the air traffic controller about various minimum altitudes for his route of flight. The controller responded with a minimum instrument altitude of 15,000 to 15,300 feet. A review of the handling of the accident flight showed that the controller was aware of the airplane's position, altitude, general route of flight, and its proximity to terrain. No safety alert was issued to the accident flight. Weather depiction charts, infrared satellite imagery, and local weather observations indicate instrument meteorological conditions prevailed along the route of flight, closest to the accident location. The moon had set at 1539 on the day of the accident. The pilot reported a planned flight altitude of 12,500 feet to his dispatcher. No record of a preflight weather briefing was located. An examination of the airplane, engines, and related systems revealed no anomalies.
Probable cause
The pilot's failure to maintain clearance from mountainous terrain. Contributing to the accident was the pilot's inadequate preflight planning, improper in-flight planning and decision making, the dark night, and the controller's failure to issue a safety alert to the pilot.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN08FA003
- Event ID
- 20071029X01672
- Case number
- DEN08FA003
- 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 2007-10-05.
- API snapshot SHA-256: cc1555580dc6ebc0bd0e9c7bdf0b7d4692ce70d8760e72a052e26c30e40bda93; retrieved 2026-09-20T16:13:51.476Z.