FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Colgan Air Beech 1900C accident

1 Nov 2001 · Bar Harbor, ME, United States

Beech 1900C · Accident: on ground/water collision with object during landing

From Boston Logan International Airport (BOS) to Hancock County-Bar Harbor Airport (BHB)

Report a problem

Event

NTSB case
NYC02LA023
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
API-reported fatalities
0 · all aircraft and ground
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
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Beech 1900C

Aircraft type
Beechcraft 1900
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
N210CJ
Operator
Colgan Air
Onboard fatalities
Unknown
Route
From Boston Logan International Airport (BOS), Boston, MATo Hancock County-Bar Harbor Airport (BHB), Bar Harbor, ME
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
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
Landing · landing roll
First occurrenceThe 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
On ground/water collision with object
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Object › Animal(s)

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

NTSB narrative

The first officer landed the airplane upon completion of a night ILS approach. Just after touchdown, the airplane struck a deer in the vicinity of the left engine. The deer had been crossing the runway from left to right. The captain shut down the engine and taxied to the gate. Post-accident examination of the airplane revealed that the engine firewall was cracked, one propeller blade was bent, and another blade had separated near the hub. The separated portion of the blade was found about 300 feet from where the collision occurred. Weather at the time included a 600-foot overcast layer.

Probable cause

A deer, which had been crossing the runway as the airplane touched down. A factor was the dark night conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC02LA023
Event ID
20011106X02201
Case number
NYC02LA023
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2001-11-02.
  • API snapshot SHA-256: 7f35bb4bb3fa3702c559a3f7a8968205bbdc1d4bbeed960b28e6f7e18151dd4b; retrieved 2026-09-18T16:08:26.112Z.