MIA94LA002 · Schweizer 269C
Miami Helicopter Service Schweizer 269C · Accident: loss of control on ground/water during landing
From Miami-Opa Locka Executive Airport (OPF) to Miami-Opa Locka Executive Airport (OPF)
Event
- NTSB case
- MIA94LA002
- 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
- 0
- 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
- N95AF
- Operator
- Miami Helicopter Service
- Onboard fatalities
- Unknown
- Route
- From Miami-Opa Locka Executive Airport (OPF)To Miami-Opa Locka Executive Airport (OPF)
- 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
- Loss of control on ground/water
- 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
- Company maintenance personnel › Maintenance, improper
- Landing gear, main gear shock absorbing strut › Improper
- Pilot in command › Remedial action, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE HELICOPTER WAS INVOLVED IN A PREVIOUS ACCIDENT INVOLVING A TAIL ROTOR STRIKE. AS A RESULT, IN PART, THE 4 LANDING GEAR DAMPERS WERE SERVICED. THE HELICOPTER WAS REPAIRED, INSPECTED, AND SIGNED OFF FOR RETURN TO SERVICE. TESTS OF THE MAIN ROTOR TRACK AND BALANCE WERE PERFORMED WITH NO DISCREPANCIES NOTED. THE PILOT REPORTED THAT AS HE LANDED FROM A HOVER, THE HELICOPTER BEGAN TO OSCILLATE FORE AND AFT (APPARENT GROUND RESONANCE). AT THE TIME, FULL POWER WAS APPLIED AND THE COLLECTIVE CONTROL WAS DOWN. REPORTEDLY, THE PILOT DID NOT RAISE THE COLLECTIVE. SUBSEQUENTLY, THE LEFT SKID FAILED, AND THE HELICOPTER ROLLED ONTO ITS LEFT SIDE. THREE OF THE 4 LANDING GEAR DAMPERS WERE DETERMINED TO BE IMPROPERLY SERVICED. THE MAIN ROTOR BLADE DAMPERS WERE TESTED AND WERE FOUND TO BE FREE OF PREIMPACT FAILURE OR MALFUNCTION.
Probable cause
IMPROPER SERVICING OF THREE OF THE FOUR MAIN LANDING GEAR DAMPERS BY COMPANY MAINTENANCE PERSONNEL, AND INNADEQUATE REMEDIAL ACTION BY THE PILOT AS GROUND RESONANCE BEGAN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA94LA002
- Event ID
- 20001211X13612
- Case number
- MIA94LA002
- 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. 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: d5c8669bac36e723ca9ca8abb98a95b2131fe4b8c47d0899dde143c43323c881; retrieved 2026-09-23T01:33:08.188Z.