Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

October 19, 2002 · Boeing 767-222 · N607UA

Boston, MA

Overview

Report Status
Final with probable cause
Event Type
Incident
Date
October 19, 2002
Injury Outcomes
No injuries (128 uninjured)
Location
Boston, MA
Aircraft
Boeing 767-222
Tail Number
N607UA
Injuries
None
Aircraft Damage
Minor
NTSB Number
IAD03IA007

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.

NTSB Probable Cause

An inadvertant collision with birds during the initial climb out.

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

Flight

Event TypeIncident
Event Time08:50 EDT
Nearest AirportLogan International Airport (0nm)
Runway33L
Runway Length10081 ft
Runway Width150 ft
Flight Plan FiledIFR
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftBoeing 767-222
Tail NumberN607UA
Aircraft CategoryAir
DamageMinor
Operating RulePart 121
Engines2
Engine TypeTurbofan
Engine DetailsPratt & Whitney · JT9-74RD · Turbofan

People & Injuries

Injury SummaryNo injuries (128 uninjured)
Fatal0
Serious0
Minor0
Uninjured128
Total128

Conditions

ConditionsVMC
LightDaylight
Wind200° @ 9 kt
Visibility10 sm
CeilingBroken clouds 8500 ft
Temperature / Dew Point50 / 41 C
Altimeter30.05 inHg
Observation Time12:54
Weather SourceWFAC

Appendix: Source Data