FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX99TA299 · Bell B212

9 Sept 1999 · Bakersfield, CA, United States

USDA Forest Service Bell B212 · Accident: in flight collision with object while maneuvering

Report a problem

Event

NTSB case
LAX99TA299
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
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 B212

Aircraft type
Bell B212
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
N212AR
Onboard fatalities
Unknown
Route
From not recordedTo 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 133: Rotorcraft Ext. Load
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
Maneuvering
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
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire, transmission
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 › Visual lookout, inadequate

Approximate · Estimated position: the centre of Bakersfield, CA, the place the record names. Not the accident site.

NTSB narrative

While engaged in fire fighting water-dropping operations, the helicopter impacted high tension power transmission wires and fell to the ground under marginal control. The pilot and helicopter were reassigned from another nearby base on the morning of the accident and, at the time of the wire strike, the pilot was engaged in his first operational sortie in the new area. Prior to takeoff the pilot had been briefed about wire hazards in the area. A topographical map that was used in the briefing showed high power transmission wires, including the set the pilot later impacted, as red lines. After takeoff, the pilot proceeded to the fire area and made an initial drop on the fire. It was while returning to the dip site to refill that the wire strike occurred. The pilot reported that as he approached the dip site at 250 - 300 feet agl, he was aware of a power transmission tower high on the mountain to his right, well above him. He was also aware of another tower to his left on the valley floor below and an electrical powerhouse on the valley floor nearly in front of him. He thought that the wires from both the tower on his right and the tower on his left went to the powerhouse and were beneath him. In fact, the wires were strung directly from the tower above him, on the right, to the lower tower, on his left, and crossed his flight path at the helicopter's altitude. Visual meteorological conditions prevailed and smoke was not present in the area of the accident. Flights flown after the accident in like conditions of daylight and visibility showed the wires could not be visually detected until the helicopter was 'extremely close to the wires.'

Probable cause

The failure of the pilot-in-command to maintain adequate visual surveillance to see and avoid power transmission wires known to be in the area.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX99TA299
Event ID
20001212X19818
Case number
LAX99TA299
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: 08bf1e3ede041d88211b731276e2eb1b453719ecf571d9da24118a2be3694aae; retrieved 2026-09-21T20:24:04.594Z.