Casualties unknown

2002-10-19: Boeing 767-222 (N607UA) — Boston, MA

Boston, MA, US

On October 19, 2002, a Boeing 767-222 (registration N607UA) was involved in an aviation accident near Boston, MA. Investigators recorded the probable cause as: An inadvertant collision with birds during the initial climb out. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive; 5 related events involving the same aircraft type or operator are linked below.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 1781061362Data APIEditorial standards
Aircraft registered N607UA
Aircraft registered N607UA. Photo: Aero Icarus from Zürich, Switzerland / CC BY-SA 2.0, via Wikimedia Commons

A Boeing 767 struck three birds during takeoff from runway 22, ingesting one into the #2 engine. The aircraft returned and landed uneventfully with damage to the wing, landing light, and engine.

Incident Details

A Boeing 767 struck three birds during its initial climb from runway 22. One double-crested cormorant was ingested by the #2 engine, another struck the right wing, and a third bird was found seriously injured on the runway. The airplane returned to the airport and landed without further incident.

Damage Assessment

Post-flight examination revealed damage to the right inboard leading edge slat, the landing light, and the #2 engine bypass stator vanes.

Wildlife Hazard Management

A review of the airport's Wildlife Hazard Management Plan indicated that earlier that morning, two wildlife technicians reported "heavy bird activity" to the control tower. The airport's Automated Terminal Information System (ATIS) was updated to reflect the hazard and remained active at the time of the incident.

Prior to the airplane's takeoff, one of the wildlife plan supervisors reported a flock of birds to the control tower, stating they were flying about 200 feet over the approach end of runway 15, moving southbound. A tower controller acknowledged that the birds were in sight. Shortly thereafter, another airplane departed runway 22 without incident, followed by the incident airplane.

Air Traffic Control Communications

A review of air traffic control communications revealed that no specific warning was given to either crew, as the birds were not in their flight path. It was believed that the flock split into two or three separate flocks after the other airplane took off, with one flock turning east and directly into the path of the incident airplane.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20030423X00550. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.