Air Logistics Sikorsky S-76A accident
Sikorsky S-76A · Accident: propeller/rotor contact to person while standing
From 573B · OFFSHORE PLAT., GM to BLOCK 573A
Narrative check · The NTSB narrative appears to contradict this record's injuries. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- FTW88LA082
- 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
- 0 · 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
- Visual Meteorological Cond
Sikorsky S-76A
- Aircraft type
- Sikorsky S-76
- 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
- N1547N
- Operator
- Air Logistics
- Onboard fatalities
- Unknown
- Route
- From 573B · OFFSHORE PLAT., GMTo BLOCK 573A
- 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
- Standing · idling rotors
- 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
- Propeller/rotor contact to person
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Passenger › Procedures/directives, not followed
- Passenger › Visual lookout, inadequate
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
AFTER LANDING ON THE PLATFORM, THE COPILOT MOVED THE POWER LEVERS TO FLIGHT IDLE AND SET THE MAIN ROTOR BLADE TIP PATH PLANE TO THE HEIGHT NORMALLY USED. WHEN AN ENPLANNING PASSENGER CAME UP THE STAIRS ONTO THE PLATFORM, HE WAS STRUCK ON THE HEAD BY THE MAIN ROTOR BLADE. THE OPERATOR REPORTED THAT THE INJURED PASSENGER HAD BEEN REQUIRED TO VIEW A VIDEO TAPE RECORDING THAT SHOWED THE PROPER PROCEDURES TO USE WHEN ENPLANNING OR DEPLANNING. ADDITIONALLY, THEY REPORTED THAT HE HAD BEEN GIVEN SPECIFIC INSTRUCTIONS TO BEND OVER TO LOWER HIS HEIGHT WHEN UNDER THE MAIN ROTOR BLADES.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW88LA082
- Event ID
- 20001213X25262
- Case number
- FTW88LA082
- 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, damage. 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: dbae924fca48c0fd30f1d1b021dda089a1bcf5e0746b694be8b2e7b3a95d4899; retrieved 2026-09-18T19:24:42.032Z.