FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Omni Flight Airways [ems] MBB BO-105 incident

22 Oct 1984 · Orlando, FL, United States

MBB BO-105 · Incident: loss of control in flight on approach

From Leesburg, FL to Orlando, FL

Report a problem

Event

NTSB case
MIA85IA015
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
Incident
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
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

MBB BO-105

Aircraft type
MBB BO-105
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
N29144
Onboard fatalities
Unknown
Route
From Leesburg, FLTo Orlando, FL
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 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 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 control in flight
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

  • Control interference
  • Pilot in command › Planning/decision, improper
  • Rotorcraft flight control, collective control › Foreign object

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

NTSB narrative

THE PURPOSE OF THE FLT WAS TO TRANSPORT A 76 YR OLD PATIENT, WHO WAS IN CRITICAL CONDITION. THE FLT WAS NORMAL UNTIL IT WAS ON FINAL APCH TO A 7TH FLOOR, ROOFTOP, HOSPITAL HELIPORT. DURING THE APCH, THE PLT ATTEMPTED TO INCREASE THE COLLECTIVE TO SLOW THE RATE OF DESCENT. HOWEVER, THE COLLECTIVE CONTROL WOULD NOT RAISE. THE PLT WAS ABLE TO KEEP THE HELICOPTER FROM HITTING THE SIDE OF THE BUILDING, BUT SUBSEQUENTLY LANDED HARD ON A LOWER ROOFTOP AT THE 2ND FLOOR LEVEL. THERE WAS MINOR DAMAGE TO THE SKID CROSSTUBES, TAIL ROTOR, TAIL BOOM, LEFT HORIZONTAL STABILIZER FIN & AN ANTENNA. AFTER THE INCIDENT, THE PLT NOTED THAT A HAND HELD TYPE RADIO HAD LODGED BEHIND THE COLLECTIVE PITCH CONTROL.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MIA85IA015
Event ID
20001214X41429
Case number
MIA85IA015
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: d7342bbad8d0d7b5d5ae1bc374f9acdbbb50079b43018e76deb6f27dbc45d6a9; retrieved 2026-09-18T20:35:39.830Z.
  • The NTSB's operator name is blank for N29144; the operator shown is the name the NTSB records it doing business as.