FA20 departure on runway 18R at tul experienced a jetblast from B737 departure on runway 8.

Attributes
ACN	655886
Time
Date	200504
Place
Locale Reference	airport : tul.airport
State Reference	OK
Altitude	agl bound lower : 10 agl bound upper : 20
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : tul.tower
Operator	general aviation : corporate
Make Model Name	Falcon 20FJF/20C/20D/20E/20F
Operating Under FAR Part	Part 91
Flight Phase	climbout : initial
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : tul.tower
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	climbout : initial
Person 1
Affiliation	company : corporate
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 45 flight time total : 5500 flight time type : 310
ASRS Report	655886
Person 2
Affiliation	company : corporate
Function	flight crew : first officer
Events
Anomaly	inflight encounter other
Independent Detector	other flight crewa
Resolutory Action	none taken : insufficient time
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

The aircraft I was flying was taking off from runway 18R at tul. A B737 was taking off from runway 8 at the same airport. We rotated and were between 0-25 ft with the landing gear still extended when we flew through the jetblast from the departing B737. We experienced an approximately 1-G side load and 25-30 degrees of roll that required control input to correct. During a later phase of flight; I contacted tul tower via VHF communication and informed them we experienced the jetblast and would have preferred our takeoff clearance to not have placed us in that situation. Tower acknowledged the transmission. My experience with this runway confign at tulsa suggests that a protocol already exists or should exist that would preclude takeoff clrncs that would create this conflict. In the future; I would not accept a clearance to take off of runway 18R if I had any knowledge simultaneous departing jet traffic on runway 8. The threshold of runway 18R does not have a clear view of runway 8 due to the runway slope of runway 18R.

Original NASA ASRS Text

Title: FA20 DEP ON RWY 18R AT TUL EXPERIENCED A JETBLAST FROM B737 DEP ON RWY 8.

Narrative: THE ACFT I WAS FLYING WAS TAKING OFF FROM RWY 18R AT TUL. A B737 WAS TAKING OFF FROM RWY 8 AT THE SAME ARPT. WE ROTATED AND WERE BTWN 0-25 FT WITH THE LNDG GEAR STILL EXTENDED WHEN WE FLEW THROUGH THE JETBLAST FROM THE DEPARTING B737. WE EXPERIENCED AN APPROX 1-G SIDE LOAD AND 25-30 DEGS OF ROLL THAT REQUIRED CTL INPUT TO CORRECT. DURING A LATER PHASE OF FLT; I CONTACTED TUL TWR VIA VHF COM AND INFORMED THEM WE EXPERIENCED THE JETBLAST AND WOULD HAVE PREFERRED OUR TKOF CLRNC TO NOT HAVE PLACED US IN THAT SIT. TWR ACKNOWLEDGED THE XMISSION. MY EXPERIENCE WITH THIS RWY CONFIGN AT TULSA SUGGESTS THAT A PROTOCOL ALREADY EXISTS OR SHOULD EXIST THAT WOULD PRECLUDE TKOF CLRNCS THAT WOULD CREATE THIS CONFLICT. IN THE FUTURE; I WOULD NOT ACCEPT A CLRNC TO TAKE OFF OF RWY 18R IF I HAD ANY KNOWLEDGE SIMULTANEOUS DEPARTING JET TFC ON RWY 8. THE THRESHOLD OF RWY 18R DOES NOT HAVE A CLR VIEW OF RWY 8 DUE TO THE RWY SLOPE OF RWY 18R.

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.