NYC92FA118 · Beech BE-200
Omega Air Beech BE-200 · Accident: loss of engine power on approach
From Martin State Airport (MTN) to Wilmington Airport (ILG)
Event
- NTSB case
- NYC92FA118
- 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
- 4 · 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
Beech BE-200
- Aircraft type
- Beechcraft BE-200
- 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
- N32HG
- Operator
- Omega Air
- Onboard fatalities
- Unknown
- Route
- From Martin State Airport (MTN), Baltimore, MDTo Wilmington Airport (ILG), New Castle, DE
- 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
- Loss of engine power
- 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
- Stall; Tree(s)
- 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
- Pilot in command › Airspeed(vmc), not maintained
- Pilot in command › Emergency procedure, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WITNESSES OBSERVED THE AIRPLANE ON A 'NORMAL' FINAL APPROACH, THEN SAW IT DROP 'LOW AND SLOW, RETRACT THE GEAR AND ROLL TO THE LEFT INTO THE TREES.' EXAMINATION OF THE ENGINES REVEALED THAT THE LEFT ENGINE FAILED BECAUSE OF A FATIGUE FAILURE OF A COMPRESSOR TURBINE BLADE. EXAMINATION OF THE RIGHT ENGINE REVEALED NO EVIDENCE OF MALFUNCTION THAT WOULD HAVE PREVENTED THE USE OF FULL POWER. THE AIRCREW WAS EXPERIENCED AND WELL TRAINED. THE RADAR DATA CONFIRMED A DROP IN AIRSPEED JUST BEFORE THE AIRPLANE CONTACTED THE TREES.
Probable cause
THE PILOT'S IMPROPER EXECUTION OF AN EMERGENCY PROCEDURE, AFTER AN ENGINE FAILURE, WHICH RESULTED IN A LOSS OF AIRSPEED AND SUBSEQUENT STALL AT AN ALTITUDE TOO LOW FOR RECOVERY. A FACTOR RELATED TO THE ACCIDENT WAS THE FATIGUE FAILURE OF A COMPRESSOR TURBINE BLADE AND THE SUBSEQUENT ENGINE FAILURE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC92FA118
- Event ID
- 20001211X14949
- Case number
- NYC92FA118
- 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: e362d87953ea3754ea3ed2b27f627ba4fe3823dd25577aeff136b14f95d2f27e; retrieved 2026-09-21T01:07:06.778Z.