FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13LA163 · PZL Mielec M-18A

15 Feb 2013 · Jennings, LA, United States

Riceland Aviation PZL Mielec M-18A · Accident: loss of control in flight while maneuvering

From Jennings, LA to Jennings, LA

Report a problem

Event

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

PZL Mielec M-18A

Aircraft type
PZL Mielec M-18
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
N4305D
Onboard fatalities
Unknown
Route
From Jennings, LATo Jennings, LA
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 · 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
Loss of control in flight
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
Tower/antenna (incl guy wires)
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
  • Environmental issues › Physical environment
  • Personnel issues › Psychological

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

NTSB narrative

The pilot was conducting aerial application activities to the southeast of the airport. After the pilot finished spraying a field with a radio tower located in the northwest corner, the airplane struck the tower's guy wires. Although the tower was marked, the guy wires were not nor were they required to be marked. The tower was also depicted on the relevant aeronautical sectional chart. An examination of the airframe, engine, and related systems revealed no malfunctions or failures that would have precluded normal operation. At the time of the accident, the reported weather conditions were scattered clouds at 7,000 feet with the sun setting and visibility greater than 10 miles. It is unknown the extent that the clouds may have obscured the guy wires. The setting sun should have been behind the pilot during his pass and therefore not a factor. Based on the available evidence, it is likely the pilot lost track of the tower's location relative to his and did not notice the guy wires in time to avoid a collision.

Probable cause

The pilot’s inadequate visual lookout, which resulted in a collision with guy wires during an aerial application flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13LA163
Event ID
20130216X54725
Case number
CEN13LA163
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: 876cc62d374d3a87c835567a405cfa1058827182d818301346ad4277f0719bf9; retrieved 2026-09-14T15:53:07.034Z.