CEN21FA368 · Rockwell International S2R
Rockwell International S2R · Accident: collision with terrain/object (non-CFIT) while maneuvering
From Linton Municipal Airport (7L2) to an unrecorded destination
Event
- NTSB case
- CEN21FA368
- 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
- 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
Rockwell International S2R
- Aircraft type
- Rockwell 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
- N4956X
- Operator
- Gunia Michel L
- Onboard fatalities
- Unknown
- Route
- From Linton Municipal Airport (7L2), Linton, NDTo not recorded
- Aircraft age
- About 36 years (built 1985)
- 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
- 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 pilot had completed one aerial application flight and was in the process of spraying a sunflower field. The flight track indicated that the airplane entered the area from the north and made a left turn over the field. The recorded flight track ended before the airplane descended toward the target field. It is likely that the pilot started spraying the field beginning at the northeast corner and headed west. A witness driving eastbound observed the airplane flying west after it exited the sunflower field. As the airplane flew under three power lines, the top of the vertical stabilizer hit the second line. The airplane then collided with the third line, crashed onto a road, and slid into a field. A colleague of the pilot, who was familiar with the operation, stated that he and the pilot had sprayed this field many times before and that they always used a north-south racetrack pattern. He had never seen the pilot spray this field in an east-west pattern before and added that it should not be done due to the large powerlines on the west side of the field. A postaccident examination of the accident site and airplane revealed wire strike signatures on the airplane. Two areas on the airplane exhibited black sooting and burn marks, which were indicative of the airplane contacting two power lines simultaneously resulting in electrical arcing. The airplane examination did not reveal any evidence of preimpact mechanical malfunction or anomalies that would have precluded normal operation.
Probable cause
The pilot’s intentional flight under power lines and his failure to maintain clearance from the lines during an aerial application flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN21FA368
- Event ID
- 20210810103667
- Case number
- CEN21FA368
- 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: ab9a23571a1982ccda19721ac246c707b973925650170c8e955900eceee0168e; retrieved 2026-09-15T07:33:05.943Z.