FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA01FA085 · MBB BO-105C

5 May 2001 · Medford, OR, United States

MBB BO-105C · Accident: fire

From Rogue Valley International-Medford Airport (MFR) to Rogue Valley International-Medford Airport (MFR)

Report a problem

Event

NTSB case
SEA01FA085
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
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-105C

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
N105RH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Rogue Valley International-Medford Airport (MFR), Medford, ORTo Rogue Valley International-Medford Airport (MFR), Medford, OR
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
Unknown
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
Fire
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

  • Miscellaneous, bolt/nut/fastener/clamp/spring › Leak

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

NTSB narrative

As the helicopter cleared trees after patient pickup, a series of "pops" was heard and the #1 engine lost power. The pilot initially decided to make an emergency landing in a field, but no suitable landing areas were found, and the helicopter's #2 engine was determined to be producing sufficient power to sustain flight. The pilot therefore elected to continue the flight to the airport, and called the Medford tower and requested an emergency landing with fire crews standing by. The medical crew on board the helicopter subsequently reported that they smelled "something burning." Approaching the airport, the Medford tower controller advised the pilot that the aircraft was trailing smoke, and subsequently advised the pilot that the helicopter was on fire. The pilot elected to make a fast run-on landing, and subsequently landed on taxiway A at the airport. The aircraft occupants evacuated the helicopter without injury, and ARFF successfully extinguished the fire. The fire extensively damaged the helicopter's #1 engine compartment, engine cowling, outer surfaces of the #1 engine, and transmission compartment. The fire also partially burned/melted through the main rotor flight control tubes, and molten metal and debris were ingested into the #1 engine compressor. Post-accident examinations disclosed that the fire occurred in the #1 engine compartment, external to the #1 engine. The #1 engine compartment contained puddles of oil on the pan below the engine, and the #1 engine oil tank was found to be empty. The #1 engine oil out line (a line carrying oil from the engine accessory gearbox to the oil tank) was found to be leaking at a B-nut fitting at one end of the line. Additionally, the engine's right exhaust stack and right exhaust extension were found to be cracked around portions of their circumference under a V-clamp. Disassembly examination of the #1 engine N1 gas producer turbine assembly at the engine manufacturer's facilities disclosed that the first-stage nozzle and turbine wheel were burned consistent with exposure to excessive TOT, and that the second-stage nozzle and turbine wheel were generally intact. Examination of the three main bearings located in the turbine assembly (Nos. 6, 7, and 8) disclosed that the number 8 bearing was oiled and rotated freely, the number 6 bearing was dry but intact and rotated freely, and that the number 7 bearing was dry and slightly notchy but was able to be rotated. The Rolls-Royce accident investigation report concluded that "There were no hardware failures on any part of the engine", that "The damages to the 1st stage nozzle and 1st stage turbine wheel were the result of operation at an excessive TOT", and that "The engine was operating with the external fire well advanced as evidenced by the ingestion of fire debris and molten metal into the compressor."

Probable cause

A leaking engine oil outlet line fitting in the #1 engine compartment, resulting in an oil fire in the engine compartment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA01FA085
Event ID
20010522X00990
Case number
SEA01FA085
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, coordinates. 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: 873d5053c5fbcfde1044226a2f3229d251912c574f7b71472834bba8b5521202; retrieved 2026-09-18T16:13:52.054Z.