FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17CA120 · Aero Commander S2R UNDESIGNAT

2 Mar 2017 · Fairmont, OK, United States

Carson Flying Service Aero Commander S2R UNDESIGNAT · Accident: low altitude operation/event while maneuvering

From PRI · Breckenridge, OK to PRI · Breckenridge, OK

Report a problem

Event

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

Aero Commander S2R UNDESIGNAT

Aircraft type
Aero Commander S2
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
N1755S
Onboard fatalities
Unknown
Route
From PRI · Breckenridge, OKTo PRI · Breckenridge, OK
Aircraft age
About 49 years (built 1968)
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
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 › Psychological

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

NTSB narrative

The pilot stated that he was conducting spray operations to a pasture with power lines on its north border. As the pilot approached the pasture from the north on his fourth pass, he intended to descend after flying past the second of two cables. The pilot initiated a descent, but the airplane struck the second cable. The airplane subsequently impacted the ground and a postimpact fire ensued. Following the accident, the pilot stated that he misidentified the first cable as the second cable.

Probable cause

The pilot’s failure to maintain clearance from a power line while conducting agricultural spray operations.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17CA120
Event ID
20170307X02808
Case number
CEN17CA120
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. 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: 07aada99ee87939a0f7a03bbf2d4e9828f49a8e3ecb81de2720f986578ac59c5; retrieved 2026-09-16T05:04:33.196Z.