ASN Wikibase Occurrence # 65876
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Sunday 21 June 2009 |
| Time: | 01:20 |
| Type: |  Robinson R22 Beta |
| Owner/operator: | Palm Beach Helicopters |
| Registration: | N2306T |
| MSN: | 1951 |
| Year of manufacture: | 1991 |
| Total airframe hrs: | 6631 hours |
| Engine model: | Lycoming O320-B2L |
| Fatalities: | Fatalities: 0 / Occupants: 2 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Del Ray Beach, FL -
 United States of America
|
| Phase: | En route |
| Nature: | Training |
| Departure airport: | Palm Beach County Park Airport, FL (LNA/KLNA) |
| Kendall-Tamiami Executive Airport, FL (TMB/KTMB) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
On June 21, 2009, about 0120 eastern daylight time, a Robinson R-22 Beta helicopter, N2306T, collided with trees while executing an emergency autorotation in Del Ray Beach, Florida. The certificated flight instructor (CFI) and student pilot received minor injuries and the helicopter sustained substantial damage. The flight was operated as an instructional flight under the provisions of 14 Code of Federal Regulations (CFR) Part 91, with an instrument flight rules (IFR) flight plan filed. Night visual meteorological conditions prevailed at the time of the accident. The flight originated from the Palm Beach County Park Airport (LNA), Lantana, Florida, at 0105, and was enroute to Kendall-Tamiami Executive Airport (TMB), Miami, Florida, when the accident occurred.
According to the CFI, they had taken off from LNA and just opened their flight plan with Miami Center. They were at 3000 feet with an airspeed of 65 -70 knots when he felt a low frequency vibration throughout the helicopter. He described the vibration as being a lateral vibration as if coming from the tailrotor. He did not remember feeling the vibration in the pedal or cyclic, but more of an overall vibration. He took over the controls from the student and lowered the collective, but could not remember if he rolled the throttle off or not. He decided on a spot to autorotate into. He noticed the clutch light was on and one other light, but wasn’t sure which light it was, it’s color or location on the panel. He said the vibration did not get any better or any worse as he reduced power and he never attempted to add power. He was confident there was no overspeed of the engine or the rotor and he did not recall hearing the low rotor RPM warning horn. As they approached the chosen spot, he saw wires and decided on a second spot closer to some trees. The helicopter made contact with the trees and the ground.
According to the student pilot, during a change in cruise altitude from 3,500 feet mean sea level (MSL) to 4,000 msl, they felt an airframe vibration. The vibration increased in intensity to a point where they could not read the instrument panel and they both observed the rotor brake light and clutch light illuminate. The CFI took control of the helicopter and initiated an emergency autorotation. During flare/touchdown the low rotor rpm light and horn came on as the helicopter stuck some trees and rolled onto its right side.
Examination of the helicopter by a Federal Aviation Administration (FAA) Inspector found the leading edge of the main rotor blades had no impact damage and other than being bent, the blades were intact. The pitch control rod to one blade was broken on impact. The temperature tape on the main gearbox was within normal range. The tail rotor blades or gearbox showed no impact damage. The right side of the horizontal stabilizer was bent from impact with the ground on the right side of the helicopter. The tail section was broken and bent downward and to the left. The vibration dampener inside the tail cone was not damaged. Both main drive vee belts were off their pulleys. The forward vee belt left black residue on the front side of the pulley and shaft. The rear vee belt was broken in two and also had breaks in the center between the two v sections. Other than the breaks, the belts had no evidence of deterioration. There was no indication that the belts had visible damaged prior to the flight.
A review of the helicopters logbooks found no entries as to when the drive vee belts were last changed. The was last engine overhauled 430.5 hours prior to the accident. The total time on the helicopter at the time of the accident was 6,630.6 hours.
- Probable Cause:
"An in-flight failure of the main drive vee belts."
Accident investigation:
 |
|
Sources:
NTSB
2. FAA: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=2306T
3. http://www.griffin-helicopters.co.uk/accidents.aspx?ManufacturerKey=1
4. https://www.wptv.com/mostpopular/story/Helicopter-down-in-Delray-Beach/wGiLSMt5X02RKCvnQXekbQ.cspx
5. http://www.wpbnews1st.com/helicopter-crashes-in-delray-beach/
6. http://asj.nolan-law.com/2009/06/accidents-incidents-61409-62009/
7. http://www.foxnews.com/story/2009/06/21/helicopter-crashes-off-florida-beach.html
8. http://southflorida.sun-sentinel.com/news/sfl-helicopter-crash-bn092109,0,2727114.story
Location
Images:
Photo(c): NTSB
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 21-Jun-2009 06:25 | slowkid | Added |
| 22-Jun-2009 09:05 | slowkid | Updated |
| 03-Oct-2016 13:15 | Dr.John Smith | Updated [Time, Location, Departure airport, Destination airport, Source, Narrative] |
| 26-Sep-2018 19:19 | Dr.John Smith | Updated [Source] |
| 16-Aug-2021 07:56 | harro | Updated [Date, Time, Source, Accident report] |
| 26-Feb-2022 00:17 | Captain Adam | Updated [Location, Departure airport, Destination airport, Narrative, Photo] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation