Rotorcraft Leasing Bell 206 L4 incident
Bell 206 L4 · Incident: loss of control in flight on approach
From Gulf of Mexico, LA (no airport) to Gulf of Mexico, LA (no airport)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN10IA397
- 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
- Incident
- 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
- Unknown
- 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
Bell 206 L4
- Aircraft type
- Bell 206
- 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
- N523RL
- Operator
- Rotorcraft Leasing
- Onboard fatalities
- Unknown
- Route
- From Gulf of Mexico, LA (no airport)To Gulf of Mexico, LA (no airport)
- 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
- Approach · VFR go-around
- Defining eventThe 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
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Aircraft › Aircraft propeller/rotor
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, the helicopter was on final approach to a platform in the Gulf of Mexico when he raised the collective to perform a go-around. However, the helicopter did not respond properly; rather, its performance and torque indications remained fixed at 45 percent. The pilot began a slow climb and diverted to a land-based airport at a cruise speed of about 60 knots. Because of a complete loss of collective pitch control, the pilot made a running landing on the runway at the airport, touching down about 45 knots. The helicopter came to a stop in the grass about 100 feet past the end of the runway. An examination of the helicopter revealed that several fasteners were missing from the top clevis of the collective control tube, which led to the control tube becoming disconnected from the collective pitch arm on the swash plate. The missing fasteners were found loose on the deck in the transmission compartment. Records showed that maintenance to reinstall the transmission and main rotor hub had been completed about 6 flight hours before the incident and that several mechanics and two pilots had examined the helicopter before the incident flight without noting the improperly secured/missing fasteners.
Probable cause
Improper reassembly of the collective flight controls by maintenance personnel. Contributing to the incident were inadequate postmaintenance examinations by maintenance personnel and inadequate preflight inspections by two pilots.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10IA397
- Event ID
- 20100715X13336
- Case number
- CEN10IA397
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 554d6f5332f5af0e299d5bee19bc62d106ff112ab1f236ef8c98d73a7c09c035; retrieved 2026-09-15T14:42:00.903Z.