FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC04CA049 · Bell B407

20 Dec 2003 · Morehead, KY, United States

Bell B407 · Accident: in flight collision with object on approach

From Morehead, KY (no airport) to Morehead, KY (no airport)

Report a problem

Event

NTSB case
NYC04CA049
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
General aviation
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

Bell B407

Aircraft type
Bell B407
Category
Helicopter
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
N508MT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Morehead, KY (no airport)To Morehead, KY (no airport)
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 91: General Aviation
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 final
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
In flight collision with object
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Pole
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

  • Ground personnel › Unsafe/hazardous condition, not identified

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

After two reconnaissance flights over the landing zone, the pilot initiated an approach. The pilot then performed a go-around due to blowing snow, and completed a third reconnaissance flight over the landing zone. During the second approach, the tail rotor struck a standing frost free hydrant. The hydrant was approximately 1 inch in diameter and 3 feet high. The helicopter subsequently spun right and the pilot performed a hovering autorotation to the ground. Ground personnel had marked the perimeter of the landing zone with lights. However, the ground personnel later stated that they had not walked the interior of the landing zone and were unaware of the obstacle.

Probable cause

The ground personnel's failure to identify the hazardous condition. Factors were blowing snow and night conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC04CA049
Event ID
20040122X00085
Case number
NYC04CA049
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2003-12-21.
  • API snapshot SHA-256: ec3b91f7e7c6df9598734eb18bedb370ae67a900aa747d6de073cf6c7d40435c; retrieved 2026-09-22T08:03:48.164Z.