FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

United Air Lines Flight 297

23 Nov 1962 · Howard County, near Ellicott City, Maryland, US

United Airlines Vickers 745D · Bird strike

From Newark Liberty International Airport (EWR) to Hartsfield Jackson Atlanta International Airport (ATL)

Report a problem

Event

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
Unknown
Event fatalities
17 · all aircraft and ground
Ground fatalities
0
Occupants
17
Survivors
0
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
0 serious · 0 minor (NTSB)
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

Vickers 745D

Aircraft type
Vickers 745
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
N7430
Onboard fatalities
Unknown
Route
From Newark Liberty International Airport (EWR)To Hartsfield Jackson Atlanta International Airport (ATL)
Aircraft age
Not recorded
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 (scheduled domestic passenger service)
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
En route · cruise
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
Bird strike
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Airframe › Horizontal stabilizer, attachments
  • Miscellaneous acts, conditions › Overload failure
  • Miscellaneous › Bird collision

Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.

From the Wikipedia article

United Air Lines Flight 297 was a scheduled American flight from Newark International Airport to Atlanta that crashed 10 mi southwest of Baltimore on November 23, 1962, killing all 17 people on board. An investigation concluded that the aircraft, a Vickers Viscount 745D turboprop airliner, had struck at least two whistling swans, which caused severe damage to the plane, resulting in a loss of control.

The accident resulted in a greater understanding of the amount of damage that can be caused by bird strikes during flight. As a result, the Federal Aviation Administration (FAA) issued new safety regulations that required newly certified aircraft to be able to better withstand in-flight impacts with birds without affecting the aircraft's ability to fly or land safely.

Accident

The flight, flying as United Air Lines Flight 297, was a scheduled passenger flight from Newark to Atlanta, with stops at Washington National Airport, Raleigh–Durham Airport, and Charlotte Municipal Airport. It had 13 passengers and 4 crew members on board. The first leg of the flight was scheduled to last one hour at a true airspeed of 260 knot.

The plane departed Newark at 11:39 a.m. local time and proceeded normally until 12:14 p.m., when it was cleared to descend from 10,000 to 6,000 feet. At 12:19 p.m., air traffic controllers advised the flight that they had received numerous reports of large numbers of ducks and geese in the area, and the pilots acknowledged the report. At 12:22 p.m., Washington Approach directed the flight to turn left to a heading of 200 degrees, which was also confirmed by the pilots. An additional course change was transmitted at 12:23 p.m., but was not acknowledged. At 12:24 p.m., controllers lost radar contact with the plane.

The aircraft struck two whistling swans with its stabilizers at 6,000 feet. One of the birds caused only superficial damage to the right stabilizer, approximately one foot long and an eighth of an inch deep, while the other crashed completely through the left stabilizer and came out the other side. The impact caused the stabilizer to separate from the plane; it was found a quarter of a mile from the main wreckage. Investigators estimated that the crash might not have occurred if the two birds had hit the aircraft just a few inches higher or lower. The plane lost control, and in less than a minute, the aircraft's altitude dropped from approximately 6,000 feet to ground level, and its airspeed increased from 240 to 365 knot indicated airspeed. The plane crashed 10 mi southwest of Baltimore and exploded, killing all of the occupants.

Investigation and cause

Investigation

After the accident, a team of ten investigators from Washington arrived, headed by George A. Van Epps, the chief of safety investigation for the Civil Aeronautics Board. The wreckage from the plane was spread over an area of 100 to 150 yd in diameter, with the largest piece of debris only 15 feet long. A severe ground fire that broke out after the crash consumed most of the fuselage, right wing, and part of the left wing. The fire removed potential evidence of additional bird strikes that may have occurred on other parts of the aircraft, but the investigators were able to recover the flight recorder. Investigators reassembled critical parts of the aircraft at Washington National Airport, where they concluded that the aircraft had struck at least two birds.

A partial bird carcass as well as feathers, tissue, and blood was found 10 feet from the separated section of the left stabilizer and was identified by the Chief Medical Examiner for the State of Maryland to be of bird origin. Specimens of feathers and bones found at the site were taken to the United States Fish and Wildlife Service, who identified them as belonging to whistling swans, birds that can attain weights in excess of 18 lb. A pilot in the vicinity of the flight had reported seeing a flock of approximately fifty very large white birds flying in a trail at approximately 5,500 feet. Other pilots in the area also said that air traffic controllers at Washington Center had reported radar contacts near them that the pilots identified as large flocks of birds.

The Civil Aeronautics Board released a final report of their investigation on March 22, 1963. The investigators concluded that the probable cause of the accident was "a loss of control following separation of the left horizontal stabilizer which had been weakened by a collision with a whistling swan." The board recommended that additional research be undertaken to determine the risks to modern aircraft from bird strikes and to learn how to increase safety of aircraft in the event of bird strikes.

Text from the Wikipedia article “United Air Lines Flight 297” (revision 1373042821, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

NTSB remarks

LOSS OF CTL AFTER SEPARATION OF L HORIZ STAB DUECOLLISION WITH WHISTLING SWAN.

NTSB's remark from its 1962–1981 archive, as recorded (abbreviated, at most 98 characters): the archive has no narrative

Sources

Wikipedia article: United Air Lines Flight 297
Article
United Air Lines Flight 297
Revision
1373042821 · 2026-09-03 · retrieved 2026-09-18
Wikidata
Q7887347
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record
Event ID
19621123P000032
Case number
Unknown
Dataset
historical-pre1982
Source SHA-256
abe1a933b4b73583d61684309f7f0610c281e3c1de3537c6471bf2a98ba6481d
Where each value comes from
Record
Wikipedia article "United Air Lines Flight 297" (page 3771050, revision 1373042821); merged with NTSB case NTSB19621123P000032 (PRE1982 tblFirstHalf (one row per aircraft, grouped by date, place and time))
Date
NTSB record NTSB19621123P000032: PRE1982 DATE_OCCURRENCE
Place and country
Wikipedia infobox: site; country from NTSB record NTSB19621123P000032
Map position
Wikipedia: Wikipedia article coordinates
Aircraft, operator and route
NTSB record NTSB19621123P000032: PRE1982 REGIST_NO, ACFT_MAKE, ACFT_MODEL; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
Operation
NTSB record NTSB19621123P000032: operated under Part 121: Air carrier (scheduled domestic passg.svc)
Fatalities
NTSB record NTSB19621123P000032: PRE1982 TOTAL_ABRD_FATAL of each aircraft, plus people on the ground and others outside the aircraft
Ground fatalities
NTSB record NTSB19621123P000032: events.inj_f_grnd
Summary
Wikipedia infobox: summary
Source notes (4)
  • One occurrence in two sources, merged: the Wikipedia article "United Air Lines Flight 297" and NTSB case NTSB19621123P000032, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
  • From NTSB's 1962-1981 archive (PRE1982), which holds at most a short remark (98 characters, abbreviated) instead of a narrative; the accident type, phase of flight, causes and conditions are NTSB's codes, decoded as the archive defines them.
  • Reviewed means this record passed the site's consistency check, not that it was checked against a narrative or report - there is none to check against.
  • The operation category is mapped from the archive's operator and operation codes and has not been reviewed.