FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI01LA251 · Aero Commander S2R

31 Jul 2001 · Pierre, SD, United States

Ice Spray Service Aero Commander S2R · Accident: in flight collision with object while maneuvering

From Pierre Regional Airport (PIR) to an unrecorded destination

Report a problem

Event

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

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
N5551X
Onboard fatalities
Unknown
Route
From Pierre Regional Airport (PIR), Pierre, SDTo not recorded
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 · aerial application
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
Destroyed

Cause areas

  • Pilot in command › Clearance, not obtained

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

NTSB narrative

The airplane struck a transmission line while spraying a field. The pilot/owner of the agricultural operator made several passes under the transmission line prior to the strike. He stated that he was "a little high" when the airplane's rudder struck the transmission line tearing the rudder completely off and damaging the vertical stabilizer. He also added that he could not control the airplane following the strike and forced the airplane down in attempt to avoid hitting a house.

Probable cause

clearance not obtained by the pilot. A contributing factor was the transmission line.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI01LA251
Event ID
20010731X01570
Case number
CHI01LA251
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: 52e930ccb667611fabcf5bdb88bef0ee8ead7b3dd227004cefd6c7008d044a26; retrieved 2026-09-21T09:57:03.816Z.