Petroleum Helicopters Aerospatiale SA-330J accident
Aerospatiale SA-330J · Accident: in flight collision with object during landing
From Baham Airstrip (2LA3) to an unrecorded destination
Event
- NTSB case
- FTW88FA039
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 15 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Aerospatiale SA-330J
- Aircraft type
- Aerospatiale SA-330
- Category
- Helicopter
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N3596N
- Operator
- Petroleum Helicopters
- Onboard fatalities
- Unknown
- Route
- From Baham Airstrip (2LA3), INTRACOASTAL, LATo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 135: Air Taxi & Commuter
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- In flight collision with object
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Clearance, not maintained
- Pilot in command › Planned approach, improper
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
THE HELICOPTER, WITH 2 PLTS & 13 PASSENGERS, WAS ON AN IFR FLT TO A PSN IN THE GULF OF MEXICO. FROM THAT PSN, THEY PROCEEDED UNDER VFR TO AN OFF-SHORE OIL DRILLING RIG (EI-190). AS THE HELICOPTER WAS ARRIVING FROM THE SE, THERE WAS A STRONG WIND FROM THE NE. THE LANDING PLATFORM (HELIPAD) WAS LOCATED ON THE NW SIDE OF THE OIL RIG. THE PLT ELECTED TO MAKE AN APCH TO THE HELIPAD BY FLYING PARALLEL TO THE UPWIND (NE) SIDE OF THE OIL RIG, RATHER THAN GOING AROUND THE DOWNWIND SIDE & APCHG THE HELIPAD BY FLYING INTO THE WIND. AFTER PROCEEDING TO AN AREA OVER THE VCNTY OF THE HELIPAD, THE PLT TURNED THE HELICOPTER TO THE RGT & ALIGNED IT IN THE DIRECTION OF THE WIND. THE HELICOPTER WAS THEN OBSERVED TO DRIFT REARWARD & TO THE RGT UNTIL THE MAIN ROTOR BLADES COLLIDED WITH THE NW LEG OF THE OIL RIG. IT THEN CRASHED ON THE OIL RIG & WAS DESTROYED BY IMPACT & FIRE. AN NTSB STUDY SHOWED THE WIND WAS FROM 040 DEG AT 35 KTS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW88FA039
- Event ID
- 20001213X32701
- Case number
- FTW88FA039
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 1442ec7136f500189b4a3b59e34d5da5ac3240d3141728195bf852242ea00712; retrieved 2026-09-18T14:12:27.167Z.