IAD03IA007

NTSB incident investigation · Boeing 767-222 · Boston, MA · October 19, 2002

Incident · No injuriesIncident investigationFinal report
Date
October 19, 2002, 08:50 local (12:50 UTC)
Place
Boston, MA
Injuries
128 uninjured
Damage
Minor damage
Phase of flight
Initial climb
Aircraft
N607UABoeing 767-222
Weather
Visual (VMC) · Day
Status
Completed · report August 26, 2003
Report
Approved by Office Director
Parties
BOSTON FSFO
FAA report
20021019030979I
Case key
55984

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the incident.

On this page

Probable cause

An inadvertant collision with birds during the initial climb out.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

In flight collision with objectTakeoff - initial climb
Object - bird(s)Cause

Analysis

The Boeing 767 struck three birds during the initial climb out 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 uneventfully. Examination revealed damage to the right inboard leading edge slat, landing light, and the #2 engine bypass stator vanes. A review of the airport's Wildlife Hazard Management Plan revealed that on the morning of the incident, two wildlife technicians reported "heavy bird activity" to the control tower. The airport's Automated Terminal Information System (ATIS) was then updated to reflect the hazard, and was still active at the time of the incident. Prior to the airplane's take-off, one of the wildlife plan supervisors reported a flock of birds to the control tower and said they were flying about 200 feet over the approach end of runway 15, moving southbound. A tower controller responded that they had the birds in sight. Shortly thereafter, another airplane departed runway 22 without incident, then the incident airplane took off. A review of air traffic control communications revealed that no specific warning was given by the air traffic controllers to either of the crews, due to the fact that the birds were not in their flight path. It was believed that the flock then split into two or three separate flocks after the other airplane took off, with one of the flocks turning east and directly into the path of the incident airplane.

Factual narrative

On October 19, 2002, about 0850 eastern daylight time, a Boeing 767-222, N607UA, operating as United Airlines flight 185, sustained minor damage when it struck birds on takeoff from General Edward Lawrence Logan International Airport (BOS), Boston, Massachusetts. The airplane sustained minor damage. The captain, first officer, 7 flight attendants, and 119 passengers were not injured. The flight was operating on an instrument flight rules flight plan to San Francisco International Airport (SFO), San Francisco, California. The scheduled passenger flight was conducted under 14 CFR Part 121.

The airplane departed runway 22R, and struck the birds during the initial climbout. 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. Even though the #2 engine was still producing power, the captain elected to shut it down as a precautionary measure. The airplane returned to Logan Airport and performed an overweight landing on runway 33L. The airplane was then towed to the gate, and the passengers deplaned normally.

Examination of the airplane revealed damage to the right inboard leading edge slat, landing light, and the #2 engine bypass stator vanes. Some of the vanes exited the forward section of the cowling at the 9 o'clock and 12 o'clock position.

The Massachusetts Port Authority (Massport), the public authority that managed Logan Airport, had a Wildlife Hazard Management Plan in place at the airport. The plan included regular, daily inspections of the runways and airport environment. On the morning of the incident, after examination of the airport perimeter, two Massport wildlife technicians reported "heavy bird activity" to the control tower, which was standard operating procedure. The Automated Terminal Information System (ATIS) was then updated to reflect this hazard, and was still active at the time of the incident.

Prior to flight 185's take-off, one of the wildlife plan supervisors reported a flock of birds to the control tower on 128.8, the tower frequency for runway 22. The supervisor reported the birds were flying about 200 feet over the approach end of runway 15, and were moving southbound. A tower controller responded that they had the birds in sight.

Shortly thereafter, a Delta Airlines Boeing 737 departed runway 22 without incident, followed by United Airlines flight 185.

A review of air traffic control communications revealed that no specific warning was given by the air traffic controllers to the Delta or United Airlines crews, due to the fact that the birds were not in their flight path. It was believed that the flock then split into two or three separate flocks after the Delta airplane took off, with one of the flocks turning east and directly into the path of the departing United airplane.

When asked if something could have been done to avoid this incident, a Massport wildlife representative answered "no." Moreover, no changes were made to the Massport Wildlife Hazard Management Plan.

Weather at the time included winds from 200 degrees at 9 knots, visibility 10 statute miles, broken clouds at 8,500 feet, overcast clouds 12,000 feet, temperature 50 degrees F, and dewpoint 41 degrees F.

Aircraft

Registration
N607UA
Reported as
Boeing 767-222
Category
Airplane
Serial number
21868
Engine
Pratt & Whitney JT9-74RD, turbo fan
Damage
Minor damage
Flight
Part 121
Registered owner
United Air Lines Inc
Airworthiness certificate
Standard, Transport
Departed
BOS · Boston, MA
Destination
SFR · San Fransisco, CA
Flight plan
IFR
Airport
BOS · Logan International Airport, runway 33L, 10,081 × 150 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Weather

Conditions
Visual (VMC) · Day
Wind
200° at 9 knots
Visibility
10 statute miles
Lowest ceiling
8,500 ft broken
Temperature
50 °F, dew point 41 °F
Altimeter
30.05 inHg
Observed at
BOS

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.