FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN05LA023 · Cessna 152

14 Nov 2004 · Lyons, CO, United States

Air West Flight Center Cessna 152 · Accident: in flight encounter with weather en route

From 2V2 · Longmont, CO to an unrecorded destination

Report a problem

Event

NTSB case
DEN05LA023
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
Instrument Meteorological Cond

Cessna 152

Aircraft type
Cessna 152
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
N48943
Onboard fatalities
Unknown
Route
From 2V2 · Longmont, COTo not recorded
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 encounter with weather
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); 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 › Clearance, not maintained
  • Pilot in command › In-flight planning/decision, inadequate
  • Pilot in command › VFR flight into imc, intentional

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

While descending through a layer of clouds, the airplane impacted trees and came to rest entangled with trees. According to the pilot and passenger, after performing climbs, descents, and turning maneuvers above a cloud layer, the pilot descended the airplane through the clouds. During the descent through the cloud layer, the airplane impacted trees.

Probable cause

the pilot's inadequate in-flight planning/decision by his intentional VFR flight into IMC, and his failure to maintain obstacle clearance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN05LA023
Event ID
20041116X01819
Case number
DEN05LA023
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: bde95a154819c412f4baf7777f9eb45599fe1c4513c7dc5c11b92cb8effdddfa; retrieved 2026-09-22T06:31:03.317Z.