MIA88FA001 · Piper PA-23-250
Applied Mechanical Services Piper PA-23-250 · Accident: in flight encounter with weather en route
From Page Field (FMY) to Miami-Opa Locka Executive Airport (OPF)
Event
- NTSB case
- MIA88FA001
- 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
- 3 · 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
Piper PA-23-250
- Aircraft type
- Piper PA-23
- 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
- N3RP
- Operator
- Applied Mechanical Services
- Onboard fatalities
- Unknown
- Route
- From Page Field (FMY), FT. MYERS, FLTo Miami-Opa Locka Executive Airport (OPF), OPA LOCKA, FL
- 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 91: General Aviation
- 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
- En route · cruise
- 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 encounter with weather
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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
- Pilot in command › Became lost/disoriented, inadvertent
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Spiral, not corrected
- Pilot in command › VFR flight into imc, inadvertent
- Pilot in command › Weather evaluation, poor
Approximate · Estimated position: the centre of Everglades City, FL, the place the record names. Not the accident site.
NTSB narrative
THE NON-INSTRUMENT RATED PLT ATTEMPTED A VFR FLT OVER THE EVERGLADES DURING THE HRS OF DARKNESS. THE ACFT CRASHED INTO A SWAMPY AREA AT A HIGH RATE OF SPEED WHILE IN A 90 DEGREE LEFT BANK. THE ACFT DISINTEGRATED ON IMPACT. A CONVECTIVE SIGMET WAS ISSUED ABOUT 25 MINUTES AFTER DEPARTURE. IT IS UNKNOWN WHETHER THE FLT RECEIVED THE SIGMET INFORMATION. AN EVERGLADES NATIONAL PARK RANGER PILOT, WHO ARRIVED ON THE SCENE AFTER THE ACCIDENT, STATED THAT THE AREA INTO WHICH THE FLT WAS OPERATING WAS DESOLATE, WITH NO GROUND LIGHTS & NO DISCERNABLE HORIZON DURING THE HRS OF DARKNESS. THE SURFACE WX OBSERVATION AT FORT MYERS, ABT 50 MILES NW OF THE ACCIDENT SITE, INDICATED 4,500 FOOT BROKEN CLOUDS AND 7 MILES VISIBILITY. WX SATELLITE PHOTOS INDICATED THUNDERSTORMS IN THE AREA WHERE THE ACCIDENT TOOK PLACE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA88FA001
- Event ID
- 20001213X32377
- Case number
- MIA88FA001
- 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: ac7c0599d0dab548cd0010e0902acfcdf78be3a4dbc7f20ece32d5d1635e56f9; retrieved 2026-09-21T03:57:42.595Z.