# Accident 19960606045452A: Boeing 767223, San Francisco, CA, June 6, 1996

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 6, 1996, 22:05 local time
- Place: San Francisco, CA
- Airport: San Francisco International
- Damage: Minor damage
- Collision: Midair collision, second aircraft
- Phase of flight: Other Ground Ops
- Operating rules: Air carrier (Part 121)
- Operator: AALA
- Location: 37.6098° N, 122.3807° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=37.6098&lon=-122.3807&mi=10
- Aircraft: N335AA, a cancelled registration (https://openairdocs.org/deregistered/N335AA-2015-12-09) (OpenAirDocs)
- Registry model: Boeing 767-223 (registry code 1385123, https://openairdocs.org/model/boeing-767-223) (OpenAirDocs)
- Registry engine: GE CF6-80 series (registry code 30025, https://openairdocs.org/engine/ge-cf6-80-series) (OpenAirDocs)
- Reported make and model: BOEING 767223
- Reported engine: GE CF680A
- People aboard: 165
- Fatal injuries: 0
- Pilot flight hours: 25,000 total, 2,942 in this make and model
- NTSB investigation: [NTSB LAX96LA222](https://openairdocs.org/ntsb/LAX96LA222) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960606045452A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(.4)AT NIGHT, A TAIL-TO-TAIL GROUND COLLISION OCCURRED IN AN ALLEYWAY BETWEEN AN OUTBOUND UNITED BOEING 737, N371UA, AND AN OUTBOUND AMERICAN BOEING 767, N335AA. AT THE TIME, THE B-737 WAS UNDER TUG CONTROL WHILE BEING PUSHED BACK WITHOUT THE AID OF WING WALKERS FROM GATE NUMBER 77.  THE UNITED B-767 WAS BEGINNING TO TAXI FROM THE SAME ALLEYWAY FOLLOWING ITS EARLIER UNEVENTFUL PUSHBACK WITH THE AID OF WING WALKERS FROM GATE NUMBER 63.  ACCORDING TO THE B-737'S TUG DRIVER, DURING PUSHBACK SHE HAD OBSERVED A NEARBY FOOD SERVICE TRUCK AND HAD INITIALLY SLOWED HER SPEED TO ENSURE ITS PASSAGE. THEREAFTER, SHE CONTINUED PUSHING THE B-737 TOWARD THE DESIGNED ALLEYWAY LOCATION.  SUDDENLY, AN IMPACT OCCURRED AND THE TUG DRIVER FOR THE FIRST TIME OBSERVED AN AMERICAN B-767 WAS ALREADY LOCATED IN THE ALLEYWAY.  UNITED MANAGEMENT REPORTED THAT DURING PUSHBACK OPERATIONS IT WAS THE TUG DRIVER'S RESPONSIBILITY TO ENSURE THAT ADEQUATE CLEARANCE EXISTED.  NINE MONTHS EARLIER UNITED MANAGEMENT WAS AWARE THAT AIRCRAFT UTILIZING ITS GATE NUMBER 77 DID NOT HAVE THE MINIMUM 25-FOOT AIRCRAFT WING TIP CLEARANCE AS REQUIRED BY THE CITY OF SAN FRANCISCO.  CITY PERSONNEL AGREED TO ALLOW UNITED GATE USAGE P ROVIDED UNITED 'GUARANTEE THE USE OF WING WALKERS'.

## Other aircraft in the event

- N371UA, Boeing 737322: [Accident 19960606045451A](https://openairdocs.org/incident/19960606045451A)

## The NTSB's investigation of this event (1)

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.

- [NTSB LAX96LA222](https://openairdocs.org/ntsb/LAX96LA222), Jun 7, 1996: Boeing 767-223 (N335AA), San Francisco, CA, minor damage. Probable cause: inadequate visual lookout by the United Airlines tug driver during the pushback operation. Contributing factors were: the driver's reduced ability to observe the American B-767 due to the nighttime…

## Other reports on N335AA (1)

Matched to the same aircraft by N-number and date.

- [Accident 19980722046529A](https://openairdocs.org/incident/19980722046529A), Jul 22, 1998: Boeing 767223 (N335AA), Peotone, IL. (.4) Moderate turbulence was encountered as the airplane climbed through FL180 while in the clouds. There were no weather returns indicating turbulence nor…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.