FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN89LA211 · Cessna 182L

1 Sept 1989 · Moab, UT, United States

Ogden Air Service Cessna 182L · Accident: hard landing

From Page Municipal Airport (PGA) to Canyonlands Regional Airport (CNY)

Report a problem

Event

NTSB case
DEN89LA211
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 182L

Aircraft type
Cessna 182
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
N42027
Onboard fatalities
Unknown
Route
From Page Municipal Airport (PGA), Page, AZTo Canyonlands Regional Airport (CNY)
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 › Compensation for wind conditions, inadequate
  • Pilot in command › Flare, not attained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PLT AND HIS WIFE WERE MAKING A X-COUNTRY FLIGHT. RPRTDLY, WHEN HE LANDED, THE WIND WAS VARIABLE FROM 270 TO 300 DEG AT 10 TO 15 KTS WITH GUSTS TO 20 KTS. THE PLT SAID THAT AT TOUCHDOWN, THE PLANE ENCOUNTERED A WIND GUST AND LANDED HARD. HE SAID HE MADE A GO-AROUND AND LANDED ON RWY 3 WITHOUT FURTHER INCIDENT. AFTER LANDING, HE FOUND A WRINKLE IN THE FUSELAGE AND AN A&P MECHANIC DISCOVERED DAMAGE TO THE FIREWALL. DENSITY ALT WAS ABOUT 7500 FT AT THE ARPT.

Probable cause

INADEQUATE COMPENSATION FOR THE WIND CONDITIONS BY THE PILOT, AND HIS FAILURE TO ATTAIN A FLARE. THE UNFAVORABLE (VARIABLE & GUSTY) WIND CONDITION WAS A RELATED FACTOR.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN89LA211
Event ID
20001213X29349
Case number
DEN89LA211
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: a58f32d0f408800db9cb4791ad9b1c4d05d2768068c7a098d90bef5ba4557bd6; retrieved 2026-09-23T07:12:48.623Z.