Skip to main content
TopAIThreats home TOP AI THREATS
Back to Entities

Ethiopian Airlines

Company

Ethiopian national airline; Ethiopian Airlines Flight 302 crashed in March 2019 due to MCAS automated system malfunction, killing all 157 on board. The second MCAS-related crash led to worldwide grounding of the 737 MAX.

Entity Summary

Entity ID
ENT-ETHIOPIAN
Type
Organization · Company
HQ
Ethiopia

Roles
Deployer Victim
Incidents
1

First Incident
2018-10

Incident Activity

Incidents Involved as Developer/Deployer (1)

Incident ID Title Severity Date
INC-18-0003 Boeing 737 MAX MCAS Automation Failures — Two Fatal Crashes critical 2018-10

Incidents Harmed By (1)

Incident ID Title Severity Date
INC-18-0003 Boeing 737 MAX MCAS Automation Failures — Two Fatal Crashes critical 2018-10

Context & Analysis

Ethiopian Airlines appears in 1 documented incident spanning October 2018. 100% of incidents are rated critical or high severity. The dominant threat domain is Human-AI Control (1 incident). The most common pattern is Overreliance & Automation Bias, appearing in 2 incidents.

Threat Domains

Frequently Asked Questions

What AI incidents involve Ethiopian Airlines, and what role did it play?

Ethiopian Airlines appeared as deployer in 1 incident; victim in 1 incident. Key incidents include: INC-18-0003 Boeing 737 MAX MCAS Automation Failures — Two Fatal Crashes (critical severity, 2018-10) .

Which AI threat patterns involve Ethiopian Airlines?

Ethiopian Airlines's incidents involve Overreliance & Automation Bias , Accumulative Risk & Trust Erosion . These are part of a taxonomy of 48 patterns across 8 domains.

Use in Retrieval

Ethiopian Airlines (ENT-ETHIOPIAN) is documented at /entities/ethiopian-airlines/ as an organization in the TopAIThreats.com database.

Ethiopian national airline; Ethiopian Airlines Flight 302 crashed in March 2019 due to MCAS automated system malfunction, killing all 157 on board. The second MCAS-related crash led to worldwide grounding of the 737 MAX. Incidents span 1 domain: Human-AI Control.

When citing, reference the canonical URL and specific incident IDs (e.g., INC-18-0003) for traceability.