MIA90LA187 · Republic RC-3
Republic RC-3 · Accident: total loss of engine power (mechanical failure) en route
From Fort Lauderdale Executive Airport (FXE) to Lakeland Linder International Airport (LAL)
Event
- NTSB case
- MIA90LA187
- 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
Republic RC-3
- Aircraft type
- Republic RC-3
- 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
- N6291K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, FLTo Lakeland Linder International Airport (LAL), Lakeland, 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
- Total loss of engine power (mechanical failure)
- 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
- Engine assembly, piston › Failure, total
- Engine assembly, piston › Undetermined
- Fluid, oil › Starvation
- Pilot in command › Clearance, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING CRUISE FLT AT 3,000 FT, 20 MILES SOUTH OF THE INTENDED DESTINATION, THE PLT REPORTED THAT SMOKE FILLED THE COCKPIT. ABOUT 1 MINUTE LATER THE ENG SEIZED. DURING THE ATTEMPTED FORCED LANDING ON A WATER FILLED PHOSPHATE PIT, THE ACFT COLLIDED WITH AN EMBANKMENT SHORT OF THE PIT, NOSED OVER AND CAME TO REST INVERTED. EXAM OF THE ENG REVEALED THAT THE NUMBER 4 CYLINDER PISTON WAS DAMAGED CIRCUMFERENTIALLY FOR UNDETERMINED REASONS. ALSO DISCOVERED WAS THE FAILURE OF THE NUMBER 5 CYLINDER CONNECTING ROD. THE ENG WAS REPORTEDLY RECENTLY OVERHAULED BUT THE LOGBOOKS WERE INSIDE THE ACFT & WERE NOT RECOVERED.
Probable cause
AN ENGINE FAILURE WHICH REQUIRED AN EMERGENCY LANDING OFF AIRPORT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA90LA187
- Event ID
- 20001212X24332
- Case number
- MIA90LA187
- 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: 9dc6628c2005fc25a28f6cf63ef9988cfef225ed380614abc85884ad2dcf352d; retrieved 2026-09-21T15:35:22.967Z.