FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA03LA181 · Schweizer 269C-1

11 Sept 2003 · Homestead, FL, United States

Helicenter International Academy Schweizer 269C-1 · Accident during landing

From Miami Executive Airport (KTMB) to Miami Homestead General Aviation Airport (X51)

Report a problem

Event

NTSB case
MIA03LA181
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
N6147Q
Onboard fatalities
Unknown
Route
From Miami Executive Airport (KTMB), Miami, FLTo Miami Homestead General Aviation Airport (X51), Homestead, FL
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
Miscellaneous/other
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

  • Other maintenance personnel › Maintenance, 100-hour inspection, inadequate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The certified flight instructor (CFI) stated that after departure the flight proceeded to the Homestead General Airport where he advised the student that the lesson would continue with "running landing" and "running take off" training from the previous day. The flight continued in the traffic pattern for runway 36, and when on short final approach to the runway at 5 feet above ground level, the helicopter was at 25 knots indicated airspeed. The helicopter contacted the runway with the skids parallel to the runway centerline, and the CFI allowed the helicopter to continue sliding. The CFI advised the student that the lesson would conclude with a "running takeoff", and upon lifting off the runway at an indicated airspeed of 35 knots, he noticed a vibration from the main rotor system. He noticed the rpm was decreasing and touched down again on the runway, at which time the helicopter began to "shake violently." He realized the flight had encountered ground resonance, and noticed that there was insufficient main rotor rpm to lift off the ground to stabilize the vibrating rotor blade system. He lowered the collective but felt a force when he attempted to reduce throttle input; he felt the force was the student pilot applying throttle input. At that point he was contacted in the head, lost consciousness, which he regained in the hospital. The student pilot advised a Federal Aviation Administration (FAA) inspector that when the flight was approximately 30 feet above ground level prior to performing a running landing, the CFI took the controls from him. The flight continued and while sliding on the runway, the CFI started screaming and froze on the controls. He (student pilot) then braced for impact. Following recovery of the helicopter, the landing gear and main rotor dampers were removed for further examination at the manufacturer's facility with FAA oversight. Examination of the main rotor blade dampers revealed all three exhibited damage associated from lead lag motions encountered in ground resonance. Examination of the four landing gear dampers which had been installed when the helicopter was manufactured revealed all tested out of limits for charge pressure (low). The helicopter was last inspected in accordance with a 100-Hour inspection on August 11, 2003; the helicopter had accumulated 87.9 hours since the inspection at the time of the accident. Review of the 100-Hour inspection guide revealed the landing gear dampers are required to be inspected for operation and condition, and for damper extension with a full fuel tank. Review of Section 12 of the Basic Handbook of Maintenance Instructions manual indicates the landing gear dampers will experience a decrease in pressure with subsequent use of the helicopter, and they should be extension checked during a 100-Hour inspection, or every six months, whichever occurs first. According to a memorandum from the Director of Flight Training to all flight instructors dated August 25, 2003, with respect to the Dominican Republic Flight Training Program, running landings were prohibited to be demonstrated and practiced until a new order was given.

Probable cause

the inadequate 100-hour inspection of the helicopter by other maintenance personnel who failed to discover that the landing gear dampers had low pressure, which resulted in ground resonance and subsequent substantial damage during a run-on landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03LA181
Event ID
20030917X01552
Case number
MIA03LA181
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: 7d8e0d787cbac23497ee2819bdeda5a4ea63b86af3ec85635129c9c0e87c11a2; retrieved 2026-09-21T19:22:12.909Z.