An LJ31A pilot on takeoff roll at tix observed an H269 helicopter overfly his runway at approximatel...

Narrative:

Shortly after tower closed; we taxied out to runway 18 monitoring CTAF 118.9; and broadcasting our position and intentions on same. There was a training helicopter -- we believe that is one of many based at tix; practicing touch-and-goes on the 5000 ft runway 9. Due to our weight and the ambient temperature; we elected to use runway 18 (7319 ft); winds were variable and light from the ese. We announced taxiing out to runway 18; crossing runway 9; back-taxiing on runway 18 for departure; and departing runway 18. (As we crossed the departure end of runway 9 we observed the helicopter hovering on the approach end of runway 9. This was during our taxi out to runway 18.) he had announced he was hovering in position. The taxiway layout to runway 18 requires a back-taxi on runway 18 for full length. Consequently; we held short of runway 18 while we completed the 'before takeoff' checklist. Then we announced on CTAF we were back-taxiing on runway 18 for departure. Upon reaching the approach end of runway 18; we turned to depart runway 18 and announced same on CTAF. As we commenced our takeoff roll; the helicopter announced departing runway 9. He stayed below tree line (along north side of runway 9) and appeared from behind trees shortly before he crossed our departure runway at approximately 50 ft AGL. At this point we were at V1 and I knew we would not reach vr till past the runway intersection. Rather than risk a high speed abort; I advised the copilot to continue (he was PF; as it was his check ride). The helicopter crossed the runway intersection at an estimated 50 ft AGL and approximately 100-200 ft in front of us. We reached vr just past the runway intersection. I am also commercial rotorcraft rated; and while we 'may' have been able to safely abort; I fail to see why the helicopter pilot hovered at the approach end of runway 9 in a blind spot and elected to execute a low level; high speed departure; using the full length of runway 8; after he hovered for the entire time of our taxi to the runway (approximately 6-8 mins); he knew we were departing the intersecting runway; unless he wasn't listening; and could have turned south to 'avoid the flow of fixed wing traffic' or climbed out at a speed and rate of climb so as to not stay below tree line to the extent he did. Just my observation/opinion.

Original NASA ASRS Text

Title: AN LJ31A PILOT ON TAKEOFF ROLL AT TIX OBSERVED AN H269 HELICOPTER OVERFLY HIS RUNWAY AT APPROX 50 FT AGL AND APPROX 100 FT IN FRONT OF HIM.

Narrative: SHORTLY AFTER TWR CLOSED; WE TAXIED OUT TO RWY 18 MONITORING CTAF 118.9; AND BROADCASTING OUR POS AND INTENTIONS ON SAME. THERE WAS A TRAINING HELI -- WE BELIEVE THAT IS ONE OF MANY BASED AT TIX; PRACTICING TOUCH-AND-GOES ON THE 5000 FT RWY 9. DUE TO OUR WT AND THE AMBIENT TEMP; WE ELECTED TO USE RWY 18 (7319 FT); WINDS WERE VARIABLE AND LIGHT FROM THE ESE. WE ANNOUNCED TAXIING OUT TO RWY 18; XING RWY 9; BACK-TAXIING ON RWY 18 FOR DEP; AND DEPARTING RWY 18. (AS WE CROSSED THE DEP END OF RWY 9 WE OBSERVED THE HELI HOVERING ON THE APCH END OF RWY 9. THIS WAS DURING OUR TAXI OUT TO RWY 18.) HE HAD ANNOUNCED HE WAS HOVERING IN POS. THE TXWY LAYOUT TO RWY 18 REQUIRES A BACK-TAXI ON RWY 18 FOR FULL LENGTH. CONSEQUENTLY; WE HELD SHORT OF RWY 18 WHILE WE COMPLETED THE 'BEFORE TKOF' CHKLIST. THEN WE ANNOUNCED ON CTAF WE WERE BACK-TAXIING ON RWY 18 FOR DEP. UPON REACHING THE APCH END OF RWY 18; WE TURNED TO DEPART RWY 18 AND ANNOUNCED SAME ON CTAF. AS WE COMMENCED OUR TKOF ROLL; THE HELI ANNOUNCED DEPARTING RWY 9. HE STAYED BELOW TREE LINE (ALONG N SIDE OF RWY 9) AND APPEARED FROM BEHIND TREES SHORTLY BEFORE HE CROSSED OUR DEP RWY AT APPROX 50 FT AGL. AT THIS POINT WE WERE AT V1 AND I KNEW WE WOULD NOT REACH VR TILL PAST THE RWY INTXN. RATHER THAN RISK A HIGH SPD ABORT; I ADVISED THE COPLT TO CONTINUE (HE WAS PF; AS IT WAS HIS CHK RIDE). THE HELI CROSSED THE RWY INTXN AT AN ESTIMATED 50 FT AGL AND APPROX 100-200 FT IN FRONT OF US. WE REACHED VR JUST PAST THE RWY INTXN. I AM ALSO COMMERCIAL ROTORCRAFT RATED; AND WHILE WE 'MAY' HAVE BEEN ABLE TO SAFELY ABORT; I FAIL TO SEE WHY THE HELI PLT HOVERED AT THE APCH END OF RWY 9 IN A BLIND SPOT AND ELECTED TO EXECUTE A LOW LEVEL; HIGH SPD DEP; USING THE FULL LENGTH OF RWY 8; AFTER HE HOVERED FOR THE ENTIRE TIME OF OUR TAXI TO THE RWY (APPROX 6-8 MINS); HE KNEW WE WERE DEPARTING THE INTERSECTING RWY; UNLESS HE WASN'T LISTENING; AND COULD HAVE TURNED S TO 'AVOID THE FLOW OF FIXED WING TFC' OR CLBED OUT AT A SPD AND RATE OF CLB SO AS TO NOT STAY BELOW TREE LINE TO THE EXTENT HE DID. JUST MY OBSERVATION/OPINION.

Data retrieved from NASA's ASRS site as of January 2009 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.

Attributes
ACN	749926
Time
Date	200708
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : tix.airport
State Reference	FL
Altitude	agl single value : 0
Aircraft 1
Operator	common carrier : charter
Make Model Name	Learjet 31
Operating Under FAR Part	Part 135
Flight Phase	ground : takeoff roll
Flight Plan	IFR
Aircraft 2
Make Model Name	Helicopter
Flight Phase	climbout : takeoff
Person 1
Affiliation	company : corporate
Function	flight crew : captain observation : company check pilot oversight : pic
Qualification	other other : rotorcraft pilot : commercial pilot : multi engine pilot : atp
Experience	flight time last 90 days : 100 flight time total : 14000 flight time type : 8000
ASRS Report	749926
Events
Anomaly	conflict : ground critical
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Miss Distance	horizontal : 100 vertical : 50
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

An LJ31A pilot on takeoff roll at tix observed an H269 helicopter overfly his runway at approximately 50 ft AGL and approximately 100 ft in front of him.