Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

July 29, 2015 · Airbus AS350-B2 · N6095U

Tucson, AZ

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 29, 2015
Injury Outcomes
1 injury (1 minor injury), 1 uninjured
Location
Tucson, AZ
Aircraft
Airbus AS350-B2 (1993)
Tail Number
N6095U
Operator
Us Department of Homeland Security
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
GAA15CA204

According to the Pilot/Operator Aircraft Accident Report, the operator reported that, the flight instructor(CFI) was demonstrating the flare portion of an autorotation to the pilot-rated student when the aircraft continued through the power recovery point and impacted the runway. However, during the interview with the CFI and the student, both pilots referred to "flare portion" as the quick stop maneuver, which was the maneuver being performed at the time of the accident. Both pilots stated that they hover taxied to the approach end of the runway, stopped over the runway numbers and established a hover between 65-75 feet above ground level. They reported that they hovered over the runway numbers, facing in the direction of the runway heading, and the CFI described the intricacies of the quick stop maneuver. The CFI specified that the maneuver would terminate to a hover, and initiated the quick stop demonstration by accelerating to the airspeed of 65 knots. The CFI reported that as he talked through the maneuver, he lowered the collective and applied aft cyclic. He stated that as the helicopter began to settle, he misperceived the helicopters altitude in relation to the ground and the helicopter skids impacted the ground hard. Both pilots stated that the CFI responded by increasing collective and the helicopter ascended, started moving aft, and the tail boom separated impacting the left side of the fuselage. The student reported that he and the CFI were both on the controls after the first impact. Both pilots recalled lowering the collective in order to set the helicopter down, the helicopter remained in a level pitch attitude, but yawed left and landed on the skids. The helicopter remained on the ground as the left yaw continued, and the engine was shut down. Both pilots reported that the helicopter spun on the skids, in two complete circles while on the ground, before coming to a stop. The tail boom and main rotor system sustained substantial damage. Both pilots reported that there were no pre-impact mechanical malfunctions or anomalies with any portion of the helicopter that would have prevented normal operations.

NTSB Probable Cause

The flight instructor's misperception of the helicopter's altitude in relation to the runway surface during a low altitude maneuver, resulting in ground impact.

Full Narrative

According to the Pilot/Operator Aircraft Accident Report, the operator reported that, the flight instructor(CFI) was demonstrating the flare portion of an autorotation to the pilot-rated student when the aircraft continued through the power recovery point and impacted the runway. However, during the interview with the CFI and the student, both pilots referred to "flare portion" as the quick stop maneuver, which was the maneuver being performed at the time of the accident. Both pilots stated that they hover taxied to the approach end of the runway, stopped over the runway numbers and established a hover between 65-75 feet above ground level. They reported that they hovered over the runway numbers, facing in the direction of the runway heading, and the CFI described the intricacies of the quick stop maneuver. The CFI specified that the maneuver would terminate to a hover, and initiated the quick stop demonstration by accelerating to the airspeed of 65 knots. The CFI reported that as he talked through the maneuver, he lowered the collective and applied aft cyclic. He stated that as the helicopter began to settle, he misperceived the helicopters altitude in relation to the ground and the helicopter skids impacted the ground hard. Both pilots stated that the CFI responded by increasing collective and the helicopter ascended, started moving aft, and the tail boom separated impacting the left side of the fuselage. The student reported that he and the CFI were both on the controls after the first impact. Both pilots recalled lowering the collective in order to set the helicopter down, the helicopter remained in a level pitch attitude, but yawed left and landed on the skids. The helicopter remained on the ground as the left yaw continued, and the engine was shut down. Both pilots reported that the helicopter spun on the skids, in two complete circles while on the ground, before coming to a stop. The tail boom and main rotor system sustained substantial damage. Both pilots reported that there were no pre-impact mechanical malfunctions or anomalies with any portion of the helicopter that would have prevented normal operations.

Flight

Event TypeAccident
Event Time16:45 MST
Nearest AirportRyan Field (0nm WSW)
Runway24R
Runway Length4900 ft
Runway Width75 ft
Flight Plan FiledCvfr
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftAirbus AS350-B2
Tail NumberN6095U
Aircraft CategoryHeli
DamageSubstantial
OperatorUs Department of Homeland Security
Engines1
Engine TypeTurboshaft
Engine DetailsTurbomeca · Arriel/1D1 · Turboshaft · 732
Seats6

People & Injuries

Injury Summary1 injury (1 minor injury), 1 uninjured
Fatal0
Serious0
Minor1
Uninjured1
Total2
Crew 1Age 48 · Second Class · Minor
Crew 2Age 46 · Second Class · None

Conditions

ConditionsVMC
LightDaylight
Wind270° @ 3 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point61 F
Altimeter29.98 inHg
Observation Time23:45
Weather SourceWFAC

Appendix: Source Data