Idaho Helicopters McDonnell Douglas MD-900 accident
McDonnell Douglas MD-900 · Accident: in flight collision with object en route
From an unrecorded airport to Rigby Airport (U56)
Event
- NTSB case
- SEA99LA016
- 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
- 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
McDonnell Douglas MD-900
- Aircraft type
- McDonnell Douglas MD-900
- 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
- N977LF
- Operator
- Idaho Helicopters
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Rigby Airport (U56), Boise, ID
- 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
- En route · climb to cruise
- 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; Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Clearance, not obtained/maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The McDonnell Douglas MD-900 medevac helicopter was dispatched to a car accident at a site characterized by high terrain and high trees. Prior to landing, the pilot requested information about wires and was advised by ground personnel that 'there were none.' Subsequent to landing, the pilot examined the landing site and proposed departure route for wires, and reportedly observed none. The departure from the site was conducted under dusk to dark night conditions. While climbing out vertically due to the narrow canyon conditions at the site, the helicopter struck unmarked transmission lines approximately 150 feet above ground. The pilot then determined that the helicopter was controllable and displayed no unusual flight characteristics, and chose to proceed to his destination. Post-flight examination revealed crazing of the windscreen and damage to four of the five main rotor blades requiring major repair/replacement.
Probable cause
The pilot-in-command's not obtaining/maintaining clearance with the unmarked transmission lines. Contributing factors were environmental (dusk) conditions, the transmission lines, and both the pilot-in-command and the ground personnel not identifying the existence of the hazardous condition (high wires).
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA99LA016
- Event ID
- 20001211X11501
- Case number
- SEA99LA016
- 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 1998-11-30.
- API snapshot SHA-256: 661991676a092d7c3751616d4950c89e1473fa60de1441faf52144e354c17f97; retrieved 2026-09-18T17:02:13.326Z.