SEA08CA168 · WSL PZL Mielec
WSL PZL Mielec · Accident: collision with terrain/object (non-CFIT) while maneuvering
From Hubler Field (ID00) to Hubler Field (ID00)
Event
- NTSB case
- SEA08CA168
- 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
- 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
WSL PZL Mielec
- Aircraft type
- WSL PZL MIELEC
- 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
- N81541
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hubler Field (ID00), Caldwell, IDTo Hubler Field (ID00), Caldwell, 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 137: Agricultural
- 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 · low-altitude flying
- 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
- Collision with terrain/object (non-CFIT)
- 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
- 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
- Aircraft › Aircraft oper/perf/capability
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The Federal Aviation Administration inspector reported that he discussed the accident with the pilot. The pilot indicated to the FAA inspector that he was conducting aerial application operations. He was flying over the field and going to pass below a power line. As he neared the power line, he noticed a vehicle on the road. The pilot gained altitude in order to provide separation between the airplane and the vehicle. As the airplane gained altitude, it collided with the power lines. The airplane then descended into the terrain. There were no mechanical anomalies reported with the airplane. At the time of this report, the pilot did not submit NTSB Form 6120.1/2, the Pilot Operator Report.
Probable cause
The pilot failed to maintain clearance from a power line while maneuvering. Contributing to the accident was a vehicle.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA08CA168
- Event ID
- 20080822X01295
- Case number
- SEA08CA168
- 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, coordinates. 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: d4144ff3ecacf704e13d6506ac3aed34ea577bdc8e38b0297eed0ff0e48c7d75; retrieved 2026-09-15T10:05:37.576Z.