ASA Embraer EMB-110P accident
Embraer EMB-110P · Accident: total loss of engine power (mechanical failure) during initial climb
From an unrecorded airport to Dallas Fort Worth International Airport (DFW)
Event
- NTSB case
- DCA88MA059
- 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
- 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
Embraer EMB-110P
- Aircraft type
- Embraer EMB-110
- 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
- N65DA
- Operator
- ASA
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Dallas Fort Worth International Airport (DFW), Fort Worth, TX
- 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
- Initial climb
- 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
- Total loss of engine power (mechanical 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 › Directional control, not maintained
- Pilot in command › Emergency procedure, improper
Approximate · Estimated position: the centre of Lawton, OK, the place the record names. Not the accident site.
NTSB narrative
THE NUMBER 1 (LEFT) ENGINE FAILED DURING THE TAKEOFF FROM RUNWAY 35. IT WAS REPORTED THAT THE AIRCRAFT YAWED SHARPLY LEFT AND CLIMBED TO BETWEEN 50 AND 100 FEET AGL BEFORE IT BEGAN LOSING ALT. THE AIRCRAFT STRUCK THE GROUND AND CONTINUED TO MOVE FORWARD ON THE GROUND SEVERAL HUNDRED FEET UNTIL IT STRUCK THE AIRPORT PERIMETER FENCE. THE AIRCRAFT CAME TO REST 1,600 FEET WEST OF THE RUNWAY, ON A HEADING OF 290 DEGREES. A POST-CRASH FIRE DESTROYED THE CARGO AREA OF THE AIRCRAFT. EXAMINATION OF THE NO. 1 ENGINE REVEALED A COMPRESSOR TURBINE BLADE AIRFOIL SEPARATION. DISASSEMBLY OF THE PROPELLER ON THE NO. 1 ENGINE INDICATED THAT THE PROPELLER HAD AUTOFEATHERED NORMALLY AFTER THE ENGINE FAILED. THE CAPTAIN REPORTEDLY MADE THE TAKEOFF.
Probable cause
NONE SUBMITTED
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA88MA059
- Event ID
- 20001213X25662
- Case number
- DCA88MA059
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: 821de4fc9de269735dfd86af9871ccfef979370e4523969c45c12a6a6b4ab287; retrieved 2026-09-18T19:21:55.924Z.
- The NTSB's operator name is blank for N65DA; the operator shown is the name the NTSB records it doing business as.