FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

JetBlue Airways Airbus A321-231 accident

8 Feb 2024 · Boston, MA, United States

Airbus A321-231 and Airbus A321 · Accident: ground collision while standing

Report a problem

Event

NTSB case
DCA24LA092
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 · Airbus A321-231

Aircraft type
Airbus A321
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
N956JT
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 9 years (built 2015)
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 · engine(s) operating
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 A321

Aircraft type
Airbus A321
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
N2157J
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 1 year (built 2023)
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
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
Minor

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

While taxiing within the Amelia Earhart de-icing pad area, the left sharklet of JetBlue Airways flight 777 collided with the right horizontal stabilizer and elevator of JetBlue Airways flight 551 at the General Edward Lawrence Logan International Airport (BOS), Boston, Massachusetts. There were no injuries to the 210 passengers and crew on flight 551 or the 154 passengers and crew on flight 777.

The flight crew of flight 551 stated that, following a normal preflight and uneventful taxi from the gate to the de-icing pad, they were guided by a “follow me” vehicle operated by JetBlue contractor, Aeromag (see figure 1). The flight crew proceeded to follow the vehicle to the D2 parking spot. A yellow painted “T” inside a black square marked the proper stopping point location for the airplane’s nose tires when parked. Nearing the stopping point, the “follow me” vehicle turned to the right and stopped with its headlights facing toward the back of the airplane. The driver of the “follow me” vehicle communicated with the flight crew via radio and began a “countdown” for when the captain should stop the airplane.

Upon the verbal stop command, the captain stopped the airplane and set the parking brake. After the de-ice procedure was complete, the flight crew received instructions to taxi the airplane to runway 9 for departure. Immediately after releasing the airplane’s parking brake, the flight crew felt jolts and vibrations and the airplane swayed back and forth. The captain set the parking brake and the first officer (FO) contacted air traffic control (ATC) and was informed they had been struck by another aircraft.

Figure 1. Google Earth image showing the ground position tracks of both airplanes.

In a post-accident statement, the driver of the “follow me” vehicle indicated that he stopped the airplane (flight 551) at what he thought was the normal stopping point. He had difficulty seeing the yellow “T” -bar due to the dark night conditions and the de-icing fluid that was present on the ground (figure 2). A post-accident inspection found that the airplane was about 35 ft short of the normal stopping point.

Figure 2. Photograph showing N956JT (JetBlue flight 551) about 35 feet from the yellow “T” bar. (Source: JetBlue)

The flight crew of flight 777 indicated that after a normal preflight and uneventful taxi from the gate to the de-icing pad they were guided to the D1 spot by a “follow me” vehicle. The captain stated spacing appeared to be tight and he focused on the yellow taxi line to ensure proper clearance from other airplanes in the area. Shortly thereafter, while taxiing, the flight crew heard a grinding noise and felt a vibration. While still moving forward, they heard another aircraft on the Aeromag radio frequency ask if something had struck their airplane.

The flight crew of flight 777 stopped their airplane and set the parking brake. The captain had difficulty seeing the left sharklet due to the dark night conditions but noted that it was intact. In addition, he was unable to see the empennage of flight 551 parked at the D2 location as it was behind them.

Flight 551 (N956JT) sustained substantial damage to the left horizontal stabilizer and the left elevator.

As a result of this event, Aeromag investigated and produced a February 12, 2024, memo to their BOS-JBU [JetBlue] operations staff discussing an amendment to the Coordinator of Traffic and Movement (CTM) phraseology and aircraft stopping procedures. The memo outlined the updated procedures and phraseology as: “Follow me” truck is now required to verbally confirm with the flight crew that the aircraft is correctly stopped on the deicing “T”-Bar. JetBlue will add to the Airport Briefing Guide (ABG) that the pilot will not configure the aircraft until confirmation that the aircraft is correctly stopped on the deicing “T”-Bar. The “follow me” truck is required to check the rear of the aircraft to ensure that it is within the bay and clear of the zipper line before confirming brake set. Safety Lead will perform a secondary check, reconfirming with the CTM that the aircraft has stopped on the deicing “T”-Bar. Safety Lead will also verify that the rear of the aircraft is clear of the zipper line and within the bay. Truck positioning and aircraft deicing will commence after these checks have been completed.

Additionally, once CTM has confirmed with the flight crew that they have a visual on the “follow me” truck, the “follow me” truck operator will follow these steps: 1. Guide the aircraft into the assigned bay. 2. Ensure the aircraft is properly stopped on the deicing “T”-Bar. 3. Confirm that the rear of the aircraft is within the bay, clear of the zipper line, before bringing any other aircraft in.

Finally, the Safety Lead will: 1. Inspect and confirm with CTM that the aircraft is properly stopped on the deicing “T”-Bar. 2. Inspect that the rear of the aircraft is well within the bay and clear of the zipper line.

Aeromag also increased its daily roster to include sufficient qualified staff to allocate a Safety Lead dedicated to each operational bay regardless of operating conditions. Long term prevention strategies identified were: Repainting and reviewing the color format of the delineated markings using high-visibility paint and/or reflective inset markers. Investigating the feasibility of adding high mast lighting for the Earhart facility. Operational audits to focus on the correct positioning of aircraft while maintaining the safety buffer zones. Explore opportunities to locate Aeromag tower personnel in elevated positions.

Probable cause

The “follow me” driver stopping the airplane (flight 551) about 35 feet from the normal stopping point due to a difficulty in seeing the yellow “T”-bar because of the dark night conditions and the presence of de-icing fluid on the ground.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA24LA092
Event ID
20240208193765
Case number
DCA24LA092
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: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
  • API snapshot SHA-256: 0764ff9741b01bf53ecc24f353fb0ba825a41978352ba853fb9a3a3e508f1540; retrieved 2026-09-13T18:43:16.081Z.