DEN05LA061 · Robinson Helicopter Company R22
Silver State Helicopters Robinson Helicopter Company R22 · Accident: hard landing
From Provo Municipal Airport (PVU) to Provo Municipal Airport (PVU)
Event
- NTSB case
- DEN05LA061
- 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
- Visual Meteorological Cond
Robinson Helicopter Company R22
- Aircraft type
- Robinson R22
- Category
- Helicopter
- 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
- N780SH
- Operator
- Silver State Helicopters
- Onboard fatalities
- Unknown
- Route
- From Provo Municipal Airport (PVU), Provo, UTTo Provo Municipal Airport (PVU), Provo, UT
- 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
- 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
- Dual student › Aircraft control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor and private certificated student pilot had been practicing simulated autorotation maneuvers from an altitude of 800 feet agl. They set up for the third simulated autorotation from an altitude of 700 feet agl, and the instructor advised the student to tighten the turn to compensate for the lower altitude. Approximately 90 degrees into the turn, the instructor noticed that the airspeed was high. The student began the landing flare and the helicopter began to shutter. At that point, the instructor assumed control, but could not arrest the descent rate, nor decrease the airspeed. The instructor applied forward cyclic and the helicopter contacted the runway and bounced approximately 10 feet into the air. The helicopter sustained substantial damage as a result of ground impact.
Probable cause
the student's failure to maintain control of the helicopter. Contributing factors were high airspeed, high rate of descent, the instructor's delay in taking remedial action, and the instructor's inadequate supervision of the flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN05LA061
- Event ID
- 20050311X00297
- Case number
- DEN05LA061
- 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: 6a263f04866784a3758e152188e933cac89664288c7ae678dd252f2a6b78aba9; retrieved 2026-09-22T06:15:34.533Z.