# Accident 19990717009089A: Bolkms BK117B2, Houston, TX, July 17, 1999

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 17, 1999, 12:31 local time
- Place: Houston, TX
- Airport: Life Flt/Refuel Heliport
- Damage: Destroyed
- Phase of flight: Final Approach
- Operating rules: General operating rules (Part 91)
- Operator: GVNA
- Location: 29.5307° N, 95.4497° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=29.5307&lon=-95.4497&mi=10
- Aircraft: N110HH, a cancelled registration (https://openairdocs.org/deregistered/N110HH-2000-05-11) (OpenAirDocs)
- Registry model: Messerschmitt-Bolkow-Blohm BK 117 A-4 (registry code 5626017, https://openairdocs.org/model/messerschmitt-bolkow-blohm-bk-117-a-4) (OpenAirDocs)
- Reported make and model: BOLKMS BK117B2
- Reported engine: LYC LTS101750B1
- People aboard: 3
- Fatal injuries: 3
- Pilot flight hours: 9,233 total, 33 in the last 90 days
- NTSB investigation: [NTSB FTW99FA192](https://openairdocs.org/ntsb/FTW99FA192) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990717009089A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

AIR TAXI, LIFEFLIGHT CRASHED WITH THREE FATALITIES (OTHER CIRCUMSTANCES ARE UNKNOWN) NEAR FRESNO, TX. (.19)ON JULY 17, 1999, AT 1231 CENTRAL DAYLIGHT TIME, A MESSERSCHMITT-BOLKOW-BLOHM BK-117-B2 HELICOPTER, N110HH, OPERATED AS LIFE FLIGHT ONE, WAS DESTROYED WHEN IT COLLIDED WITH TERRAIN NEAR FRESNO, TEXAS.  THE HELICOPTER WAS REGISTERED TO AND OPERATED BY HERMANN MEMORIAL HOSPITAL SYSTEM, HOUSTON, TEXAS.  THE AIRLINE TRANSPORT PILOT AND TWO CREWMEMBERS RECEIVED FATAL INJURIES.  VISUAL METEOROLOGICAL CONDITIONS PREVAILED FOR THE 14 CFR PART 91 REPOSITIONING FLIGHT.  THE LOCAL FLIGHT ORIGINATED FROM THE HERMANN MEMORIAL HOSPITAL, HOUSTON, TEXAS, AT 1226.  ACCORDING TO WITNESSES, THE HELICOPTER WAS TRAVELING SOUTHBOUND, PARALLEL TO AND 100 YARDS WEST OF FM 521.  THE HELICOPTER APPEARED TO INITIATE A LEFT TURN, AND PIECES "SHOT OUT" FROM THE TOP OF THE HELICOPTER.  THE HELICOPTER DESCENDED IN A NOSE LOW ATTITUDE BEHIND TREES AND IMPACTED TERRAIN.  THE MAIN WRECKAGE WAS LOCATED AT LATITUDE 29 DEGREES 34.220 MINUTES NORTH AND LONGITUDE 95 DEGREES 26.272 MINUTES WEST.  THE FUSELAGE CAME TO REST UPRIGHT ON A MEASURED MAGNETIC HEADING OF 180 DEGREES.  THE MAIN TRANSMISSION AND MAIN ROTOR   HUB REMAINED ATTACHED TO EACH OTHER, BUT SEPARATED FROM THE AIRFRAME. THE TRANSMISSION AND MAIN ROTOR HUB CAME TO REST APPROXIMATELY 20 FEET FROM THE AIRFRAME. ALL FOUR MAIN ROTOR BLADES SEPARATED FROM THE MAIN ROTOR HUB.  ONE MAIN ROTOR BLADE (RED) WAS LOCATED .13 MILES WEST OF THE MAIN WRECKAGE, AND A SECOND BLADE (GREEN) WAS .13 MILES EAST OF THE MAIN WRECKAGE.  THE TWO OTHER MAIN ROTOR BLADES (BLUE AND YELLOW) WERE LOCATED NORTH OF THE MAIN WRECKAGE AT .20 AND .27 MILES, RESPECTIVELY.                               (-23) ACCORDING TO SEVERAL EYEWITNESSES, THE HELICOPTER APPEARED TO INITIATE A LEFT TURN WHEN PIECES "SHOT OUT" FROM THE TOP OF THE HELICOPTER AND THE HELICOPTER THEN DESCENDED AND IMPACTED TERRAIN. EVIDENCE AT THE SCENE SHOWED THE TT STRAP (P/N 2604067) FAILED IN FLIGHT AND ALL FOUR MAIN ROTOR BLADES SEPARATED FROM THE ROTOR HUB BEFORE TERRAIN IMPACT. THE RED ROTOR BLADE WAS LOCATED 686 FEET WEST (260 DEGREES) OF THE MAIN WRECKAGE; THE GREEN ROTOR BLADE WAS 293 FEET EAST (057 DEGREES); THE BLUE ROTOR BLADE WAS 329 FEET NORTH (330 DEGREES); AND THE YELLOW ROTOR BLADES WAS 525 FEET NORTH (340 DEGREES). THE BLADE MOUNTING FORK, PITCH HORN, AND DAMAGED TT STRAP WERE     FOUND STILL ATTACHED TO THE YELLOW BLADE. THE MAIN GEAR BOX (TRANSMISSION) AND ROTOR HUB WERE FOUND 20 FEET FROM THE FUSELAGE AND WERE NOT ATTACHED TO THE FUSELAGE WHEN THE FUSELAGE IMPACTED TERRAIN IN A PARTIALLY INVERTED NOSE LOW ATTITUDE. (.4) THE HELICOPTER WAS MAKING A VFR APPROACH TO A FUELING SITE WHEN WITNESSES OBSERVED COMPONENTS OF THE MAIN ROTOR SYSTEM SEPARATE FROM THE HELICOPTER. SUBSEQUENTLY, THE HELICOPTER ENTERED AN UNCONTROLLABLE DESCENT AND IMPACTED THE GROUND. EXAMINATION OF THE HELICOPTER REVEALED THAT ONE OF THE FOUR MAIN ROTOR BLADES SEPARATED DUE TO THE FAILURE OF THE TENSION-TORSION STRAP (T-T STRAP), WHICH SECURED THE BLADE TO THE MAIN ROTOR HEAD. EXAMINATION OF THE FAILED T-T STRAP REVEALED THAT THE POLYURETHANE PROTECTIVE COATING HAD DEBONDED FROM A PORTION OF THE STRAP ALLOWING CORROSIVE AGENTS, INCLUDING CARBON, SULPHUR, AND CHLORINE INTO THE STRAP. THE STRAP SEPARATED AS A RESULT OF FATIGUE CRACKING OF THE WIRES MAKING UP THE STRAP. THE FATIGUE CRACKING EMANATED FROM CORROSION PITS AND DEPOSITS THAT WERE INTRODUCED TO THE STRAP WHEN THE POLYURETHANE PROTECTIVE COATING DEBONDED. THE T-T STRAP HAD                                                          ACCUMULATED A TOTAL OF 7,815.3 FLIGHT HOURS AND 35,971 FLIGHTS AT THE TIME THAT IT FAILED. IT HAD BEEN IN SERVICE SINCE THE HELICOPTER WAS MANUFACTURED IN 1987. FOLLOWING THE ACCIDENT, A LIFE LIMIT OF 120 MONTHS OR 25,000 FLIGHTS (WHICHEVER COMES FIRST) WAS ESTABLISHED FOR THE T-T STRAPS.

## The NTSB's investigation of this event (1)

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.

- [NTSB FTW99FA192](https://openairdocs.org/ntsb/FTW99FA192), Jul 17, 1999: MBB BK-117-B2 (N110HH), Fresno, TX, destroyed, 3 fatal. Probable cause: the loss of control during approach due to the corrosion of the T-T strap which resulted in fatigue cracking and subsequent separation of the strap and main rotor blade from the helicopter.

## Other reports on N110HH (1)

Matched to the same aircraft by N-number and date.

- [Incident 19910608032959I](https://openairdocs.org/incident/19910608032959I), Jun 8, 1991: Bolkms BK117A4 (N110HH), Houston, TX. Engine failed in flight. Landed in a field. Investigation revealed a failure of an engine bearing.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

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