# NTSB DCA24FA299: Airbus A350-941, N503DN, College Park, GA, September 10, 2024 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Class 3 · Field · Preliminary report - Date: September 10, 2024, 10:07 local (14:07 UTC) - Place: College Park, GA - Coordinates: 33.6367, -84.428101 - Nearby events: https://openairdocs.org/map.md?lat=33.6367&lon=-84.4281&mi=10 - Phase of flight: [Taxi](https://openairdocs.org/ntsb-phases/250) (OpenAirDocs' grouping) - Defining event: [Taxi-to runway: Ground collision](https://openairdocs.org/ntsb-events/200) - Highest injury: Minor injuries - Injuries: 1 minor, 295 uninjured - Status: Investigation ongoing - Investigation class: Class 3 - NTSB office: Major Investigations Division - Parties: FAA AVP, Endeavor Air, Delta, ALPA - NTSB case key (mKey): 195092 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=DCA24FA299 - NTSB preliminary report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/195092/pdf - Page: https://openairdocs.org/ntsb/DCA24FA299 ## Preliminary report (aircraft 1) 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 totaxi 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 Airfacility. Figure 3. Image showing the distance from the hold short line to the nose landing gear of the CRJ. The investigation continues. ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Taxi-to runway: Ground collision](https://openairdocs.org/ntsb-events/200) (defining event), aircraft 1; cases with it: [Airbus A350-941, 1 case](https://openairdocs.org/ntsb-events/200/sequence.md?model=3940315), [All aircraft, 618 cases](https://openairdocs.org/ntsb-events/200/sequence.md) ## Aircraft 1 - Registration: [N503DN](https://openairdocs.org/aircraft/N503DN), registered now, S/N 0149, built 2017 (OpenAirDocs) - Reported make and model: AIRBUS A350-941 - Registry model: [Airbus A350-941](https://openairdocs.org/model/airbus-a350-941) (registry code 3940050) (OpenAirDocs) - Registry engine: [Rolls-Royce TRENT XWB-84](https://openairdocs.org/engine/rolls-royce-trent-xwb-84) (registry code 54599, turbo-fan) (OpenAirDocs) - Category: Airplane - Serial number: 0149 - Year built: 2017 - Airframe hours: 30202 - Damage: Minor damage - Flight: Part 121 - Operator: Delta Air Lines Inc - Registered owner: Delta Air Lines Inc - Airworthiness certificate: Standard, Transport - Last inspection: Continuous airworthiness, September 9, 2024 - Destination: HND, Tokyo - Flight plan: IFR - Airport: KATL, Hartsfield-Jackson Atlanta International Airport, runway 08R, 9,999 × 150 ft, concrete - Equipment: Angle of attack indicator, ADS-B, Stall warning system, Onboard weather, Electronic primary flight display, Electronic multifunction display, Electronic flight bag or handheld device, Data recorder, Auto-pilot ## Aircraft 2 - Registration: [N302PQ](https://openairdocs.org/aircraft/N302PQ), registered now, S/N 15302, built 2014 (OpenAirDocs) - Reported make and model: Mitsubishi Heavy Industries (MHI)/Bombardier CL600 2D24-900 - Registry model: [Bombardier CL-600-2D24](https://openairdocs.org/model/bombardier-cl-600-2d24) (registry code 1390016) (OpenAirDocs) - Registry engine: [GE CF34-8C5](https://openairdocs.org/engine/ge-cf34-8c5) (registry code 30050, turbo-fan) (OpenAirDocs) - Category: Airplane - Serial number: 15302 - Year built: 2014 - Airframe hours: 23050 - Damage: Substantial damage - Flight: Part 121 - Operator: Endeavor Air Inc, doing business as Delta Connection - Registered owner: Bank Of Utah Trustee - Airworthiness certificate: Standard, Transport - Last inspection: Continuous airworthiness, September 7, 2024 - Destination: LFT, Lafayette, LA - Flight plan: IFR - Equipment: Auto-pilot, Data recorder, Electronic flight bag or handheld device, Electronic multifunction display, Electronic primary flight display, Onboard weather, Stall warning system, ADS-B, Angle of attack indicator ## Weather - Conditions: Visual (VMC), Not reported - Wind: 60° at 5 knots - Visibility: 11.5 statute miles - Lowest ceiling: none - Temperature: 72 °F, dew point 63 °F - Altimeter: 30.16 inHg - Observed at: KAIL ## FAA reports on this event (2) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20240910018582A](https://openairdocs.org/incident/20240910018582A), Sep 10, 2024: Airbus A350-941, College Park, GA, Minor damage. On September 10, 2024, about 1007 eastern daylight time, [privacy data omitted], an Airbus A350-941, [privacy data omitted], collided with [privacy data… - [Accident 20240910017772A](https://openairdocs.org/incident/20240910017772A), Sep 10, 2024: Bombardier Inc CL-600-2D24, College Park, GA, Substantial damage. On September 10, 2024, about 1007 eastern daylight time, [privacy data omitted], an Airbus A350-941, [privacy data omitted], collided with [privacy data… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.