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

February 15, 2003 · Rotorway Exec 162F · N241WC

Westford, MA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 15, 2003
Injury Outcomes
1 injury (1 serious injury)
Location
Westford, MA
Aircraft
Rotorway Exec 162F
Tail Number
N241WC
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
IAD03LA033

The pilot had just made a steep approach to a confined area and was pulling into a full hover, when the helicopter began a rapid rotation to the left. The pilot applied full right pedal, but could not stop the rotation. He did not perform an autorotation from a hover because he was concerned of landing hard, rolling over, and shedding parts that could have possibly hurt his friend, who was standing nearby. Instead, he lifted the helicopter back up and tried to fly to a vacant area. During the ascent, the pilot was able to slow the rotation by reducing power, but was never able to completely stop the rotation. He was not able to perform an autorotation because he had no forward airspeed, so he put the helicopter down into trees. The pilot stated that he had experienced Loss of Tail Rotor Effectiveness (LTE) in the past, but due to the strong head wind, and the sudden rapidness of the rotation, he did not feel that this was an LTE situation. An FAA inspector reported that one of the tail rotor pitch change links was fractured, but did not take possession of the link at that time. The pilot/owner initially agreed to send the pitch change link to the Safety Board to be examined, but later determined that the part had failed during impact, and discarded the wreckage.

NTSB Probable Cause

The inflight loss of control due to the loss of tail rotor effectiveness.

Full Narrative

On February 15, 2003, about 1610 eastern standard time, a homebuilt Rotorway Exec 162F helicopter, N241WC, was substantially damaged when it collided with trees, then terrain while executing a steep approach to a confined area in Westford, Massachusetts. The certificated commercial pilot sustained serious injuries. Visual meteorological conditions prevailed for the flight that departed Hanscom Field (BED), Bedford, Massachusetts, about 1550. No flight plan was filed for the personal flight conducted under 14 CFR Part 91. The pilot stated that he had made a steep approach, and planned to land in his friend's driveway, a confined area. The pilot also noted that he had previously made the same approach and landing on several other occasions. According to the pilot, when the helicopter was just about in a full hover (about 8 feet above the ground), it began a rapid rotation to the left. The pilot applied full right pedal, but could not stop the rotation. He elected not to perform an autorotation from a hover because he was concerned of landing hard, rolling over, and shedding parts that could have possibly hurt his friend, who was standing in the driveway about 50 feet away. Instead, he lifted the helicopter back up and tried to fly to a vacant area. During the ascent, the pilot was able to slow the rotation by reducing power, but was never able to completely stop the rotation. He was not able to perform an autorotation because he had no forward airspeed, so he elected to put the helicopter down into trees. The pilot also stated that just before, and during the rotation to the left, he never heard any unusual noises or felt anything unusual in the anti-torque pedals. There was no warning whatsoever. The pilot's friend stated that he observed the helicopter when it was rotating, and the tail rotor appeared to be working normally. The pilot reported that he had a total of 265 hours in helicopters, of which, 172 hours were in make and model. In the past, he had experienced the onset of Loss of Tail Rotor Effectiveness (LTE), but due to the strong head wind, and the sudden rapidness of the rotation, he did not feel that this was an LTE situation. An FAA inspector performed an examination of the helicopter. According to the inspector, one of the tail rotor pitch change links was fractured, but he could not determine how it failed. The inspector did not take possession of the link at that time. The pilot/owner initially agreed to send the pitch change link to the Safety Board for further examination. However, upon further examination of the link, and without contacting the Safety Board, he determined that the part had failed during impact. The pilot/owner said that the helicopter wreckage had been discarded. Weather reported at Hanscom Field, 10 miles southwest of the accident location, at 1556, included winds from 350 degrees at 11 knots, temperature 12 degrees F, dewpoint -14 degrees F, and barometric pressure of 30.35 inches Hg. The visibility was 10 statute miles, and the sky was clear.

Flight

Event TypeAccident
Event Time16:10 EST
Nearest Airport0nm
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireGrd
Aircraft ExplosionGrd

Aircraft

AircraftRotorway Exec 162F
Tail NumberN241WC
Aircraft CategoryHeli
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-320 · Reciprocating · 150
Seats2

People & Injuries

Injury Summary1 injury (1 serious injury)
Fatal0
Serious1
Minor0
Uninjured0
Total1
Crew 1Age 62 · Second Class · Serious

Conditions

ConditionsVMC
LightDaylight
Wind350° @ 11 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point12 C / -15 C
Altimeter30.35 inHg
Observation Time20:56
Weather SourceWFAC

Appendix: Source Data