MD Helicopters INC 369FF accident near Mesa, Arizona, May 5, 2021
On May 5, 2021 at about 4:00 pm local time, a 2017 MD Helicopters INC 369FF, registered N6068S, was substantially damaged in an accident during approach near Mesa, Arizona (Falcon Fld airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A tail rotor blade strike to an undetermined object while practicing approaches to unimproved terrain.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 5, 2021 · about 4:00 pm local time · cases in 2021
- Place
- Mesa, Arizona · Falcon Fld · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- MD Helicopters INC 369FF, built 2017 · all 369FFs on the register
- Registration
- N6068S · no longer on the register · serial 0268FF
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Simulated/training event during approach defining event
- Collision during takeoff/land during approach
The NTSB's findings
- Personnel issues › Psychological › Attention/monitoring › Monitoring environment › Pilot
- Environmental issues › Physical environment › Object/animal/substance › Debris/dirt/foreign object › Effect on operation
Pilot
- Certificate: airline transport pilot, commercial pilot
- Ratings: instructor: helicopter; instructor: instrument helicopter; instrument: helicopter; rotorcraft: helicopter
- Flight time: 10,188 hours in all; 790 in this make and model; 130 in the last 90 days; 31 in the last 30 days; 8,693 as pilot in command; 5,366 on instruments
- Last flight review: February 15, 2020
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: no injuries
Pilot
- Certificate: foreign licence
- Flight time: 900 hours in all; 7 in the last 90 days; 7 in the last 30 days
- Medical certificate: None
- Seat: rgt
- Injury: no injuries
The aircraft
- Airframe total time: 40.6 hours
- Last inspection: condition inspection, June 23, 2020
- Maximum gross weight: 3,750 lb
- Seats: 4
- Landing gear: fixed
- Engine: Rolls-Royce 250-C30 (turboshaft); 43 hours total
- Operator: MD Helicopters INC
The flight
- A second pilot was aboard
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Temperature: 81°F (27°C), dew point 27°F (-3°C)
- Altimeter: 29.98 inHg
- Observation at 8:54 am from KFFZ
Weather report (METAR): KFFZ 051554Z 00000KT 10SM CLR 27/M03 A2998 RMK AO2 SLP128 T02721028
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
Photographs from the investigation 4 pictures from the NTSB's docket, as the NTSB released them
Photo 1 – Tail Rotor Blade 1
Photo 2 – Tail Rotor Blade 2
Photo 3 – Tail Rotor Blade 3
Photo 4 – Tail Rotor Blade 4The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
2 documents, released by the NTSB on August 3, 2021. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Accident Photographs | PDF, 4 pages · our copy | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N6068S: not on the register today · the record of its deregistration
- Md Helicopters Inc 369 108 registered today · the model family and its accident history
- Engine: Rolls-Royce 250-C30 76 aircraft carry this series today · as the NTSB recorded it
- Falcon Field · nearest airport
- Accidents and incidents in Arizona 2,985 since 1982 · 466 in the last ten years
- Arizona 8,435 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR21LA183.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.