MIA97LA207 · Wsk Pzl Mielec M-18A
Air Crop Care Wsk Pzl Mielec M-18A · Accident: loss of engine power during landing
From Belle Glade State Municipal Airport (X10) to an unrecorded destination
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
- MIA97LA207
- 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
- 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
Wsk Pzl Mielec M-18A
- Aircraft type
- WSK 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
- N82019
- Operator
- Air Crop Care
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Belle Glade State Municipal Airport (X10), Belle Glade, FLTo 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
- Landing · emergency landing after takeoff
- 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
- Loss of engine power
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane departed from a section of road which was about 3,000 feet long. At an altitude of about 50 feet above the ground, in a left turn to the crosswind, the pilot reported that the airplane's engine lost power, and was running rough. A forced landing was made to a sugar cane field. The pilot maneuvered the airplane and touched down in the sugar cane field, the propeller struck a railroad switching unit, crossed over an irrigation canal, struck the bank of the canal with the tail wheel, nosed over, and a postcrash fire ensued. Examination of the wreckage revealed that the post crash fire melted the accessory case of the engine, post-crash testing of the engine was not possible. The reason for the loss of engine power was not determined.
Probable cause
a forced landing as a result of an undetermined loss of engine power and subsequent impact with a railroad switching unit and nose over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA97LA207
- Event ID
- 20001208X08463
- Case number
- MIA97LA207
- 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: 70b1ee28b82e92d40dc8545837a1dc40a1c3fa632f11af553ede8e49c1192825; retrieved 2026-09-22T19:13:15.498Z.