The U.S. aircraft register, updated daily
Accidents · NTSB DCA24FA299 · Preliminary: the investigation is not finished

Airbus A350-941 and Mitsubishi Heavy Industries (M CL600 2D24-900 accident near College Park, Georgia, September 10, 2024

On September 10, 2024 at about 2:07 pm local time, 2 aircraft, Airbus A350-941 (N503DN) and Mitsubishi Heavy Industries (M CL600 2D24-900 (N302PQ), were involved in the same accident near College Park, Georgia (Hartsfield-Jackson Atlanta Int). 1 person had minor injuries; 295 others were unhurt. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 10, 2024 · about 2:07 pm local time
Place
College Park, Georgia · Hartsfield-Jackson Atlanta Int · map
Type
Accident · collision on the ground
Injuries
1 person had minor injuries; 295 others were unhurt.
Weather
visual conditions (good weather)
Aircraft 1
Airbus A350-941, built 2017 · all A350-941s on the register
Registration
N503DN · registry record · serial 0149
Damage
Minor damage
Flight
Flight · scheduled airline rules (Part 121)
Aircraft 2
Mitsubishi Heavy Industries (M CL600 2D24-900, built 2014
Registration
N302PQ · registry record · serial 15302
Damage
Substantial damage
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative for the Airbus A350-941 preliminary · quoted from the NTSB record

On September 10, 2024, about 1007 eastern daylight time, Delta Air Lines flight 295, an Airbus A350-941, N503DN, collided with Endeavor Air flight 5526 (dba Delta Air Lines), a Mitsubishi Heavy Industries (MHI) CRJ-900, N302PQ, while taxiing for departure at Hartsfield-Jackson Atlanta International Airport (ATL), Atlanta, Georgia. (In this report, flight 295 is referred to as the A350 airplane, and flight 5526 is referred to as the CRJ airplane.) The CRJ was holding short of runway 8R on taxiway H waiting for takeoff clearance, and the A350 was taxiing along intersecting taxiway E. As the A350 passed behind the CRJ, where the taxiways intersected, the right wingtip of the A350 impacted the vertical stabilizer of the CRJ, which resulted in substantial damage to the empennage of the CRJ (figure 1) and minor damage to the A350. The passengers and crew aboard both airplanes were not injured except for a flight attendant aboard the CRJ, who sustained a minor injury. The A350 was operating under the provisions of Title 14 Code of Federal Regulations Part 121 as a scheduled international passenger flight from ATL to Tokyo Haneda International Airport (HND), Tokyo, Japan. The CRJ was operating under Part 121 as a regularly scheduled domestic passenger flight from ATL to Lafayette Regional Airport (LFT), Lafayette Parish, Louisiana. In response to this accident, the NTSB traveled to ATL. As part of the investigative process, the NTSB invited qualified parties to participate in the investigation. These parties are the Federal Aviation Administration (FAA), Delta Air Lines, Endeavor Air, and the Air Line Pilots Association (ALPA). The NTSB assigned group chairs in the areas of operations, airworthiness, air traffic control (ATC), aircraft performance, flight data recorder (FDR), and cockpit voice recorder (CVR). The FDR and CVR were retrieved from both airplanes between September 10 and 11, 2024, by aircraft maintenance technicians (AMT) and NTSB personnel. Both CVRs were sent to the NTSB Vehicle Recorder Laboratory on September 13, 2024. The data from both FDRs were downloaded on-site by Delta Air Lines in the presence of NTSB personnel. Figure 1. Photograph showing the CRJ after impact. (Source: Atlanta Airside Operations) HISTORY OF FLIGHT: Four flight crew members consisting of a captain and first officer (FO), a relief captain, and a relief FO were on the flight deck of the A350. The captain was the pilot flying and the FO was the pilot monitoring. According to statements from the flight crew members, the pilot flying briefed the long runway (09L) normally used for heavy aircraft was closed for construction. Therefore, they would be taxiing to, and departing from, runway 8R.    After pushback from the gate, the flight crew received taxi instructions to proceed north on taxiway D, and hold short of taxiway G. They taxied the airplane as instructed and received further instructions to taxi on taxiway G and hold short of taxiway F. They were then cleared to taxi on taxiway F and transition to taxiway E. After the A350 turned onto taxiway E, ground control instructed the flight crew to have the airplane follow the CRJ on taxiway E and switch to tower frequency. As the A350 continued to taxi on taxiway E, the flight crew observed the navigational alert message, “NAV GNSS-2,” on the lower electronic centralized aircraft monitor (ECAM). The FO informed the tower that they would need to stop to coordinate with maintenance before departure. ATC instructed the crew to continue straight ahead on taxiway E as able and hold short of taxiway V to work on the problem. The captain indicated that, as the airplane approached the intersection with taxiway V, he was looking straight ahead and to the left to avoid the left wingtip from impinging on opposite direction traffic coming off taxiway V. At that time, the right wingtip of the A350 impacted the vertical stabilizer of the CRJ, which was holding short of runway 8R at taxiway H. Following the collision, the captain stopped the A350 and set the parking brake. After airport rescue and firefighting (ARFF) examined the exterior of the A350, the crew was given clearance for the airplane to return to the gate. The captain was the pilot flying, and the FO was the pilot monitoring for the CRJ. The flight crew indicated that the airplane pushed back from the gate and that ground control instructed them to taxi to runway 8R via taxiway E. The crew completed the before takeoff checks while on taxiway E, and ATC advised the crew that the A350 would wait for them and monitor the tower frequency for takeoff. The crew reported that they complied with the instructions. The captain indicated that she maneuvered the CRJ to the hold-short line on taxiway H, set the parking brake, and awaited further instruction from ATC. Figure 2 is a Google Earth screenshot that is overlaid with the ground tracks of the A350 (DAL295, the blue line) and the CRJ (EDV5526, the orange line). The white circle shows the location of the collision at the intersection of taxiways E and H. Figure 2. Ground position tracks for DAL295 (A350) and EDV5526 (CRJ) in relation to taxiways E and H. The FAA provided the NTSB with certified ADS-B latitude and longitude data. Analysis of the ADS-B and preliminary FDR data showed the airplanes collided at 10:07:46. The CRJ was stationary, and the A350 was taxiing at a groundspeed of about 12 knots. The CRJ sustained lateral accelerations of 0.5 G left followed by 0.55 G right, and the CRJ’s heading was rotated about 9° clockwise. On September 13, the operations group met at the Delta Air Lines general offices in ATL to interview the flight crews. The airworthiness group examined the accident airplane from September 11 to 13, 2024, in ATL. According to Endeavor, the distance from the hold short line to the nose landing gear of the CRJ was approximately 56 feet (figure 3). The A350 was examined at the Delta Tech Ops facility, and the CRJ was examined at the Endeavor Air facility. Figure 3. Image showing the distance from the hold short line to the nose landing gear of the CRJ. The investigation continues.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The NTSB's narrative for the Mitsubishi Heavy Industries (M CL600 2D24-900 preliminary · quoted from the NTSB record

On September 10, 2024, about 1007 eastern daylight time, Delta Air Lines flight 295, an Airbus A350-941, N503DN, collided with Endeavor Air flight 5526 (dba Delta Air Lines), a Mitsubishi Heavy Industries (MHI) CRJ-900, N302PQ, while taxiing for departure at Hartsfield-Jackson Atlanta International Airport (ATL), Atlanta, Georgia. (In this report, flight 295 is referred to as the A350 airplane, and flight 5526 is referred to as the CRJ airplane.) The CRJ was holding short of runway 8R on taxiway H waiting for takeoff clearance, and the A350 was taxiing along intersecting taxiway E. As the A350 passed behind the CRJ, where the taxiways intersected, the right wingtip of the A350 impacted the vertical stabilizer of the CRJ, which resulted in substantial damage to the empennage of the CRJ (figure 1) and minor damage to the A350. The passengers and crew aboard both airplanes were not injured except for a flight attendant aboard the CRJ, who sustained a minor injury. The A350 was operating under the provisions of Title 14 Code of Federal Regulations Part 121 as a scheduled international passenger flight from ATL to Tokyo Haneda International Airport (HND), Tokyo, Japan. The CRJ was operating under Part 121 as a regularly scheduled domestic passenger flight from ATL to Lafayette Regional Airport (LFT), Lafayette Parish, Louisiana. In response to this accident, the NTSB traveled to ATL. As part of the investigative process, the NTSB invited qualified parties to participate in the investigation. These parties are the Federal Aviation Administration (FAA), Delta Air Lines, Endeavor Air, and the Air Line Pilots Association (ALPA). The NTSB assigned group chairs in the areas of operations, airworthiness, air traffic control (ATC), aircraft performance, flight data recorder (FDR), and cockpit voice recorder (CVR). The FDR and CVR were retrieved from both airplanes between September 10 and 11, 2024, by aircraft maintenance technicians (AMT) and NTSB personnel. Both CVRs were sent to the NTSB Vehicle Recorder Laboratory on September 13, 2024. The data from both FDRs were downloaded on-site by Delta Air Lines in the presence of NTSB personnel. Figure 1. Photograph showing the CRJ after impact. (Source: Atlanta Airside Operations) HISTORY OF FLIGHT: Four flight crew members consisting of a captain and first officer (FO), a relief captain, and a relief FO were on the flight deck of the A350. The captain was the pilot flying and the FO was the pilot monitoring. According to statements from the flight crew members, the pilot flying briefed the long runway (09L) normally used for heavy aircraft was closed for construction. Therefore, they would be taxiing to, and departing from, runway 8R.    After pushback from the gate, the flight crew received taxi instructions to proceed north on taxiway D, and hold short of taxiway G. They taxied the airplane as instructed and received further instructions to taxi on taxiway G and hold short of taxiway F. They were then cleared to taxi on taxiway F and transition to taxiway E. After the A350 turned onto taxiway E, ground control instructed the flight crew to have the airplane follow the CRJ on taxiway E and switch to tower frequency. As the A350 continued to taxi on taxiway E, the flight crew observed the navigational alert message, “NAV GNSS-2,” on the lower electronic centralized aircraft monitor (ECAM). The FO informed the tower that they would need to stop to coordinate with maintenance before departure. ATC instructed the crew to continue straight ahead on taxiway E as able and hold short of taxiway V to work on the problem. The captain indicated that, as the airplane approached the intersection with taxiway V, he was looking straight ahead and to the left to avoid the left wingtip from impinging on opposite direction traffic coming off taxiway V. At that time, the right wingtip of the A350 impacted the vertical stabilizer of the CRJ, which was holding short of runway 8R at taxiway H. Following the collision, the captain stopped the A350 and set the parking brake. After airport rescue and firefighting (ARFF) examined the exterior of the A350, the crew was given clearance for the airplane to return to the gate. The captain was the pilot flying, and the FO was the pilot monitoring for the CRJ. The flight crew indicated that the airplane pushed back from the gate and that ground control instructed them to taxi to runway 8R via taxiway E. The crew completed the before takeoff checks while on taxiway E, and ATC advised the crew that the A350 would wait for them and monitor the tower frequency for takeoff. The crew reported that they complied with the instructions. The captain indicated that she maneuvered the CRJ to the hold-short line on taxiway H, set the parking brake, and awaited further instruction from ATC. Figure 2 is a Google Earth screenshot that is overlaid with the ground tracks of the A350 (DAL295, the blue line) and the CRJ (EDV5526, the orange line). The white circle shows the location of the collision at the intersection of taxiways E and H. Figure 2. Ground position tracks for DAL295 (A350) and EDV5526 (CRJ) in relation to taxiways E and H. The FAA provided the NTSB with certified ADS-B latitude and longitude data. Analysis of the ADS-B and preliminary FDR data showed the airplanes collided at 10:07:46. The CRJ was stationary, and the A350 was taxiing at a groundspeed of about 12 knots. The CRJ sustained lateral accelerations of 0.5 G left followed by 0.55 G right, and the CRJ’s heading was rotated about 9° clockwise. On September 13, the operations group met at the Delta Air Lines general offices in ATL to interview the flight crews. The airworthiness group examined the accident airplane from September 11 to 13, 2024, in ATL. According to Endeavor, the distance from the hold short line to the nose landing gear of the CRJ was approximately 56 feet (figure 3). The A350 was examined at the Delta Tech Ops facility, and the CRJ was examined at the Endeavor Air facility. Figure 3. Image showing the distance from the hold short line to the nose landing gear of the CRJ. The investigation continues.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record for the Airbus A350-941 from the NTSB's investigation tables, in plain English

What happened, in order

  1. Ground collision during taxi (to runway) defining event

The aircraft

  • Airframe total time: 30,202 hours
  • Last inspection: continuous airworthiness programme, September 9, 2024
  • Maximum gross weight: 608,255 lb
  • Seats: 323
  • Landing gear: retractable
  • Operator: Delta Air Lines INC

The flight

  • Destination: HND Tokyo
  • Flight plan: IFR
  • Runway 08R, 9,999 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: not reported
  • Wind: from 060° at 5 knots
  • Visibility: 11.5 statute miles
  • Sky: a few clouds
  • Temperature: 72°F (22°C), dew point 63°F (17°C)
  • Altimeter: 30.16 inHg
  • Observation at 1:52 pm from KAIL

Injuries

FatalSeriousMinorNone
Cabi11
Flight crew4
Passengers221

The factual record for the Mitsubishi Heavy Industries (M CL600 2D24-900 from the NTSB's investigation tables, in plain English

The aircraft

  • Airframe total time: 23,050 hours
  • Last inspection: continuous airworthiness programme, September 7, 2024
  • Maximum gross weight: 84,500 lb
  • Seats: 82
  • Landing gear: retractable
  • Operator: Endeavor Air Inc

The flight

  • Destination: LFT Lafayette LA
  • Flight plan: IFR
  • A second pilot was aboard

Injuries

FatalSeriousMinorNone
Cabi11
Flight crew2
Passengers56

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number DCA24FA299.