WPR23LA001 · Scoda Aeronautica Ltda SUPER PETREL LS
Scoda Aeronautica Ltda SUPER PETREL LS · Accident: low altitude operation/event while maneuvering
From Polson Airport (8S1) to an unrecorded destination
Event
- NTSB case
- WPR23LA001
- 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
- 1 · 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
Scoda Aeronautica Ltda SUPER PETREL LS
- Aircraft type
- Scoda Aeronautica Ltda SUPER PETREL LS
- 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
- N892SP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Polson Airport (8S1), Polson, MTTo not recorded
- Aircraft age
- About 7 years (built 2015)
- 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 · 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
- Low altitude operation/event
- 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
- Environmental issues › Physical environment
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The accident airplane was the lead airplane in a flight of two and while flying about 50 ft over a river, the airplane struck a power line. The airplane abruptly pitched up, descended to the right, and impacted the water, which resulted in substantial damage to the fuselage and wings. According to a witness, the pilot had prior experience flying at low level over the river close to the accident site. The trailing pilot reported that the accident pilot did not report any mechanical failures or anomalies before the impact with a powerline. The trailing pilot was not aware of the powerline placement, and it is likely that the pilot also did not see the powerline’s placement across the river as it was unmarked.
Probable cause
The pilot’s failure to maintain clearance from the powerline.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR23LA001
- Event ID
- 20221003106040
- Case number
- WPR23LA001
- 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, cause areas. 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: bbac8087ac53ec898353326ce703e5a8acac2b17522237259450297215f87119; retrieved 2026-09-15T07:52:07.002Z.