# NTSB LAX03TA229: Sikorsky S-64E, N6979R, Tucson, AZ, July 8, 2003 - Type: NTSB accident investigation - Classification: Accident · No injuries · Final report - Date: July 7, 2003, 18:34 local (Jul 8, 2003, 01:34 UTC) - Place: Tucson, AZ - Coordinates: 32.099998, -110.933334 - Nearby events: https://openairdocs.org/map.md?lat=32.1000&lon=-110.9333&mi=10 - Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report September 1, 2004 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 57456 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX03TA229 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/57456/pdf - Page: https://openairdocs.org/ntsb/LAX03TA229 ## Probable cause the pilot's failure to maintain tail rotor clearance while hovering resulting in a tail rotor blade strike. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight collision with object, hover - in ground effect - object - tree(s) - clearance - not maintained, pilot in command (cause) - rotor system,tail rotor - blade strike ## Analysis After a series of water drops were conducted on a forest fire, the helicopter's crew refilled the fixed tank with water from a dip tank via a snorkel. The dip tank was located in mountainous terrain and there were two mesquite trees near the tank. During the refilling operation, the tail rotor blades contacted the trees; however, the flight crew was unaware of the strike. The tail rotor blade damage was noticed when ground personnel detected damage to the number one exhaust stack, and the helicopter was inspected further. One of the four tail rotor blades incurred spar damage on the leading edge, approximately 14.5 inches from the tip end. ## Factual narrative On July 7, 2003, at 1834 mountain standard time, a Sikorsky S-64E, N6979R, impacted trees with the tail rotor while hovering near Tucson, Arizona. The U.S. Forest Service was operating the helicopter as a public-use flight under the provisions of 14 CFR Part 133 for firefighting operations. The airline transport pilot and copilot were not injured; the helicopter sustained substantial damage. The flight departed Tucson International Airport (TUS), Tucson, about 1715. Visual meteorological conditions existed during the flight and a company visual flight rules (VFR) flight plan was in effect. In a written statement, the operator reported that the helicopter was equipped with a 2,000 gallon fixed tank with snorkel hover fill capability. After a series of water drops, the crew refilled the tank from a dip tank. The dip tank was located in mountainous terrain and there were two mesquite trees near it. During the refilling operation, the tail rotor made contact with the mesquite trees, but the pilots were unaware of the strike. When the helicopter returned to Tucson, it was refueled. During the refueling operations, damage was discovered to the number one exhaust stack. The helicopter was shutdown and examined. The tail rotor blade damage was discovered and initially thought to be a result of debris from the exhaust stack coming into contact with the tail rotor blades. In a telephone interview with a representative of the operator, he stated that closer inspection of the helicopter revealed that a portion of the exhaust stack was collapsed, but no portions were missing. The pilot reported to him that, when dipping the tank, he flew perpendicular to the road, into the wind with the tail of the helicopter in the trees. A tail rotor blade tip cap and small section of a mesquite tree were found at the dip tank site. A Federal Aviation Admininstration designated repair station inspected three of the tail rotor blades and found spar damage on the leading edge of one blade approximately 14.5 inches from the tip end. The two other blades examined were noted to have minor damage. ## Aircraft - Registration: [N6979R](https://openairdocs.org/aircraft/N6979R), registered now, S/N 64079, built 1968 (OpenAirDocs) - Reported make and model: Sikorsky S-64E - Registry model: [Sikorsky S-64E](https://openairdocs.org/model/sikorsky-s-64e) (registry code 8142604) (OpenAirDocs) - Registry engine: [Pratt & Whitney JFTD12A series](https://openairdocs.org/engine/pratt-whitney-jftd12a-series) (registry code 52047, turbo-shaft) (OpenAirDocs) - Category: Helicopter - Serial number: 64079 - Airframe hours: 12746.9 - Engines: Pratt & Whitney JFTD12A-4A 4500 horsepower turbo shaft; Pratt & Whitney JFTD12A-4A 4500 horsepower turbo shaft - Damage: Substantial damage - Flight: Public aircraft, Part 133 - Registered owner: U.S. Forest Service - Airworthiness certificate: Standard, Transport - Departed: KTUS, Tucson, AZ - Destination: Sabino Helispot, AZ - Flight plan: Company VFR ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 61; injuries: none; commercial, airline transport; airplane ratings: single-engine sea, multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, valid medical--w/ waivers/lim; last flight review May 22, 2002 - Co-pilot; age 63; injuries: none; commercial, airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: helicopter; medical: class 2, valid medical--w/ waivers/lim ## Weather - Conditions: Visual (VMC), Day - Wind: 300° at 13 knots, gusting 24 - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 104 °F, dew point 46 °F - Altimeter: 29.79 inHg - Observed at: TUS, 30 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 20030707016859A](https://openairdocs.org/incident/20030707016859A), Jul 7, 2003: Skrsky S64E, Tucson, AZ, Minor damage. (-23) While firefighting in the Tucson, AZ area the pilot had made the sixth (6th) fueling cycle (ea. "Cycle is approx. 1.5 hrs) and were about to depart when… 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.