Epps Air Service Mitsubishi MU-2-60 accident
Mitsubishi MU-2-60 · Accident: airframe, component or system failure en route
From Teterboro Airport (TEB) to Burke Lakefront Airport (BKL)
Event
- NTSB case
- NYC92LA166
- 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
Mitsubishi MU-2-60
- Aircraft type
- Mitsubishi MU-2
- 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
- N66LA
- Operator
- Epps Air Service
- Onboard fatalities
- Unknown
- Route
- From Teterboro Airport (TEB), TETERBORO, NJTo Burke Lakefront Airport (BKL), Cleveland, OH
- 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
- Substantial
Cause areas
- Propeller system/accessories, blade › Fatigue
- Propeller system/accessories, blade › Separation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AT 6000 FEET MSL, WHILE IN CRUISE FLIGHT, A PROPELLER BLADE FROM THE LEFT PROPELLER ASSEMBLY SEPARATED IN-FLIGHT, PENETRATED THE FUSELAGE, BREAKING ELECTRICAL LINES AND CAUSING A LOSS OF ELECTRICAL POWER. AT THE TIME THE AIRPLANE WAS IN IMC, SO THE PILOT ELECTED TO TURN 180 DEGREES IN AN ATTEMPT TO FLY TO AN AREA OF BETTER WEATHER. HE FLEW WITHOUT ELECTRICAL POWER OR MOST OF THE INSTRUMENTS FOR ABOUT 40 MINUTES, UNTIL REACHING AN AREA OF CLEAR WEATHER. ONCE THE PILOT WAS ABLE TO IDENTIFY HIS LOCATION HE ELECTED TO MAKE A GEAR UP LANDING AT THE NEAREST AIRPORT. METALLURGICAL EXAMINATION OF THE SEPARATED BLADE REVEALED THAT THE SEPARATION OF THE BLADE WAS THE RESULT OF FATIGUE CRACKING THAT INITIATED FROM MULTIPLE SITES LOCATED AT CORROSION PITS IN THE BALANCING HOLE. IT WAS DETERMINED THAT THE CORROSION PITTING HAD NOT BEEN DETECTED DURING THE LAST OVERHAUL AND PROCEDURES TO SHOT PEEN AND PAINT THE BALANCING HOLE WERE NOT PERFORMED.
Probable cause
THE IN-FLIGHT SEPARATION OF A PROPELLER BLADE AS A RESULT OF FATIGUE CRACKING INITIATED FROM MULTIPLE SITES LOCATED AT CORROSION PITS IN THE BALANCING HOLE. CONTRIBUTING FACTORS IN THE ACCIDENT WERE: THE FAILURE TO DETECT THE CORROSION DURING THE LAST OVERHAUL PROCEDURE; AND A COMPLETE LOSS OF ELECTRICAL POWER AS RESULT OF THE SEPARATED BLADE BREAKING THE ELECTRICAL LINES.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC92LA166
- Event ID
- 20001211X15511
- Case number
- NYC92LA166
- 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: 3907fba0a24d0b918c433f44fe53984219c076dc41f419bdbe89a52fb0ceadc0; retrieved 2026-09-18T18:44:39.172Z.