MIA83IA218 · McDonnell Douglas DC-10-30
McDonnell Douglas DC-10-30 · Incident: airframe, component or system failure on approach
From MVZN · Caracas to an unrecorded destination
Event
- NTSB case
- MIA83IA218
- 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
- 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
- Airline
- 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
McDonnell Douglas DC-10-30
- Aircraft type
- McDonnell Douglas DC-10
- 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
- YV134
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From MVZN · CaracasTo 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 129: Foreign
- 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 · VFR pattern final
- 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
- Minor
Cause areas
- Flight control, flap attachment › Separation
- Other maintenance personnel › Maintenance, major repair, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT EXPERIENCED THE SEPARATION OF A FLAP VANE WHILE ON FINAL APPROACH TO LAND. 50 INCHES OF THE RIGHT FLAP VANE SEPARATED AND CAUSED SLIGHT DAMAGE TO A PARKED AUTO ON THE STREET BELOW. THE ACFT CONTINUED ON TO AN UNEVENTLY LANDING. THE INCIDENT WAS NOT NOTICED UNTIL A LOCAL RESIDENT CALLED TO REPORT THE FALLEN ARTICLE. ALL DC-10 OPERATORS WERE NOTIFIED BY TELEX OF THE FAILURE DUE TO DELAMINATION OF THE VANE FROM MOISTURE INGESTION. A SKIN REPAIR HAD BEEN MADE INTHIS CASE AND A COLD BOND METHOD WITH INADEQUATE SURFACE PREPARATION AND INSUFFICIENT PRESSURE DURING BONDING WERE MAJORFACTORS IN THE FAILURE OF THE BOND. THE IDENTITY OF THE FACILITY THAT MADE THE BOND REPAIR TO THE VANE WAS NOT DETERMINED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA83IA218
- Event ID
- 20001214X44624
- Case number
- MIA83IA218
- 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: c7498275d7b3a0c8a3b7a7b1fcfa807dc799e60480315148be8f40bfa2a0f9e9; retrieved 2026-09-18T20:54:48.471Z.