# Incident 20000611034639I: Bolkms BK117B1, Ashboro, NC, June 11, 2000

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 11, 2000, 01:15 local time
- Place: Ashboro, NC
- Damage: Minor damage
- Phase of flight: Idling Engines
- Operating rules: Air taxi and commuter (Part 135)
- Operator: BAOA
- 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
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000611034639I

## Narrative

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

(-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 ENGINES AT IDLE, GOING THROUGH ENGINE COOL-DOWN.  THE CAR CAME DOWN AN EXIT RAMP IN THE WRONG DIRECTION AND CAME NORTH ON THE SOUTHBOUND LANE OF HWY 220.  THE CAR STRUCK THE BOTTOM TIP CAP OF THE RIGHT HORIZONTAL STABILIZER.  ONLY MINOR DAMAGE WAS SUSTAINED.  THE INCIDENT WAS A HIT AND RUN, THEY NEVER CAUGHT THE DRIVER OF THE CAR.  THE POLICE DID HAVE BARRICAIDS SET UP TO STOP TRAFFIC.  THE AIRCRAFT WAS INSPECTED THEN FERRIED BACK TO RDU FOR REPAIRS.  THIS WAS ACCOMPLISHED PER A FAA ISSUED "SPECIAL FLIGHT AUTHORIZATION".

## Other reports on N601EH (1)

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

- [Incident 20081223856939I](https://openairdocs.org/incident/20081223856939I), Dec 23, 2008: Bolkms BK117B1 (N601EH), Orlando, FL, Minor damage. #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…

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.