MIA00LA152 · Piper PA-18-150
Piper PA-18-150 · Accident: loss of engine power en route
From N55J · FERNANDINA BCH, FL to an unrecorded destination
Event
- NTSB case
- MIA00LA152
- 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
Piper PA-18-150
- Aircraft type
- Piper PA-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
- N760WB
- Operator
- William O. Rabitaille · private individual
- Onboard fatalities
- Unknown
- Route
- From N55J · FERNANDINA BCH, 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 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 · climb to 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
- Loss of engine power
- 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
- Stall
- 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
- Pilot in command › Airspeed, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated the engine lost power on initial takeoff climb at about 200 feet. He attempted a forced landing by applying full left rudder and forward stick to maintain airspeed. He said he had no further recollection of the accident. Witness stated they observed the airplane on climb out. The airspeed was described as slow. The airplane was observed to make a steep left turn (45-degrees or more) between 200 to 250 feet. The nose of the airplane pitched down and the airplane collided with terrain. Examination of the flight control system and engine assembly revealed no evidence of a precrash mechanical failure or malfunction.
Probable cause
The loss of engine power for undetermined reasons, and the pilot's failure to maintain airspeed resulting in an inadvertent stall., in-flight collision with terrain, and subsequent nose over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA00LA152
- Event ID
- 20001212X21067
- Case number
- MIA00LA152
- 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, coordinates. 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: 623de73de1255a4976ba4a598c037edaf98d56c91596c6958a058adca0cc2660; retrieved 2026-09-21T10:39:35.752Z.