MIA83FA149 · Piper PA-23C-250
Lucaya Beach Air Service Piper PA-23C-250 · Accident: loss of control in flight during initial climb
From an unrecorded airport to Grand Bahama International Airport (MYGF)
Event
- NTSB case
- MIA83FA149
- 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
- 5 · 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-23C-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
- N6103Y
- Operator
- Lucaya Beach Air Service
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Grand Bahama International Airport (MYGF), Freeport
- 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
- Initial climb
- 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 control in flight
- 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
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT CRASHED SHORTLY AFTER TAKEOFF. ACCORDING TO WITNESSES, THE ACFT VEERED TO THE LEFT LOSING ALTITUDE AND SUDDENLYFLIPPED TO THE LEFT CRASHING ABOUT 1/2 MILE FROM THE ARPT IN A STEEP LEFT BANK. THE LANDING GEAR WAS REPORTED IN A DOWN POSITION. AN AIRLINE PLT REPORTED THAT THE ACFT APPEARED TO BE IN DIFFICULTY AFTER TAKEOFF AS IT BEGAN TO PORPOISE. APPARENTLY THE GEAR WAS NOT RETRACTED AS THE PLT FOUGHT THE ACFT AND AS HE BEGAN A TURN TO THE LEFT. HE OBSERVED THE ACFT TURN COMPLETELY UPSIDE DOWN, POINT NEARLY STRAIGHT DOWN AND EXPLODE ON CONTACT. ONE WITNESS REPORTED 'THE LEFT ENGINE WAS ON FIRE AND I COULD SEE SMOKE ALSO.' THE MAXIMUM ALT ATTAINED BY THE ACFT WAS ESTIMATED AS 55 FT. THE POST ACCIDENT EXAMINATION REVEALED NO EVIDENCE OF POWER PLANT FAILURE OR MALFUNCTION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA83FA149
- Event ID
- 20001214X43077
- Case number
- MIA83FA149
- 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: 3b60d66317c62d9d13530bc878cc1f87ef54d5ce4f37dc5bb6599d5adab76af7; retrieved 2026-09-21T06:42:58.903Z.