ASN Wikibase Occurrence # 145876
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: | Monday 28 May 2012 |
Time: | 16:10 |
Type: | Bell 206L-4 LongRanger IV |
Owner/operator: | PHI Inc |
Registration: | N7077F |
MSN: | 52038 |
Year of manufacture: | 1993 |
Total airframe hrs: | 12948 hours |
Engine model: | Rolls Royce 250C30P |
Fatalities: | Fatalities: 1 / Occupants: 1 |
Aircraft damage: | Substantial |
Category: | Accident |
Location: | South Timbalier (ST67B) Offshore Installation, Gulf of Mexico -
United States of America
|
Phase: | Landing |
Nature: | Offshore |
Departure airport: | |
Destination airport: | Gulf of Mexico, |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:The commercial pilot was attempting to land his single-engine helicopter on a fixed production platform helipad when the main rotor blades struck the corner of an oil derrick that was partially positioned over the helipad. The pilot lost control and descended inverted into the ocean. The emergency external floats were not inflated, and the helicopter sank. At the time of the accident, a mobile jack-up rig was mated with the fixed production platform. According to the company that owned the production platform, the helipad was closed and all flight operations were being conducted from the jack-up rig’s helipad, which was larger and unobstructed. However, at the time of the accident, the production platform’s helipad was not marked closed and no notice to airman (NOTAM) had been issued to notify pilots that the helipad was closed.
There was also nothing in the operator’s flight operations manual that would have restricted the pilot from landing under an obstruction. Other company pilots were aware that this helipad was a flight hazard due to the encroachment of the oil derrick, but it was never reported to management or via the company’s internal safety notification system. A review of company flight manifest records revealed that the pilot had flown to this platform on several occasions, including 2 days before the accident, and landed on the jack-up rig’s helipad. It could not be determined why the pilot decided to land on the smaller and obstructed helipad rather than the jack up rig’s larger helipad just 2 days later. Examination of the helicopter and engine revealed no preimpact mechanical failures or malfunctions that would have precluded normal operation.
Probable Cause: The pilot’s failure to maintain clearance from an obstacle while landing on an obstructed helipad, which resulted in a collision and loss of control. Contributing to the accident was the failure of the helipad owner to mark the helipad closed and the failure of the flight operator to report the known hazard and issue a notice to airman.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | CEN12FA321 |
Status: | Investigation completed |
Duration: | 1 year |
Download report: | Final report |
|
Sources:
NTSB
Location
Revision history:
Date/time | Contributor | Updates |
29-May-2012 01:18 |
gerard57 |
Added |
29-May-2012 02:32 |
RobertMB |
Updated [Time, Aircraft type, Source, Narrative] |
29-May-2012 10:34 |
Geno |
Updated [Aircraft type, Registration, Cn, Source] |
08-Jun-2012 18:04 |
Geno |
Updated [Time, Location, Phase, Nature, Departure airport, Destination airport, Source, Narrative] |
21-Aug-2016 20:57 |
Dr.John Smith |
Updated [Time, Operator, Source, Narrative] |
29-Sep-2016 17:32 |
Aerossurance |
Updated [Time, Location, Departure airport, Destination airport, Source, Narrative] |
21-Dec-2016 19:28 |
ASN Update Bot |
Updated [Time, Damage, Category, Investigating agency] |
27-Nov-2017 20:41 |
ASN Update Bot |
Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation