Qatar Airways Group Q.J.S.C Flight 8141
Boeing 777 FDZ · Accident: ground collision while taxiing
From Hartsfield Jackson Atlanta International Airport (KATL) to an unrecorded destination
Event
- NTSB case
- DCA22LA175
- 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
- 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
Boeing 777 FDZ
- Aircraft type
- Boeing 777
- 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
- A7-BFH
- Operator
- Qatar Airways Group Q.J.S.C
- Onboard fatalities
- Unknown
- Route
- From Hartsfield Jackson Atlanta International Airport (KATL), Atlanta, GATo 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
- Taxi · from runway
- 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
- Ground collision
- 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
- Organizational issues › Development
- Personnel issues › Experience/knowledge
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Qatar Airways flight 8141 struck a light pole with its right wingtip while taxing to parking at Chicago O’Hare International Airport (KORD), Chicago, Illinois. The 2 pilots on board were uninjured, and the airplane was substantially damaged. The non-scheduled international cargo flight was operating under the provisions of 14 Code of Federal Regulations Part 129 from Hartsfield-Jackson International Airport (KATL), Atlanta, Georgia, to KORD. After landing runway 10C at KORD, the tower controller instructed the accident airplane to taxi off the runway via taxiway F followed by a left turn onto taxiway P, and to contact ground on 121.75. The ground controller verified the flight was cargo and instructed the aircraft to continue to taxiway CC and hold short of runway 10L. Shortly after the hold, they were cleared to cross runway 10L, instructed to hold short of taxiway K, and told to contact ground on 121.9. According to air traffic control (ATC) audio, the ground controller instructed the accident airplane to turn left on taxiway K and taxi via taxiway BB to taxiway BB2 to taxiway Z. While taxiing down taxiway BB2, the right wingtip contacted a light pole in the central deicing area adjacent to the taxiway.
Figure 1. Airport diagram zoomed into the area of aircraft collision with light pole - with taxi route (green line) and accident location (yellow star) superimposed onto the airport map. The Qatar Airways crew had access to information on the taxi limitations on taxiway BB2. The FAA chart supplement valid for the time of the accident stated in the airport remarks on the 2nd page that taxiway BB2 was closed “to wingspan more than 118 ft.” Additionally, an airport notice to air mission (NOTAM), valid at the time of the accident, designated that taxiway AA between taxiway K and taxiway U as a non-movement area between June 5 and October 15, 2022. The crew reported reviewing NOTAMs prior to leaving their departure airport and the captain was referencing the airport diagram on his electronic flight bag during the taxi since this was his second time at the airport and the first time for the first officer. Taxiway BB2 was on the southern border of the central deicing facility for the airport. The area on taxiway BB2 where the accident occurred (between taxiway Z and taxiway AA) was considered a non-movement area as part of the central deicing facility and was not to be used to route taxiing aircraft. Facility SOPs noted that “all non-movement areas will be depicted on the ASDE-X as a restricted trait area (YELLOW BOX)” At the time of the accident, the ASDE-X depicted a yellow restricted trait area for the central deicing pad, however the restricted area on the display did not extend to taxiway BB2, despite the taxiway’s classification as a non-movement area.
Figure 2: Screen capture zoomed into the area of impact at the time of event from the FAA legal recording playback of the ASDE-X display processor. The accident aircraft is shown as an orange airplane symbol, and the restricted trait area is shown within the hashed yellow box. (Source: FAA)
Probable cause
The ground controller’s inappropriate routing of the B777 through a non-movement area, resulting in the airplane’s right wingtip contacting a light pole. Contributing to the accident was the lack of an appropriate display of taxiway BB2 as a restricted movement area on the ASDE-X and the flight crew’s acceptance of ATC instruction that was contrary to NOTAM information.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA22LA175
- Event ID
- 20220808105684
- Case number
- DCA22LA175
- 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.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2022-08-06.
- API snapshot SHA-256: a7f5f2de3d39fd2af610d46b87f9a5f0d19366f3aedd118273b7f8ccc9bf628b; retrieved 2026-09-16T15:35:12.439Z.