DEN08LA038 · Rotorway Exec 162-F
Rotorway Exec 162-F · Accident: airframe, component or system failure on approach
From New Century AirCenter Airport (IXD) to New Century AirCenter Airport (IXD)
Event
- NTSB case
- DEN08LA038
- 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
Rotorway Exec 162-F
- Aircraft type
- Rotorway EXEC 162
- 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
- N46110
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From New Century AirCenter Airport (IXD), New Century, KSTo New Century AirCenter Airport (IXD), New Century, KS
- 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
- Approach · VFR pattern final
- 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
- Airframe, component or system failure
- 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
- Rotor system, tail rotor blade spar › Failure, total
- Rotor system, tail rotor blade spar › Fatigue
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was doing hovering maneuvers at the end of the runway. He was cleared for a left pattern to return to the end of the runway. On final approach he felt a "moderate vibration" in the tail rotor, and elected to autorotate to a farm field adjacent to airport property rather than try to clear surrounding trees and fences. The helicopter landed hard, flexing the landing gear. The pilot later reported a spar in one of the tail rotor blades had failed due to metal fatigue.
Probable cause
While on approach the tail rotor spar failed due to metal fatigue .
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN08LA038
- Event ID
- 20071204X01894
- Case number
- DEN08LA038
- 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: 2661a28e59f048f361e88371cf7f4e3221d4dc69c15aabf8c2ddc726343adba8; retrieved 2026-09-22T03:16:46.586Z.