# Incident 20081223856939I: Bolkms BK117B1, Orlando, FL, December 23, 2008

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: December 23, 2008, 21:45 local time
- Place: Orlando, FL
- Airport: Executive
- Damage: Minor damage
- Phase of flight: Maneuver
- Operating rules: Air taxi and commuter (Part 135)
- Operator: QMLA
- Location: 28.5383° N, 81.3792° W: Placed by OpenAirDocs: center of Orlando, FL, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=28.5383&lon=-81.3792&mi=10
- Aircraft: N601EH, a cancelled registration (https://openairdocs.org/deregistered/N601EH-2013-06-05) (OpenAirDocs)
- Registry model: Messerschmitt BK 117 B-1 (registry code 5626012, https://openairdocs.org/model/messerschmitt-bk-117-b-1) (OpenAirDocs)
- Registry engine: Lycoming LTS-101 series (registry code 41560, https://openairdocs.org/engine/lycoming-lts-101-series) (OpenAirDocs)
- Reported make and model: BOLKMS BK117B1
- Reported engine: LYC LTS101*
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 2,500 total, 100 in this make and model, 6 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20081223856939I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

#2 ENGINE WAS NOT OPERATING PROPERLY AND WAS NOT ABLE TO MATCH THE TORQUE WITH #1 ENGINE, HELICOPTER LANDED AND SMOKE CAME FROM #2 RIGHT ENGINE WITH FLAMES OUT EXHAUST.  #2 ENGINE FIRE EXTINGUISHER ACTIVATED, EVERYONE EXITED AIRCRAFT WITHOUT INJURY.

## Other reports on N601EH (1)

Matched to the same aircraft by N-number and date.

- [Incident 20000611034639I](https://openairdocs.org/incident/20000611034639I), Jun 11, 2000: Bolkms BK117B1 (N601EH), Ashboro, NC, Minor damage. (-23)After landing on hwy 220 near Ashboro, NC, at an automoblie accident site, the helicopter was struck by an automobile. The aircraft was still running with…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.