FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN00FA082 · McDonnell Douglas 369E

1 May 2000 · Bloomfield, NM, United States

McDonnell Douglas 369E · Accident: in flight collision with object while maneuvering

From NM (no airport) to Four Corners Regional Airport (FMN)

Report a problem

Event

NTSB case
DEN00FA082
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
2 · 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

McDonnell Douglas 369E

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
N1606K
Operator
Unknown
Onboard fatalities
Unknown
Route
From NM (no airport)To Four Corners Regional Airport (FMN), Farmington, NM
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 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
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, static
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 › Buzzing, intentional
  • Pilot in command › Clearance, not maintained

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

NTSB narrative

The helicopter had been used for fiber optic cable installation support operations earlier that day. The helicopter landed next to a company fuel truck at a job site approximately 20 miles south-southeast of Farmington, New Mexico, and approximately 12 miles west-southwest of the accident site. There the helicopter was refueled. The pilot told the driver he and his passenger were returning to Four Corners Regional Airport in Farmington. Shortly after it departed, an oilfield worker, investigating the source of a smoke plume, found the burning wreckage of the helicopter and notified authorities. A severed static line was found nearby. The utility company estimated the height of the static line, at the point where it was severed, to be 39 feet. The power lines were estimated to be 35 feet above the ground. A toxicological screen revealed the presence of tetrahydrocannabinol (marijuana) and tetrahydrocannabinol carboxylic acid (primary inactive metabolite of marijuana) in blood, lung, and bile.

Probable cause

The pilot's intentional buzzing (low level flying), and his failure to maintain clearance with the static wire. A factor was his physical impairment by a contraindicated drug controlled substance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN00FA082
Event ID
20001212X20970
Case number
DEN00FA082
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2000-05-02.
  • API snapshot SHA-256: d08857dff3c850307792051ea69962ecb3549f5a8eb5010d82ad5724788488ce; retrieved 2026-09-20T21:15:24.522Z.