FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

United Airlines Flight 1303

24 Mar 2026 · Dulles, VA, United States

Boeing 737-8 · Accident: propeller/jet/rotor blast or suction while taxiing

From an unrecorded airport to Seattle–Tacoma International Airport (KSEA)

Report a problem

Event

NTSB case
DCA26LA164
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

Boeing 737-8

Aircraft type
Boeing 737
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
N17316
Onboard fatalities
Unknown
Route
From not recordedTo Seattle–Tacoma International Airport (KSEA), Seattle, WA
Aircraft age
About 3 years (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 · to 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
Propeller/jet/rotor blast or suction
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Personnel issues › Action/decision
  • Personnel issues › Experience/knowledge
  • Personnel issues › Task performance

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

NTSB narrative

On March 24, 2026, about 1815 eastern daylight time (EDT), United Airlines flight 1303, was involved in an accident while taxiing for departure at Washington Dulles International Airport (IAD), Dulles, Virginia. The 167 passengers and crew onboard were uninjured. One maintenance technician was seriously injured. The flight was operating under Title 14 Code of Federal Regulations Part 121 as a regularly scheduled domestic passenger flight from IAD to Seattle-Tacoma International Airport (SEA), Seattle, Washington. According to the flight crew, preflight preparations were normal, and no abnormalities were observed with either the airplane or ground personnel. The airplane was parked at Gate C6 between two aircraft undergoing preflight and post-flight activities. Departure was delayed several minutes to accommodate connecting international passengers. They were cleared to push back with the airplane's tail-oriented east to facilitate a westbound taxi on taxiway Echo (E), abeam Gate C8. During the pushback, the tug driver made two unsuccessful attempts to properly position the airplane. A nearby ramp worker joined the right-wing walker on the headset communications and appeared to discuss the situation with the tug driver. The captain asked over the intercom if everything was alright. After receiving no response, he repeated the inquiry, and the tug driver advised that they would attempt to reposition the airplane one more time. Following the final repositioning attempt, the airplane remained north of the taxiway E centerline on the terminal side. The flight crew was then instructed to set the parking brake. Before disconnecting the headset, the tug driver stated, "Sorry for the wonky pushback," to which the captain replied, "Glad you figured it out." The ground personnel then moved clear of the airplane, and the marshaller signaled that the area was clear. The captain acknowledged the signal by flashing the taxi light, indicating the airplane was ready to taxi. Air traffic control subsequently cleared the flight to taxi via taxiways E, E2, and F to Spot 86. The captain advanced the thrust levers to breakaway thrust, and the airplane began taxiing. The remainder of the flight was uneventful. According to the pushback driver, before brake release the flight crew instructed him to position the aircraft for a west taxiway departure and align it with taxiway C8. He stated that the pushback was unusual due to construction near gate C2 and the presence of widebody aircraft at adjacent gates. During the maneuver, he had difficulty achieving a 90-degree alignment and was concerned about over-rotating the nose gear. After several attempts, he repositioned the aircraft beyond gate C6 and asked the captain if the aircraft was in position for brake set. Following completion of the pushback, he observed a maintenance technician on the ground near gate C4 and summoned assistance. United Airlines had issued Flight Operations, Ops Alert, Washington Dulles (IAD) Taxiway Echo Construction, Revision 1, that was effective and available to the pilots at the time of the accident (see figure 1). The Ops Alert stated in part: Why: Beginning March 16, the Metropolitan Washington Airport Authority (MWAA) will continue the renovation of Taxiway E to support the Terminal 2 Extension (T2E) project. Construction hours are daily from 2100-1300L. This work will impact access to Gates C2 and C4, prevent entering Taxiway E from the East, and close Taxiway J between Taxiways E and F.

Figure 1. Graphic included in United Airlines Flight Operations, Ops Alert, Washington Dulles (IAD) Taxiway Echo Construction, Revision 1. Airport surveillance video showed the airplane was not released from the tug at the designated location abeam Gate C8 on taxiway E, but rather about abeam Gate C6 and north of the taxiway E centerline. As the airplane began to taxi and turned to position on the taxiway centerline its jet blast was directed toward an airplane parked at Gate C4, see figure 2. Shortly thereafter, a ladder was observed sliding across the ramp’s surface behind the parked airplane's No. 2 (right) engine.

Figure 2. Pushback and taxi illustration based on surveillance video. The yellow dot indicates the approved drop location. (Source: United Airlines) After the flight, the flight crew was informed that a maintenance technician had sustained serious injuries after falling from a ladder displaced by their airplane’s jet blast . Safety Actions Since the accident, United Airlines has implemented the following mitigations to prevent recurrence: A safety standdown was held in station regarding the proper push path related to this gate during the construction period with all pushback qualified personnel. Policy related to the final positioning of aircraft, specifically, that an aircraft must be pushed to a location where jet blast can pose no harm to personnel or equipment was played on ramp information displays throughout employee areas of the station as a reminder of that policy. A revised Ops Alert, requiring Mandatory 2 engine taxi was implemented for the duration of the construction to ensure that engine power settings are kept as low as reasonably practicable.

Probable cause

The tug drivers improper positioning of the airplane during pushback, which resulted in the airplane’s jet blast impacting an active gate area during taxi and the subsequent injury to a maintenance technician. Contributing to the accident was the captain’s decision to accept the tug driver’s incorrect release location.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA26LA164
Event ID
20260325202695
Case number
DCA26LA164
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, cause areas, damage. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: a9d2eeb3d02da89c41ac3234e6465512f22533cfd846fcaac0bf5deef7893095; retrieved 2026-09-16T21:03:25.440Z.