Narrative:

When cleared for takeoff runway 20R at sna; tower mentioned that there was traffic on 3 mile final and that a helicopter was approaching from the southeast. Tower stated that the helicopter 'will remain east of your departure path'. I checked the final traffic and initiated takeoff roll. At around the '80 knots' call I noticed a helicopter approaching perpendicular to our runway at a high rate of closure. The helicopter was descending and closing on our departure path as we were accelerating with 26K max thrust. Very uncomfortable. At V1 -15 knots; he began a steep banked turn to parallel our runway and arrested his closure at about 100 ft left and 200 ft above our runway. He then continued his descent next to our runway. Approaching V1 I lost sight of him in the ground clutter and my first officer yelled that he was clear of the runway. I have never seen anything quite like this situation. We were unable to do anything except reject our near balanced field takeoff; which would not have saved us from a collision if the helicopter had not turned at the last possible moment. Tower said nothing. I am used to VFR traffic and parallel runway ops at sna but this was a far greater threat than I have ever seen there. I have been flying out of sna for the last 25 years. ATC needs to provide more information or make sure we have a visual on traffic which affects our departure. I assumed the helicopter was a law enforcement helo working low and left of our departure path. Somehow I missed that he was landing at sna. If I had known what was going to transpire I would not have accepted a takeoff clearance. When ATC says an aircraft 'will do something'; who has responsibility if he doesn't? We were also part of a squeeze play in front of the traffic on 3 mile final-which rushed the whole situation. In hindsight; I could have refused the takeoff clearance just based on the final approach traffic.

Related reports:

Google
 

Original NASA ASRS Text

Title: Pilot reports of being advised of helicopter traffic while departing. Pilot sees traffic then rejects takeoff due to close proximity of traffic.

Narrative: When cleared for takeoff RWY 20R at SNA; tower mentioned that there was traffic on 3 mile final and that a helicopter was approaching from the southeast. Tower stated that the helicopter 'Will remain east of your departure path'. I checked the final traffic and initiated takeoff roll. At around the '80 Knots' call I noticed a helicopter approaching perpendicular to our runway at a high rate of closure. The helicopter was descending and closing on our departure path as we were accelerating with 26K max thrust. Very uncomfortable. At V1 -15 knots; he began a steep banked turn to parallel our runway and arrested his closure at about 100 ft left and 200 ft above our runway. He then continued his descent next to our runway. Approaching V1 I lost sight of him in the ground clutter and my FO yelled that he was clear of the runway. I have never seen anything quite like this situation. We were unable to do anything except reject our near balanced field takeoff; which would not have saved us from a collision if the helicopter had not turned at the last possible moment. Tower said nothing. I am used to VFR traffic and parallel runway ops at SNA but this was a far greater threat than I have ever seen there. I have been flying out of SNA for the last 25 years. ATC needs to provide more information or make sure we have a visual on traffic which affects our departure. I assumed the helicopter was a law enforcement helo working low and left of our departure path. Somehow I missed that he was landing at SNA. If I had known what was going to transpire I would not have accepted a takeoff clearance. When ATC says an aircraft 'Will do something'; who has responsibility if he doesn't? We were also part of a squeeze play in front of the traffic on 3 mile final-which rushed the whole situation. In hindsight; I could have refused the takeoff clearance just based on the final approach traffic.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.