# NTSB IAD03LA033: Rotorway Exec 162F, N241WC, Westford, MA, February 15, 2003

- Type: NTSB accident investigation
- Classification: Accident · Serious injuries · Limited investigation · Final report
- Date: February 15, 2003, 16:10 local (21:10 UTC)
- Place: Westford, MA
- Coordinates: 42.466667, -71.283332
- Nearby events: https://openairdocs.org/map.md?lat=42.4667&lon=-71.2833&mi=10
- Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping)
- Highest injury: Serious injuries
- Injuries: 1 serious
- Status: Completed, report November 25, 2003
- Report: Approved by Office Director
- Parties: FAA/FSDO, MASSACHUSETTS STATE POLICE
- NTSB case key (mKey): 56505
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=IAD03LA033
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/56505/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=56505
- Page: https://openairdocs.org/ntsb/IAD03LA033

## Probable cause

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

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Loss of control - in flight, hover
  - tail rotor effectiveness - reduced, unknown (cause)
- In flight collision with object, emergency descent/landing
  - object - tree(s)

## Analysis

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.

## Factual 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.

## Aircraft

- Registration: [N241WC](https://openairdocs.org/deregistered/N241WC-2005-02-15), registration cancelled 2005-02-15, S/N 6588 (OpenAirDocs)
- Reported make and model: Rotorway Exec 162F
- Registry model: [Copp William H JR ROTORWAY EXEC 162F](https://openairdocs.org/model/copp-william-h-jr-rotorway-exec-162f) (registry code 056118M) (OpenAirDocs)
- Registry engine: [Amateur-built UNKNOWN ENG](https://openairdocs.org/engine/amateur-built-unknown-eng) (registry code 99999) (OpenAirDocs)
- Category: Helicopter, amateur-built
- Serial number: 6588
- Airframe hours: 172
- Engines: Lycoming IO-320 150 horsepower reciprocating
- Damage: Substantial damage
- Fire: On-Ground
- Flight: Personal, Part 91
- Registered owner: William H Copp, JR
- Airworthiness certificate: Special, Experimental (Special)
- Last inspection: Annual, December 1, 2002, 22 hours before
- Departed: BED, Bedford, MA
- Destination: Westford, MA

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 62; injuries: serious; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane, helicopter; medical: class 2, valid medical--w/ waivers/lim; seat: left; flight hours: 3,054 total, 172 in this make and model, 2,979 as pilot in command, 3,026 in the last 90 days, 303 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 350° at 11 knots
- Visibility: 10 statute miles
- Temperature: 12 °F, dew point -15 °F
- Altimeter: 30.35 inHg
- Observed at: BED, 10 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20030215002599A](https://openairdocs.org/incident/20030215002599A), Feb 15, 2003: Amtr ROTORWAY162F, Westford, MA, Destroyed. (-23) Rotorway exec 162F, N241WC crashed in Westford ma at 1610EST 2/15/03. Pilot sole occupant, suffered minor injuries. Aircraft caught fire and is…

## Docket (2 files)

The files NTSB released with the investigation on August 21, 2003, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=56505. 617 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 562 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40385706&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Record of COnversation, FAA Inspector (item 2, .PDF, 54 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40195602&FileExtension=.PDF&FileName=Record%20of%20COnversation,%20FAA%20Inspector-Master.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
