All Nippon Airways Flight 9397
Boeing 787 10 and Breeze Airways Airbus Canada LP BD-500-1A11 · Accident: ground collision while taxiing
Event
- NTSB case
- DCA25LA267
- 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
- Event fatalities
- Unknown
- 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
- 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
Aircraft 1 · Boeing 787 10
- Aircraft type
- Boeing 787
- 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
- JA986A
- Operator
- All Nippon Airways
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Los Angeles International Airport (LAX), Los Angeles, CA
- Aircraft age
- Built the same year (2025)
- 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
- 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
Aircraft 2 · Airbus Canada LP BD-500-1A11
- Aircraft type
- Airbus Canada LP BD-500
- 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
- N247BZ
- Operator
- Breeze Airways
- Onboard fatalities
- Unknown
- Route
- From Las Vegas, NVTo not recorded
- Aircraft age
- Built the same year (2025)
- 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 121: Air Carrier
- 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
- Standing
- 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
- Personnel issues › Action/decision
- Personnel issues › Experience/knowledge
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
All Nippon Airways flight 9397, JA986A, a Boeing B787-10, collided with Breeze Airways flight 509, N247BZ, an Airbus Canada BD-500-1A11 (A220), while taxiing for takeoff at Charleston International Airport (CHS), Charleston, South Carolina. There were no crew injuries and two minor passenger injuries onboard N247BZ and no injuries to crew onboard JA986A. The left wingtip of NH9397 contacted the rudder of the N247BZ, resulting in substantial damage to both airplanes. Breeze Airways flight 509 was scheduled to operate from Harry Reid International Airport (LAS), Las Vegas, Nevada, to Norfolk International Airport (ORF), Norfolk, VA. Due to weather in the vicinity of ORF, the flight crew of flight 509 coordinated with the Breeze Airways dispatch team and a decision was made to divert to CHS. Dispatch coordinated with the ground service provider and CHS airport operations and was granted permission for flight 509 to park on the remain overnight (RON) ramp, spot R1, see figure 1.
Figure 1. Excerpt of Jeppesen 10-9 Airport Diagram Chart. After landing, the N247BZ flight crew taxied to the RON ramp and was marshalled by ground personnel into spot R6. After shutting down the engines and starting the auxiliary power unit, the flight crew observed ground personnel approaching with air stairs and turned OFF the fasten seatbelt sign. The captain opened the cockpit door and used the public address (PA) system to inform the passengers of the plan to refuel. Upon returning to the cockpit, the ground personnel contacted the flight crew and stated they needed to reposition the aircraft to allow a Boeing aircraft to taxi behind them. At that time, the captain turned the seatbelt sign ON, coordinated with the flight attendants, and made a PA announcement for the passengers to return to their seats for aircraft movement. The captain kept the parking brake engaged while waiting for passengers to be seated and the ramp personnel connected the tug. At that time, the flight crew felt the aircraft suddenly and violently “jolt”. The captain queried the ground personnel and was informed that the wing of JA986A hit their tail. JA986A was a ferry flight from CHS to Tokyo International Airport (HND), Tokyo, Japan, with a stop at Los Angeles International Airport (LAX), Los Angeles, California. The flight crew consisted of two captain qualified pilots; the pilot flying (PF) was seated in the left seat, and the pilot monitoring (PM) was seated in the right seat. The PF had operated out of CHS before, but at a different time of day. The PM had not flown out of CHS. The JA986A flight crew reported they received clearance to taxi to runway 15 via taxiway M. While taxiing on taxiway M, the flight crew observed good visibility but noted that it was dark and there was no taxiway centerline lighting guidance. The flight crew observed N247BZ parked ahead of them, facing West in the RON parking area (nose in), and the other airplanes were parked facing East (tail in). The flight crew assumed that the aircraft was parked for the night and was positioned in a “normal” parking spot, however as they taxied closer to the parked airplane, they thought it was “closer than normal”. The PF stated he was going to offset to the right, “just to be safe”. The PM indicated that he was attempting to monitor the right wing, by pressing his face against the windshield. While passing behind N247BZ, the flight crew felt a light vibration, similar to taxiing over an uneven surface. The JA986A flight crew stopped the airplane and requested airport personnel inspect their wing for potential damage, see figures 2 and 3.
Figure 2. Photograph of N247BZ (left) and JA986A (right) after the collision. (Source: Breeze Airways)
Figure 3. The left photo shows the damage to the vertical stabilizer and rudder of N247BZ The right photo shows the damage to the left wing on JA986A. (Source: Breeze Airways) JA986A sustained damage to the left raked wing tip and removable tip assembly. The removable wing tip is not considered a primary structure however the upper and lower panels of the raked wing tip are, and this damage adversely affects the structural strength requiring a major repair or replacement. Therefore, this was considered substantial damage. Charleston Regional Aviation Authority (CRAA) provided a RON ramp parking diagram, which indicated that all odd numbered parking spots were to be tail-in parking spots and R1 was designed to hold an A220 airplane. All even spots were to be nose-in parking spots and R6 was designated for smaller airplanes. The diagram also depicts a clearance line, indicating the boundary of the ramp area and taxiway M. Photographs provided by the CRAA depicted the nose gear of N247BZ on the lead-in line to spot R6 and main landing gear beyond the clearance line, see figures 4 and 5.
Figure 4. Excerpt of CHS RON parking diagram. (Source: CRAA)
Figure 5. N247BZ nose wheel positioned prior to the RON ramp spot R6 stop bar. (Source: CRAA) A postaccident review was conducted between Breeze Airways, CRAA, and the ground service provider. According to Breeze Airways, the ground service provider manager elected to park N247BZ on R6 due to ramp spacing for ground service equipment and the fuel truck. Additionally, they had previously parked an A220 on R6 for “gas and go” situations and had no issues. Prior to arrival, ground personnel had not cleared the ramp area of equipment and stopped the airplane with the tail beyond the ramp clearance line. Furthermore, N247BZ flight crew were unfamiliar with the RON ramp and the appropriate orientation of airplanes. They stated that the Jeppesen charts did not indicate parking directions, only spot locations. Lastly, CHS airport operations did not have prior knowledge of Boeing aircraft movements, therefore they were unaware of the potential for traffic on taxiway M.
Probable cause
The ground crews improper parking of N247BZ, which left its tail protruding into the taxiway, and the JA986A flight crew’s failure to maintain adequate clearance while taxiing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA25LA267
- Event ID
- 20250719200574
- Case number
- DCA25LA267
- 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, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2025-07-19.
- API snapshot SHA-256: bf9c0f677397c99988fb4e1705e5e59bc553e3b30b79838b091bab6ee9a9d4e8; retrieved 2026-09-13T18:50:09.352Z.