FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR26FA074 · MD Helicopters LLC 369FF

2 Jan 2026 · Superior, AZ, United States

FB Helicopter MD Helicopters LLC 369FF · Accident: collision with terrain/object (non-CFIT) while maneuvering

From Pegasus Airpark (5AZ3) to an unrecorded destination

Report a problem

Event

NTSB case
WPR26FA074
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
Ongoing
API-reported fatalities
4 · 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

MD Helicopters LLC 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
N3502P
Onboard fatalities
Unknown
Route
From Pegasus Airpark (5AZ3), Queen Creek, AZTo not recorded
Aircraft age
About 3 years (built 2023)
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
Maneuvering · low-altitude flying
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
Collision with terrain/object (non-CFIT)
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

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

On January 2, 2026, at about 1100 mountain standard time, an MD Helicopters MD369FF helicopter, N3502P, was substantially damaged when it impacted a highline/slackline near Superior, Arizona. The pilot and three passengers were fatally injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Slacklining is a sport where a participant balances on a 1 to 3 inch wide piece of webbing made from synthetic fiber that is suspended between two fixed points. A subset of the sport, called highlining, entails rigging the slackline at higher altitudes above terrain, and often involves longer slacklines. Typically, a highline/slackline consists of a mainline that the participant balances on, and a backup line that the participant connects their safety harness to. The mainline is tensioned between two anchors, and the backup line is loosely attached to the mainline with intermittent connectors. According to a witness, on or around December 26, 2025, he and a group of friends traveled to the area near the accident site, which consisted of a valley with terrain elevations that ranged between 2,600-3,500 ft mean sea level (msl). Using two anchors spaced on bluffs about 0.74 mile apart, they raised a signalization line that carried five windsocks and about ten LED lights. After the signalization line was raised, they used additional nylon lines to draw the mainline and backup lines between the anchors. (See Figure 1.) The lines were oriented in a generally north/south direction and were estimated to be about 600 ft above the ground at their highest point.

Figure 1: The series of lines between the anchors, as viewed from the northern bluff (photo courtesy of witnesses). On or about December 30, 2025, high winds and rain were predicted near the accident site, and the slackliners chose to lower the mainline and backup line. On the morning of the accident, the weather had improved, and the slackliners began to draw the mainline and backup line from the northern anchor toward the southern anchor. According to one of the slackliners, who was standing near the southern anchor point, the mainline and backup line had been drawn partway between the anchors when he heard the helicopter approach. The witness turned to the south and saw the helicopter flying at about eye level in an easterly direction. The helicopter briefly disappeared behind nearby terrain, and when it reappeared in the witness’s line of sight, it was flying toward the set of lines suspended between the anchors. The witness reported that the helicopter impacted the lines and appeared to slow or even reverse direction. The helicopter pitched nose up and yawed to the right, after which its tailboom separated. The fuselage became inverted, and the tailboom and fuselage subsequently impacted terrain about 150 and 350 ft from the lines. (See Figure 2.)

Figure 2: The helicopter fuselage. The northern bluff, signalization line, and sections of the highline/slackline are visible in the background. According to first responders, about an hour after the accident, a second helicopter flying a similar flight path flew about 10 ft under the signalization line, which had remained suspended after the accident along with portions of the highline/slackline webbing. Examination of the helicopter revealed material consistent in appearance to highline/slackline webbing imbedded in the upper part of the vertical stabilizer. (See Figure 3.) The lower ends of the horizontal stabilizer end caps were sheared off, and striations similar to the webbing weave pattern were visible on the paint on the vertical and horizontal stabilizers. Additional striations were found on two of the main rotor blades. The helicopter was equipped with a wire strike protection system that consisted of cutters on the top and bottom of the forward fuselage. The cutting surfaces did not show any striations or disturbed paint.

Figure 3: Highline/slackline webbing imbedded in the vertical stabilizer. On December 21, 2025, a Notice to Airmen (NOTAM) was filed by a friend of the slackliners that showed the presence of a “tight rope” about 3 nautical miles south of Superior Municipal Airport (E81), Superior, Arizona. The NOTAM was active between December 26, 2025, and January 6, 2026. The wreckage and sections of the highline/slackline were retained for further examination.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record WPR26FA074
Event ID
20260102202237
Case number
WPR26FA074
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. 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: 845af77c51958f996a2abf9af2134a53caaf3ed8850babfc7251d00257903526; retrieved 2026-09-15T09:12:17.391Z.