DEN85LA080 · Cessna 337
Cessna 337 · Accident: hard landing
From Albuquerque International Sunport (ABQ) to an unrecorded destination
Event
- NTSB case
- DEN85LA080
- 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 337
- Aircraft type
- Cessna 337
- 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
- N6381F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Albuquerque International Sunport (ABQ), Albuquerque, 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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
- Pilot in command › Checklist, not followed
- Pilot in command › Gear extension, not performed
- Pilot in command › Planned approach, conflicting
- Pilot in command › Procedures/directives, poor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT LANDED GEAR UP DURING A PRACTICE OF TOUCH AND GO LANDINGS. THE PRIVATE PLT CHANGED HIS CHOICE OF RWYS DURING THE APPROACH. IN A POST ACCIDENT INTERVIEW HE STATED THAT HE RAISED THE LNDG GEAR & FORGOT TO RE-EXTEND IT AFTER WSTABLISHING A NEW APPROACH PATTERN FOR THE NEXT LNDG ON RWY 03. THE PREVIOUS LNDGS WERE ON RWY 21. THE WIND WAS REPORTED AS FROM 360 DEGS AT 05 KTS WITH GUSTS TO 10 KTS. THE PLT REPORTED ON HIS WRITTEN FORM THAT THERE WAS 'NOT MUCH WIND AND NO TRAFFIC'. HIS RECOMMENDATION--'NEVER FAIL TO DO A GUMP CHECK BEFORE LANDING'. THIS ACCIDENT OCCURRED AT AN UNCONTROLLED (UNMANNED/NON-EXISTANT TWR) ARPT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN85LA080
- Event ID
- 20001214X35682
- Case number
- DEN85LA080
- 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: aba2a3f5588f400a73acdaa1da416f5235262507c63811d73232f3bebc2d9014; retrieved 2026-09-23T18:34:38.853Z.