BFO91LA036 · Hughes 369HS
Omni Flight Helicopters Hughes 369HS · Accident: in flight collision with object during landing
From Martin State Airport (MTN) to Lynchburg Regional Airport - Preston Glenn Field (LYH)
Event
- NTSB case
- BFO91LA036
- 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
- 0
- 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
Hughes 369HS
- Aircraft type
- Hughes 369
- 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
- N5FC
- Operator
- Omni Flight Helicopters
- Onboard fatalities
- Unknown
- Route
- From Martin State Airport (MTN), Baltimore, MDTo Lynchburg Regional Airport - Preston Glenn Field (LYH), Lynchburg, VA
- 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
- Landing
- 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
- 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
- Pilot in command › Visual lookout, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED HE WAS LANDING THE AIRCRAFT IN A CLEARING ON TELEPHONE COMPANY RIGHT OF WAY PROPERTY IN ORDER TO COMMUNICATE WITH THE COMPANY'S GROUND PERSONNEL. AT AN ALTITUDE OF ABOUT 100 FEET, AFTER TURNING HIS CRAFT INTO THE WIND AND MANEUVERING TO AVOID SOME LOOSE GROUND WIRES, HE DESCENDED FOR A LANDING. AT ABOUT 10 FEET ABOVE THE GROUND, HE HEARD A LOUD BANG, THE AIRCRAFT SHUDDERED VIOLENTLY, BUT HE DID NOT LOSE PEDAL CONTROL. HE EXECUTED A HOVER AUTO ROTATION, LANDED THE AIRCRAFT AND SHUT DOWN THE ENGINE. AFTER EXITING THE AIRCRAFT, THE PILOT DISCOVERED THE TAIL ROTOR AND FINS HAD STRUCK A 2 INCH METAL FENCE POST THAT WAS 7 FEET TALL.
Probable cause
THE PILOT'S INADEQUATE VISUAL LOOKOUT, WHICH RESULTED IN HIS FAILURE TO SEE-AND-AVOID THE OBSTRUCTION (FENCE POST).
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO91LA036
- Event ID
- 20001212X16558
- Case number
- BFO91LA036
- 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: investigation status. 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: d27c39a6895ed0590a71affa110e2e72f922011261ebbca95614b77a0d4ead18; retrieved 2026-09-23T04:30:30.962Z.