FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25LA336 · Piper PA-25-235

23 Aug 2025 · Argusville, ND, United States

Piper PA-25-235 · Accident: collision with terrain/object (non-CFIT) while maneuvering

From Dakota Airport (NA60) to an unrecorded destination

Report a problem

Event

NTSB case
CEN25LA336
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

Piper PA-25-235

Aircraft type
Piper PA-25
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
N7239Z
Operator
Zachary Wolf
Onboard fatalities
Unknown
Route
From Dakota Airport (NA60), Grandin, NDTo not recorded
Aircraft age
About 60 years (built 1965)
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
  • Environmental issues › Physical environment
  • Personnel issues › Psychological

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

NTSB narrative

The pilot reported that while maneuvering at low altitude during aerial application to a field, he noticed power lines. He pushed the control stick forward to maneuver the airplane underneath the power lines and then attempted to pull back on the control stick; however, due to the proximity to the ground, the airplane impacted terrain. The fuselage and left wing sustained substantial damage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain clearance from terrain while maneuvering at low altitude.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN25LA336
Event ID
20250823200843
Case number
CEN25LA336
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, 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: cf5322d065917b457be67619fe153a3f1334a2a665883bde7708386eda677369; retrieved 2026-09-16T20:15:03.090Z.