DEN85LA163 · Cessna 152
Cessna 152 · Accident: loss of control in flight while maneuvering
From Alamogordo White Sands Regional Airport (ALM) to an unrecorded destination
Event
- NTSB case
- DEN85LA163
- 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
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
- N47822
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Alamogordo White Sands Regional Airport (ALM), Alamogordo, NMTo 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
- Maneuvering
- 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
- Loss of control in flight
- 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
- 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 › Airspeed, not maintained
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Stall/mush, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT WAS FLYING IN THE VALLEYS OF MOUNTAINOUS TERRAIN. HE ELECTED TO FLY TO THE LEFT AROUND WHAT APPEARED TO BE A SMALL HILL, BUT WAS ACTUALLY PART OF A RIDGE LINE. SUBSEQUENTLY, THE ACFT ENTERED A 'DRAW' & WOULD NOT OUT-CLIMB RISING TERRAIN. THE ACFT BEGAN MUSHING, SO THE PLT LOWERED THE NOSE, SELECTED 10 DEG OF FLAPS & TRIED TO LAND IN A RELATIVELY FLAT AREA. HOWEVER, THE ACFT PITCHED FORWARD & IMPACTED THE GROUND AT A 45 DEG ANGLE WHILE AT A SPEED OF APRX 45 TO 50 KTS. THE ELEVATION OF THE CRASH SITE WAS ABOUT 8500 FT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN85LA163
- Event ID
- 20001214X36757
- Case number
- DEN85LA163
- 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: f0837fa1711e5fa3be637ed2439c58b37d5607be5610e0b07a1719d82313d202; retrieved 2026-09-21T17:15:44.828Z.