MIA01IA110 · Douglas DC3A
Douglas DC3A · Incident: loss of engine power on approach
From Luis Munoz Marin International Airport (SJU) to an unrecorded destination
Event
- NTSB case
- MIA01IA110
- 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
- Incident
- 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
- Unknown
- 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
Douglas DC3A
- Aircraft type
- Douglas DC3
- 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
- N19BA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Luis Munoz Marin International Airport (SJU), San Juan, PRTo 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
- Approach · IFR missed approach
- 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
- Minor
Cause areas
- Pilot in command › Wrong propeller feathered, inadvertent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight crew stated that while making a missed approach after a practice instrument landing system approach, the right engine failed. The captain took control of the airplane from the copilot. The captain stated that while he performed the emergency procedures for engine failure, he noticed the left engine was not producing power. He then made a forced landing in water east of the airport. He stated that just before impact, he feathered the left propeller. The copilot stated he observed the captain activate the propeller feathering button for the left engine as he performed the emergency procedures for the right engine failure. The reason for failure of the right engine was not determined.
Probable cause
The captain's activation of the left propeller feathering button after failure of the right engine for undetermined reasons resulting in loss of all engine power and the airplane making a forced landing in water.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA01IA110
- Event ID
- 20010410X00726
- Case number
- MIA01IA110
- 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: 3a90ae0e5148ff5b6a0be35f64b45460748da849b7dbe5d315190345e8f70927; retrieved 2026-09-22T12:03:24.785Z.