WPR14LA198 · Rockwell International S 2R UNDESIGNAT
Clear Skies Aviation Rockwell International S 2R UNDESIGNAT · Accident: ground collision during landing
From Sher-Wood Airport (PWD) to Sher-Wood Airport (PWD)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR14LA198
- 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
Rockwell International S 2R UNDESIGNAT
- Aircraft type
- Rockwell S-2
- 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
- N702CB
- Operator
- Clear Skies Aviation
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Sher-Wood Airport (PWD), Medicine Lake, MTTo Sher-Wood Airport (PWD), Medicine Lake, MT
- Aircraft age
- About 37 years (built 1977)
- 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
- Landing · flare/touchdown
- 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
- Ground collision
- 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
- Personnel issues › Task performance
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 reported that he was maneuvering the airplane into a left banking turn after an aerial application. He added that, the next thing that he could remember, was that he could not arrest the airplane's descent and that it was heading toward the ground. The pilot tried to correct the airplane's attitude by pulling up, but the airplane subsequently impacted terrain.
Wreckage examination revealed that the left wing contacted the ground first. Engine examination and component testing did not reveal evidence of any preimpact mechanical anomalies that would have precluded normal operation. It is likely that the pilot did not maintain airplane control and sufficient altitude to clear terrain during the turn.
Probable cause
The pilot’s failure to maintain airplane control and sufficient altitude to clear terrain during a low-altitude maneuver.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14LA198
- Event ID
- 20140522X23743
- Case number
- WPR14LA198
- 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. 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: 3819794c27ea5ccedbfceacea1cd9250ffae9b36de12560d0d0a9872321240bd; retrieved 2026-09-15T23:39:02.647Z.