Commercial Fixed Wing
Communication Breakdown; Confusion; Situational Awareness
ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Flight Crew Took Evasive Action
Human Factors; Procedure
While taking off of Runway 19 from FLO we spotted traffic; a light helicopter; and were advised of the traffic.  The FLO Tower also notified the helicopter that it had traffic (us) passing on its left. The helicopter responded to the effect; 'Okay turning left.'  The helicopter then made a left hand turn into our flight path requiring me to take control of the aircraft (the First Officer didn't have visual on the helicopter) to maneuver it out of the flight path of the helicopter. I estimate that the helicopter was with in a few hundred feet horizontally of my aircraft at the same altitude. We saw the helicopter in close proximity.  This event occurred because we were given a takeoff clearance with traffic in the departure corridor of our runway. It also occurred because the helicopter misunderstood communication from the Tower that wasn't corrected by the Tower upon the helicopter's erroneous read back. I took control of the aircraft made a turn to avoid striking the helicopter; then notified ATC of our deviation from assigned heading. Returned aircraft back to the First Officer after clearing the conflict and then obtained a new clearance. This event could have been avoided if the Tower Controller would have instructed the helicopter clear of the departure end of the runway prior to launching us. It could have also been avoided if the Tower Controller would have corrected the erroneous read back of the traffic call from the helicopter.
Air Carrier departure from FLO experienced a conflict with a helicopter; both aircraft were advised of one another but ATC failed to hear an incorrect read back by the helicopter resulting in the conflict.