FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI03FA056 · Bell 206L-1

16 Jan 2003 · B.S. 53, LA, United States Narrative disagrees

Bell 206L-1 · Accident: loss of control in flight on approach

From Venice, LA to an unrecorded destination

Report a problem

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
CHI03FA056
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
1 · 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 206L-1

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
N3194P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Venice, 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
Approach
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
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
Destroyed

Cause areas

  • Pilot in command › Planned approach, improper
  • Pilot in command › Settling with power, encountered

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The on-demand offshore helicopter flight impacted an oil platform during landing. The pilot stated that he was performing a standard pinnacle approach to the helipad. The approach was described as normal until the helicopter crossed over the edge of the platform, at which point the helicopter suddenly descended below the approach path. He reported that an increase of power beyond 100% torque was ineffective in arresting descent rate. The platform was equipped with a windsock located to southeast side of the landing pad. The height of the windsock was such that it intersected the approximate plane formed by the helideck. The windsock was tattered and according to the pilot's report, "the end of the windsock was wrapped around the pole." Disassembly of the engine revealed no anomalies.

Probable cause

The improper approach by the pilot and the settling with power encountered by the pilot.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI03FA056
Event ID
20030117X00083
Case number
CHI03FA056
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: 5a34c452295a47a268ff3dd875667e7608307bc8804b918431079347d92d2d25; retrieved 2026-09-18T13:03:10.795Z.