CHI07TA201 · WSK PZL Mielec PZL M18B
WSK PZL Mielec PZL M18B · Accident: in flight collision with terrain/water while maneuvering
From Rapid City Regional Airport (RAP) to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's flight rules. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CHI07TA201
- 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
- Government
- 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
WSK PZL Mielec PZL M18B
- Aircraft type
- WSK PZL Mielec PZL M18B
- 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
- N14067
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rapid City Regional Airport (RAP), Rapid City, 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
- Public Aircraft Narrative disagrees
- 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 terrain/water
- 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
- Pilot in command › Altitude/clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The agricultural application airplane sustained substantial damage when it impacted terrain while maneuvering for a public use aerial application of fire retardant. The pilot stated that he was approaching a fire location from the northwest. He was crossing a "burnt area from west to east across gently rolling terrain." When he crossed a ridgeline, he encountered a downdraft and the airplane "wanted to settle." The pilot "pushed [the] nose over and released [the] load." The pilot stated that the airplane would not recover before impacting terrain. The pilot reported no mechanical malfunctions with the airplane in reference to the flight. Gusty winds were present in the area at the time of the accident.
Probable cause
The pilot's failure to maintain clearance from terrain during an aerial application maneuver. Contributing to the accident were wind gusts, low altitude, and the reported downdraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07TA201
- Event ID
- 20070711X00914
- Case number
- CHI07TA201
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: 9b0c54daf431fab3469fe6fe7ff5f46ed084577de22c22e9cd0a2f9d60e67755; retrieved 2026-09-21T18:27:47.457Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: operation. The narrative states the airplane "impacted terrain while maneuvering for a public use aerial application of fire retardant"; the flight was a public aircraft operation, not Part 91 general aviation.