WPR21LA183 · MD Helicopters Inc 369FF
MD Helicopters Inc 369FF · Accident: simulated/training event on approach
Event
- NTSB case
- WPR21LA183
- 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
- Event fatalities
- Unknown
- 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
MD Helicopters Inc 369FF
- Aircraft type
- MD Helicopters 369
- 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
- N6068S
- Operator
- MD Helicopters
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 4 years (built 2017)
- 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
- 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
- Simulated/training event
- 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
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that, he performed a preflight inspection with the pilot receiving instruction and did not observe any damage to the tail rotor blades before the accident flight. They subsequently departed to a nearby training area and completed several terrain flight approaches to a sandy wash area using standard approach profiles. After one hour of flight and about 15 approaches they returned to their departure airport. While performing a post-flight inspection, the flight instructor and the pilot both observed substantial damage to the tail rotor blades. According to the flight instructor, at no point during the flight did they feel any unusual vibrations with the helicopter, nor did they observe any debris within the landing area. The flight instructor reported no preaccident mechanical failures or malfunctions with the helicopter that would have precluded normal operation.
Probable cause
A tail rotor blade strike to an undetermined object while practicing approaches to unimproved terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR21LA183
- Event ID
- 20210506103042
- Case number
- WPR21LA183
- 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, coordinates, cause areas. 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: 9314f2155a7fa1ccd921a3535735e97660ed2fbfcb946baad66aebc1c7482c68; retrieved 2026-09-16T14:01:06.106Z.