CEN10CA183 · Schweizer 269C
Aerial Resources Schweizer 269C · Accident: hard landing
From Rocky Mountain Metropolitan Airport (KBJC) to Rocky Mountain Metropolitan Airport (KBJC)
Event
- NTSB case
- CEN10CA183
- 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
Schweizer 269C
- Aircraft type
- Schweizer 269
- 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
- N67TK
- Operator
- Aerial Resources
- Onboard fatalities
- Unknown
- Route
- From Rocky Mountain Metropolitan Airport (KBJC), Broomfield, COTo Rocky Mountain Metropolitan Airport (KBJC), Broomfield, CO
- 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
- Defining eventThe 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The helicopter flight instructor and private pilot were conducting an approach to a pinnacle landing pad. Two previous passes were made and both pilots estimated winds to be from the northeast at 8 knots. While approaching the landing pad from the southwest, the flight instructor noticed that the helicopter's rpms were slightly low and he reminded the private pilot to increase power until the rpms were in the green arc of the rpm gauge. The private pilot did not increase power sufficiently enough to place the rotor rpm in the green arc and the helicopter began to descend rapidly. The flight instructor took control of the helicopter, increased power, and attempted to reverse course and travel downhill. The helicopter landed hard, bounced, and rolled approximately 1 1/4 times before coming to rest on its right side and sustaining substantial damage to its fuselage and tail boom. An examination of the airframe by a Federal Aviation Administration inspector did not reveal any preimpact anomalies. Additionally, neither pilot reported a malfunction of the airframe or engine.
Probable cause
The flight instructor's delayed remedial actions to regain rotor rpm, resulting in a rapid descent and hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA183
- Event ID
- 20100404X13606
- Case number
- CEN10CA183
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 4e73d8057d6efac30e2d997caf26c729b882ab853ea08a46b3c5cdd70ad3e47f; retrieved 2026-09-15T13:48:47.048Z.