ATL00LA083 · Douglas DC-3
Douglas DC-3 · Accident: on ground/water collision with object while taxiing
From Golosón International Airport (MHLC) to Key West International Airport (EYW)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ATL00LA083
- 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
Douglas DC-3 Narrative disagrees
- Aircraft type
- Douglas DC-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
- N79MA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Golosón International Airport (MHLC), HONDURUSTo Key West International Airport (EYW)
- 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
- Taxi · from runway
- 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
- On ground/water collision with object
- 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
- Landing gear, normal brake system › Failure
- Pilot in command › Aircraft control, not possible
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, after exiting the runway, he taxied normally to the U.S. Customs service ramp. Upon attempting to turn right at the Customs Ramp, no right brake function was available. The pilot said that due to the close proximity of other aircraft, differential power was not an option. The pilot stated that he cut the magnetos and tried to gently brake with the left brake. He said the left wing struck a parked Beech-18, damaging the upper engine nacelle and propeller. He said that the impact caused the airplane to continue to the left until the right propeller not rotating struck the left wing of the same Beech-18. Examination of the right brake found that the right expander tube had failed. As a result, the pilot was unable to stop the airplane before colliding with a parked and unoccupied Beech 18.
Probable cause
Failure of the right brake expander tube which limited the pilots control of the aircraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL00LA083
- Event ID
- 20001212X21651
- Case number
- ATL00LA083
- 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: 79785e80b3e44b28c181d0ab8bf64c07a602b58d4b0b7289b9beead0a81d1384; retrieved 2026-09-22T12:32:13.751Z.