ENG17WA007 · Boeing 767 300ER
Boeing 767 300ER · Incident: loss of engine power (total) during initial climb
Event
- NTSB case
- ENG17WA007
- 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
- Unknown · led by another country; figures from NTSB notifications
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- 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
- Unknown
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Not recorded
Boeing 767 300ER
- Aircraft type
- Boeing 767
- 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
- 4X-EAM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- Not recorded
- 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
- Defining eventThe 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
- Loss of engine power (total)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Not recorded
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
On Dec. 21, 2016, an ElAl Boeing 767-300ER, powered by Pratt & Whitney PW4000 turbofan engines, registration number 4X-EAM, while climbing through 13,000 ft. from Pearson International Airport (YYZ), Toronto, Canada, experienced a loss of power of the right hand engine with associated vibrations and a subsequent yawing motion of the airplane. It was reported that passengers saw fire from the engine. The engine was shut down and the airplane landed uneventfully at YYZ.
The State of Israel Ministry of Transport, Aviation Incidents & Accidents Investigation is investigating the incident. As the state of manufacture of the airplane and engines, the NTSB has designated a U.S. Accredited Representative under the provisions of Annex 13 to the Convention of Civil Aviation to assist the AI in their investigation.
All inquiries concerning this accident should be directed to the State of Israel Ministry of Transport, Aviation Incidents & Accidents Investigation.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ENG17WA007
- Event ID
- 20161221X11609
- Case number
- ENG17WA007
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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.
- No bulk values were replaced by the NTSB case API.
- The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: 4bae294be6d179cf87a0477a29ebf5e86c1f662474a0376a3f88e1c01075fca1; retrieved 2026-09-16T04:54:29.801Z.