# Incident 20060727016579I: Urocop EC135P1, Hollywood, FL, July 27, 2006

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 27, 2006, 08:50 local time
- Place: Hollywood, FL
- Airport: North Perry Airport
- Damage: Minor damage
- Phase of flight: To Running(Helicopter/Vtol Ac)
- Operating rules: Air taxi and commuter (Part 135)
- Operator: RMXA
- Location: 26.0013° N, 80.2407° W: Placed by OpenAirDocs at NORTH PERRY (HWO), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=26.0013&lon=-80.2407&mi=10
- Aircraft: N135KT (not matched to a registry record)
- Reported make and model: UROCOP EC135P1
- Reported engine: PWA PW206B
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 10,800 total, 80 in this make and model, 10 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20060727016579I

## Narrative

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

(-23) ON JULY 27, 2006 N135KT, A EUROCOPTER EC135 REGISTERED TO OMNIFLIGHT HELICOPTERS INC. DEPARTED NORTH PERRY AIRPORT FLORIDA (KHWO) ON A 14 CFR 135 AIR AMBULANCE FLIGHT AT APPROXIMATELY 0845 LOCAL TIME. THE PILOT STATED HE DEPARTED TO THE EAST ENROUTE TO KEY WEST. AT APPROXIMATELY 200-250 FEET ABOVE GROUND LEVEL (AGL) THE ROTOR RPM SEGMENT LIGHT ILLUMINATED (HIGH SIDE) FOR 2-3 SECONDS. HE NOTICED THE #1 AND #2 NEEDLES SPLIT WITH THE #1 NEEDLE LOWER AND DECREASING. THE #2 NEEDLE WAS STABLE. (AT THE TIME OF THE INTERVIEW THE PILOT WAS NOT SURE WHICH SYSTEM WAS FAILING. LATER WHEN THE PILOT SAT IN THE AIRCRAFT HE CONFIRMED THAT ENGINE N2 SYSTEM WAS THE CORRECT GAUGE HE WAS REFERENCING). THE PILOT FURTHER STATED THE ROTOR RPM WAS HIGH AND CLIMBING. HE MANUALLY TOOK CONTROL USING THE TWIST GRIP. THIS ACTION BROUGHT THE #1 ENGINE OUT OF FADC AND INTO MANUAL. HE STATED THAT HE ASKED THE PARAMEDIC TO VERIFY WHAT CAUTION LIGHTS WERE ILLUMINATED. THE PARAMEDIC VERIFIED THAT "TWIST GRIP AND ENGINE MANUAL ON THE #1 SIDE." AS HE MADE HIS TURN BACK TO THE AIRPORT HE INFORMED THE TOWER THAT HE INTENDED TO RETURN TO THE AIRPORT. THE PILOT WAS ABLE TO STABILIZE THE AIRCRAFT AND SYSTEMS EXCEPT FOR THE HIGH ROTOR RPM. COLLECTIVE WAS INCREASED AS MUCH AS POSSIBLE WHILE MAINTAINING A SHALLOW APPROACH. AT APPROXIMATELY 75 FEET AGL THE HELICOPTER BEGAN TO SHUTTER AND AFTER ABOUT ONE OR TWO SECONDS THE PILOT ELECTED TO ENTER AN AUTOROTATION TO THE GROUND. THE HELICOPTER LANDED WITHOUT INCIDENT. THE HELICOPTER DID CONTINUE TO SHUTTER THROUGHOUT THE ENTIRE LANDING. AT ABOUT 50 FEET AGL A DOOR POPPED OPEN DUE TO THE VIBRATION. AN INTERVIEW WITH THE AIR TRAFFIC CONTROLLER ON DUTY STATED THAT THE HELICOPTER MADE A NOISE AS IF IT WERE OUT OF TRACK. SEVERAL DAYS LATER TECHNICIANS FOUND STRUCTURAL DAMAGE HAD OCCURRED DUE TO THE OVER SPEED. THE #1 AND #2 ENGINE POWER TURBINES WERE LOCKED UP AND COULD NOT BE ROTATED BY HAND. THE AFT ENGINE SUPPORT TO THE #1 AND #2 ENGINES WERE BENT AND DISTORTED DUE TO THE ROTOR OVER SPEED. BOTH ENGINE FADC COMPUTERS WERE REMOVED AND SENT TO THE MANUFACTURER FOR DATA EVALUATION. THE NTSB INVESTIGATOR STATED THAT CASE WOULD BE CONSIDERED AN INCIDENT BY THE NTSB AND WOULD NOT BE ISSUED AN ACCIDENT CONTROL NUMBER.

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.
