DEN82DA033 · Cessna 210
Ray Martin Painting Cessna 210 · Accident: hard landing
From Gillette, WY to Rapid City, SD
Event
- NTSB case
- DEN82DA033
- 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 210
- Aircraft type
- Cessna 210
- 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
- N5314A
- Operator
- Ray Martin Painting
- Onboard fatalities
- Unknown
- Route
- From Gillette, WYTo Rapid City, SD
- 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 · landing roll
- 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 › Airspeed, misjudged
- Pilot in command › Distance, misjudged
- Pilot in command › Level off, improper
Approximate · Estimated position: the centre of Rapid City, SD, the place the record names. Not the accident site.
NTSB narrative
DURING LANDING, THE NOSEWHEEL BEGAN TO SHIMMY WHILE THE BRAKES WERE BEING APPLIED. THE NOSE GEAR FAILED AT THE END OF THE RUNWAY, AND THE PLANE CONTINUED OFF THE END AND DOWN AN EMBANKMENT, THEN NOSED OVER. THE PILOT STATED IN PART THAT HE TOUCHED DOWN PAST THE NUMBERS SOME 100 FT AND HAD NO LEFT BRAKE. WHEN THE NOSEWHEEL BEGAN TO SHIMMY HE STARTED TO GO-AROUND, BUT THEN THE SHAKING BECAME SO BAD THAT HE ABORTED THE GO-AROUND. A WITNESS STATED THAT HE SAW THE PLANE ON A STEEP FINAL APPROACH, BUT OBSERVED NO FLARE-OUT. HE REPORTED THAT THE PLANE TOUCHED DOWN NEAR MID-FIELD IN A 3 POINT ATTITUDE, BUT DID NOT BOUNCE. THE PASSENGER INDICATED THAT THE PLANE LANDED WITH NO FLAPS ABOUT 1/3 DOWN THE RUNWAY. HE STATED THE TOUCHDOWN WAS SMOOTH AND THE NOSEWHEEL DID NOT SHIMMY UNTIL THE TIRES SQUEALED FROM HEAVY BRAKING. EXAMINATION OF THE BRAKES REVEALED NO PRE-CRASH MALFUNCTIONS. THE NOSEWHEEL SHIMMY DAMPER WAS FOUND BROKEN FROM THE NOSE STRUT WITH EVIDENCE OF GROUND IMPACT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN82DA033
- Event ID
- 20020917X01927
- Case number
- DEN82DA033
- 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: 513bd37b39f16eac9950f3d6b486be13c94a8cc2d338b85cc6a77aaf6f553b76; retrieved 2026-09-24T03:40:26.677Z.