SEA99LA059 · Cessna 172D
Cessna 172D · Accident: in flight collision with object en route
From Mountain Home Municipal Airport (U76) to Jackpot Airport/Hayden Field (06U)
Event
- NTSB case
- SEA99LA059
- 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
Cessna 172D
- Aircraft type
- Cessna 172
- Category
- Airplane
- 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
- N2650U
- Operator
- Jonathan E. Powell · private individual
- Onboard fatalities
- Unknown
- Route
- From Mountain Home Municipal Airport (U76), Mountain Home, IDTo Jackpot Airport/Hayden Field (06U), Jackpot, NV
- 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
- En route · 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
- 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 maintained
- Pilot in command › Visual lookout, inadequate
- Pilot passenger › Clearance, not maintained
- Pilot passenger › Visual lookout, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilots reported that while cruising up a river, one of the passengers spotted a coyote on the river bank and all the aircraft occupants turned to look at it. When the pilot-in-command (the left-seat pilot) directed his attention back to the front of the aircraft, he spotted unmarked powerlines crossing the river and warned the flying pilot (a non-current private pilot in the right front seat). The right-seat pilot pulled back on the control yoke, but the left-seat pilot stated it appeared to him that this would take them directly into the wires and he therefore pushed the yoke forward. The aircraft struck the wires, losing 1/3 of its vertical tail and 1/2 of its rudder; however, control of the aircraft was maintained. After climbing and performing a stability check and a simulated landing, the pilots returned to the departure airport and landed without further incident. Terrain in the vicinity of the powerline crossing is about 200 feet above the elevation of an airport on the river bank 2 1/2 miles upstream.
Probable cause
The failure of both pilots to see-and-avoid wires crossing the river. Factors included: transmission wires; inattention of both pilots to the aircraft's flight path; and the pilots' low-altitude flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA99LA059
- Event ID
- 20001205X00569
- Case number
- SEA99LA059
- 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: 84c7078df4a43d6113b40ca5635dd7cbf997b03d01b54e4c3edd1a751b56adfb; retrieved 2026-09-22T15:30:14.028Z.