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

September 6, 2013 · Continental Copters Tomcat MK5A · N9005T

Arlington, MN

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
September 6, 2013
Injury Outcomes
No injuries (1 uninjured)
Location
Arlington, MN
Aircraft
Continental Copters Tomcat MK5A
Tail Number
N9005T
Operator
Scotts Helicopter Services
Injuries
None
Aircraft Damage
Substantial
NTSB Number
CEN13LA537

After taking off, the pilot applied pesticides to a field and proceeded to the next field located about 3 miles away. While en route, the pilot wanted to call his truck driver over the two-way radio. However, the radio connection to his helmet was unplugged, so he reached to plug it in with his right hand while his left hand transferred from the collective to the cyclic. Immediately after he plugged in the radio connection to his helmet, the collective slammed into the full-down position. The pilot then quickly grabbed the collective and raised it up. He noticed that the helicopter was losing altitude, that the main rotor rpm was decreasing, and that the engine rpm and main rotor rpm needles were split. He twisted the throttle control back and forth with no effect and then attempted to autorotate. The helicopter touched down hard, which resulted in substantial damage to the tailboom. Examination of the helicopter did not reveal any mechanical anomalies that would have precluded normal operation. Also, a review of the maintenance logbooks for the helicopter did not show any entries regarding malfunctions with the collective control during previous flights, and the helicopter operated normally during the first flight of the day. The pilot stated that he could have chosen to not unplug his helmet and keep his hand on the collective control at all times, which would have prevented the collective from slamming down while he was connecting his radio cables to his helmet. This model helicopter does not have a friction control mechanism on the collective control, and, if it is not held in place by the pilot, it can move up or down during flight. It is likely that, when the pilot removed his hand from the collective control and was distracted with plugging in his helmet radio connection, the collective moved to the full-down position and that he did not have enough altitude to recover the helicopter.

NTSB Probable Cause

The pilot’s failure to maintain control of the helicopter while maneuvering when he removed his hand from the collective control while plugging in his radio connection to his helmet, which resulted in the collective moving to the full-down position.

Full Narrative

On September 6, 2013, about 0925 central daylight time, a Continental Copters Inc., OH13-H Tomcat agricultural helicopter, N9005T, registered to Scotts Helicopter Service Inc., of LeSueur, Minnesota, sustained substantial damage after it collided with the ground while maneuvering during an aerial application flight. The pilot was not injured. Visual meteorological conditions prevailed in the vicinity and no flight plan was filed. The aerial application flight was being conducted under the provisions of 14 Code of Federal Regulations Part 137. The flight originated from a private location near Gaylord, Minnesota, about 0920. The pilot reported to work on the morning of the accident for a scheduled day of flying after he had the previous day off. His first aerial application flight of the morning was uneventful and the helicopter landed to reload pesticides. The pilot then took off and successfully applied about 75 gallons pesticides to a field and proceeded to the next field located about 3 miles away at 300-400 feet AGL. While enroute the pilot wanted to call his truck driver over the two way radio. The radio connection to his helmet was unplugged, so he reached and plugged it in with his right hand while his left hand transferred from the collective to the cyclic. The pilot estimated that this process took about 5 to 8 seconds. Immediately after he plugged in the radio connection to his helmet, the collective slammed into a full down position and the pilot recalled seeing his black-colored notebook fly around the cabin due to the sudden collective movement. The pilot then quickly grabbed the collective and raised it up. He noticed that the helicopter was losing altitude and the main rotor RPMs were decreasing, with the engine RPM and main rotor RPM needles split. He recalls twisting the throttle control back and forth with no effect and attempted to autorotate. The helicopter touched down hard, sustaining substantial damage to the tailboom. An on site inspection of the accident site and the helicopter was conducted by an FAA inspector. The inspector reported that no mechanical or environmental anomalies were found that could have contributed to the accident. The pilot stated in the recommendation section of NTSB Form 6120, that could have chose to not unplug his helmet and keep his hand on the collective control at all times, which would have prevented the collective from slamming down while he was connecting his radio cables to his helmet. A review of the maintenance log books for the helicopter did not show any entries regarding malfunctions with the collective control during previous flights and the helicopter was operating normally during the first flight of the day. Additionally, this model helicopter does not have a friction control mechanism on the collective control, and if it is not held in place by the pilot, it could move up or down during flight.

Flight

Event TypeAccident
Event Time10:30 CDT
Nearest Airport0nm
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftContinental Copters Tomcat MK5A
Tail NumberN9005T
Aircraft CategoryHeli
DamageSubstantial
OperatorScotts Helicopter Services
Operating RulePart 137
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · VO-435 SERIES · Reciprocating · 260
Seats1

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 27 · Second Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind160° @ 5 kt
Visibility10 sm
CeilingOvercast 9500 ft
Altimeter30.05 inHg
Observation Time12:54
Weather SourcePILO

Appendix: Source Data