ERA13IA313 · Bell Helicopter Textron Canada 206 L-4
New York Helicopter Charter Bell Helicopter Textron Canada 206 L-4 · Incident: loss of engine power (total) en route
From Downtown Skyport Heliport (JRB) to Downtown Skyport Heliport (JRB)
Event
- NTSB case
- ERA13IA313
- 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
- General aviation
- 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 Helicopter Textron Canada 206 L-4
- 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
- N405MR
- Operator
- New York Helicopter Charter
- Onboard fatalities
- Unknown
- Route
- From Downtown Skyport Heliport (JRB), New York, NYTo Downtown Skyport Heliport (JRB), New York, NY
- Aircraft age
- About 4 years (built 2009)
- 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 91: General Aviation
- 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
- En route · cruise
- 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 engine power (total)
- 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 power plant
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot reported that, during an overwater sightseeing flight in the single-engine helicopter and while at 1,500 ft, he heard a "bang," followed by the "engine out" warning. He then saw that the N2 (power turbine) indication was dropping. The pilot decided to perform an autorotation, and just before lowering the collective and rolling the throttle to flight idle, he saw the "engine chip" light illuminate. During the landing flare, the pilot deployed the skid-mounted floats, bled off all forward airspeed, and completed a successful autorotation.
The turbine section of the turboshaft engine had recently been overhauled, and the engine had operated for about 2 hours before the incident. The No. 2 bearing in the compressor section and its corresponding races were found damaged and appeared dry with evidence of high-temperature exposure. The forward side of the bearing cage exhibited significantly more damage than the aft side; the forward side was deformed, and the bearing balls on that side appeared rough and had large areas of material loss. Metallurgical examination revealed thermal distress to the raceway surfaces consistent with the bearing operating with reduced oil flow.
To confirm oil flow, the engine gearbox was attached to an oil supply, and the engine oil pump was rotated by a hand drill. Three of the four jets from the oil supply tube produced streams of oil; however, the fourth jet, which normally supplied oil to the aft face of the No. 2 bearing, did not. Visual examination of the oil supply tube revealed that a dark, thick substance was adhered to the face and chamfer. Analysis of the substance determined that, although it was the correct-specification turbine oil, it was thermally degraded. Initial flow tests revealed that the oil supply tube that lubricated the No. 2 bearing was operating below the total flow requirement. The tube was cleaned ultrasonically multiple times, and, with each subsequent cleaning, the amount of debris collected decreased. After the cleanings, the No. 2 bearing orifice met the flow requirement.
Nearly the entire surface of the pressure oil screen, except for the area covered by an O-ring, was also covered in a thick, dark substance. A sample of the substance was also determined to be consistent with correct-specification but thermally degraded turbine oil. Additional components were also covered with coked and degraded turbine oil.
In addition, the engine oil pressure regulator valve was found backed out, and the poppet guide was atypically close to the outer lip of the housing. The atypical position indicated that adjustments, which were not documented, were likely made in response to high oil pressure indications. However, any adjustment to the oil pressure regulator valve would have been contrary to the engine manufacturer's maintenance manual, which cautioned not to do so for high oil pressure, which would have been "cause to suspect other oil system problems have developed."
The origin of the coking and buildup of degraded turbine oil within the supply system could not be determined; however, the extent to which the oil pressure regulator valve was found adjusted indicated that it had likely occurred over time, which in turn then masked a growing oil blockage problem within the oil lubrication supply paths.
Probable cause
The improper maintenance decision to adjust the engine oil pressure regulator valve in response to high oil pressure indications rather than to properly troubleshoot the anomaly, which then allowed an existing oil supply path blockage to increase and led to the eventual insufficient lubrication of the compressor section No. 2 bearing and the subsequent loss of engine power. Contributing to the incident was an engine oil lubrication system anomaly of unknown origin.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13IA313
- Event ID
- 20130702X95531
- Case number
- ERA13IA313
- 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. 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: acda9bc55022dc499d82cf18d96a0941af6aa33fbd307f5ab2505fcf97969605; retrieved 2026-09-15T22:05:09.740Z.