Lit air carrier departure experienced a TCAS RA event immediately after take off with reported VFR t...

Narrative:

This report is submitted to highlight what I believe to be an ATC error. Lit tower cleared us for takeoff on 22R with an assigned heading. Immediately after take off; VFR; another carrier; traffic was called at our 1 o'clock. I responded that we were looking for traffic. Due to sun in our eyes; we could not visually acquire the traffic. ATC said the traffic had us in sight. Very shortly after the flaps were up; we got a TCAS RA to descend. We complied in accordance with fom guidance. The last readout I saw on the TCAS display was +300. Almost immediately after we began the descent to comply with the RA; we began to receive a GPWS 'don't sink'. We continued to comply with the RA while noting our AGL altitude of about 800 ft AGL. The captain and I agreed to continue to comply with the RA and that we would monitor our AGL altitude. Once clear of conflict; we continued to climb out. When told to contact departure; I told the tower that we had descended to comply with a RA for the VFR traffic. They responded; 'roger; contact departure'. We never should have been cleared for take off with VFR traffic in a position to give us a RA. A delay of a minute would have completely eliminated this unsafe condition.

Original NASA ASRS Text

Title: LIT Air Carrier departure experienced a TCAS RA event immediately after take off with reported VFR traffic that was maintaining visual separation; the reporter noting ATC should have delayed their take off clearance.

Narrative: This report is submitted to highlight what I believe to be an ATC error. LIT Tower cleared us for takeoff on 22R with an assigned heading. Immediately after take off; VFR; another carrier; traffic was called at our 1 o'clock. I responded that we were looking for traffic. Due to sun in our eyes; we could not visually acquire the traffic. ATC said the traffic had us in sight. Very shortly after the flaps were up; we got a TCAS RA to descend. We complied in accordance with FOM guidance. The last readout I saw on the TCAS display was +300. Almost immediately after we began the descent to comply with the RA; we began to receive a GPWS 'don't sink'. We continued to comply with the RA while noting our AGL altitude of about 800 FT AGL. The Captain and I agreed to continue to comply with the RA and that we would monitor our AGL altitude. Once clear of conflict; we continued to climb out. When told to contact Departure; I told the Tower that we had descended to comply with a RA for the VFR traffic. They responded; 'Roger; contact Departure'. We never should have been cleared for take off with VFR traffic in a position to give us a RA. A delay of a minute would have completely eliminated this unsafe condition.

Data retrieved from NASA's ASRS site as of April 2012 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	968325
Time
Date	201109
Local Time Of Day	1201-1800
Place
Locale Reference	LIT.Tower
State Reference	AR
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	Takeoff
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Plan	VFR
Person 1
Function	First Officer
Experience	Flight Crew Last 90 Days 240 Flight Crew Type 5350
Events
Anomaly	ATC Issue All Types Conflict NMAC Conflict Airborne Conflict

Lit air carrier departure experienced a TCAS RA event immediately after take off with reported VFR traffic that was maintaining visual separation; the reporter noting ATC should have delayed their take off clearance.