FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MBD Beech 18G accident

11 Dec 1996 · ROOSEVELT ROADS, PR, United States

Beech 18G · Accident: airframe, component or system failure en route

From Luis Munoz Marin International Airport (SJU) to José Aponte de la Torre Airport (NRR)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
MIA97LA036
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
1 · 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
Charter & commuter
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

Beech 18G

Aircraft type
Beechcraft 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
N353T
Operator
MBD
Onboard fatalities
Unknown
Route Possible conflict
From Luis Munoz Marin International Airport (SJU), San Juan, PRTo José Aponte de la Torre Airport (NRR)
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 135: Air Taxi & Commuter
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
Airframe, component or system failure
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 › Planning/decision, improper

Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.

NTSB narrative

At 1136 AST, the twin engine airplane departed San Juan, PR, on a flight to St Vincent. About 1208 AST, the pilot contacted ATC and indicated that he would like to divert to St Thomas. He informed the controller that he had 'feathered' the left engine due to loss of the left engine cowling, but he did not declare an emergency. He requested wind information for St Thomas, then at about 1613 AST, he changed his destination to Roosevelt Roads, PR. At 1120 AST, the pilot reported that the airplane was losing about 300'/min, then about 1 minute later, he said he was going to attempt an engine restart, and that the airplane was getting close to the water. A short time later, he informed ATC that he was not going to make it to shore. The pilot acknowledged info that search and rescue personnel were responding, then there was not further contact with the airplane. The airplane was located about 6 miles east of Roosevelt Roads NAS, but the pilot was not found. Review of weight and balance info revealed the pilot did not follow written procedures, and that the airplane exceeded the maximum authorized gross weight for take off. Flight crews had been informed of a communique from the manufacturer that there was no need to shut down an engine and feather the propeller unless engine performance or a major vibration problem confirmed the need.

Probable cause

The pilot's improper planning/decision concerning separation of the left engine cowling. Factors relating to the accident were: the pilot's failure to perform weight and balance calculations, and/or to ensure the airplane was loaded in accordance with company procedures and the airplane flight manual; loss of the left engine cowling for undetermined reasons; and the pilot's decision not to follow written procedures by intentionally shutting down the left engine and feathering the propeller.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA97LA036
Event ID
20001208X07211
Case number
MIA97LA036
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: 5b8517b5946de4227776e50bb938a40a141058be29551c5ebce65f54d15f1350; retrieved 2026-09-18T13:32:08.074Z.