FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Hyannis Air Service Cessna 402 C accident

4 Jun 2023 · Charlotte Amalie, CB, United States Possible conflict

Cessna 402 C · Accident: birdstrike on approach

From Terrance B. Lettsome International Airport (TUPJ) to an unrecorded destination

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ERA23LA257
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
Completed
Event fatalities
Unknown
Ground fatalities
Unknown
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
Charter & commuter
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

Cessna 402 C

Aircraft type
Cessna 402
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
N7037E
Onboard fatalities
Unknown
Route
From Terrance B. Lettsome International Airport (TUPJ), RoadtownTo not recorded
Aircraft age
About 42 years (built 1981)
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 135: Air Taxi & Commuter
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
Approach · VFR pattern downwind
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
Birdstrike
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Environmental issues › Physical environment

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The operator reported that while entering the traffic pattern for landing, the pilot saw a large bird and attempted to take evasive action, but the airplane and the bird collided. The bird entered the cabin through the right windscreen and struck two passengers. One passenger sustained serious injuries while the other passenger incurred minor injuries. The pilot declared an emergency and subsequently landed the airplane uneventfully. The operator reported that there were no preaccident mechanical malfunctions or failures of the airplane that would have precluded normal operation.

Probable cause

An in-flight collision with a bird while entering the traffic pattern.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23LA257
Event ID
20230606192322
Case number
ERA23LA257
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 5401aff1da15acd98df12d10cd4b9ec6954af62022d2898c79b89ae3d27dc1ce; retrieved 2026-09-16T17:42:00.835Z.