FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16LA261 · Schweizer 269C 1

16 Jul 2016 · Calhoun, GA, United States

Schweizer 269C 1 · Accident: ground resonance while standing

From Tom B. David Field (CZL) to Tom B. David Field (CZL)

Report a problem

Event

NTSB case
ERA16LA261
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 1

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
N6148D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tom B. David Field (CZL), Calhoun, GATo Tom B. David Field (CZL), Calhoun, GA
Aircraft age
About 18 years (built 1998)
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
Standing · engine(s) operating
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
Ground resonance
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 systems
  • Personnel issues › Task performance

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

NTSB narrative

The commercial pilot flew with the helicopter's owner earlier that day for a demonstration flight, during which the owner performed several autorotative landings to either touchdown or power recovery. After that flight, the owner exited the helicopter, and a commercial pilot-rated passenger boarded and sat in the left seat of the helicopter. They departed, and, after about 10 to 15 minutes, the pilot landed the helicopter uneventfully on a taxiway. With the engine operating, they discussed a helicopter system. The pilot intended to demonstrate the system that they were discussing, and, while guarding the collective down, he slowly advanced the throttle. As the rpm increased, he reported feeling a shake, then a "boom boom" sound, and noticed a vibration, which he identified from training as ground resonance. He reduced throttle, which was the correct procedure to perform for ground resonance, but the vibration increased. The pilot-rated passenger then advised him to pick the helicopter off the ground and attempted to assist by raising the collective. The throttle was advanced, and, with the main rotor rpm near the green arc, the helicopter began shaking and did not become airborne, although the collective was raised. The main rotor blades contacted the tailboom several times.

The helicopter's latest annual/100-hour inspection was performed about 1 year 2 months before the accident, and the helicopter had been operated about 61 hours since then. The handbook of maintenance instructions for the helicopter specified that the dampers are to be inspected for operation and condition, and for damper extension on airframe, at each 100-hour inspection or every 6 months, whichever occurred first.

Postaccident operational testing of the dampers from the unairworthy helicopter revealed that all failed a load stroke test. Two of the four dampers, which were underserviced, likely would not have passed an on-airframe extension test during the annual/100-hour inspection that was overdue, while one damper, which was slightly underserviced, would likely have passed. The remaining damper was overserviced, but that condition would not have been detected during the on-airframe extension test because there was no test procedure in place to identify that condition. Without the airframe protection provided by the dampers, ground resonance occurred. Further, the Federal Aviation Administration's Helicopter Flying Handbook states that with respect to ground resonance, if the main rotor rpm is low, the only corrective action to stop ground resonance is to close the throttle immediately and fully lower the collective to place the main rotor blades in low pitch. Thus, raising the collective and advancing the throttle likely contributed to the helicopter's damage.

Probable cause

The helicopter owner’s failure to ensure the helicopter’s airworthiness and the inadequate inspection and maintenance of the helicopter's landing gear dampers, which resulted in ground resonance during throttle application. Contributing to the damage of the helicopter were the improper actions of the pilots after encountering ground resonance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16LA261
Event ID
20160719X94831
Case number
ERA16LA261
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: d325ab69add30485056d46891ea4d1bd25f1f0ab7c8af86667a7801b4074f956; retrieved 2026-09-16T03:40:29.952Z.