Narrative:

Departing out of richmond on the LUCYL4 departure; off runway 2; we were giving the clearance of climb via the SID. This calls for runway heading until 687 feet then right turn direct sjayy to cross at or above 5;000. After liftoff tower called traffic northeast of the field at 2;700. We did not have that traffic in sight; so tower asked the skyhawk traffic if they had us in sight. They replied that they did and tower asked them to maintain visual separation from that traffic. We still did not have the traffic in sight when tower handed us over to departure but he did mention the skyhawk has us in sight and would maintain visual. We could see them on TCAS. As we climbed via the SID; it called for a turn directly towards the aircraft. Climbing through about 2;200 feet it became clear that we were going to be very close. We got a traffic alert but no RA.around this time; we both saw the traffic; it was flying directly at us and then began a left turn to fly behind us. When we saw the plane flying at us; it was decided we needed to take corrective action without the RA resolution. We made a descending left turn away from traffic; back down to around 2;000 feet. When we checked in with departure; he asked if we had the traffic; and we informed him we were descending.once the traffic had passed; we commenced our climb and the flight continued without any further incident. Suggestions: in this case; the controller believed that the skyhawk would maintain visual separation [but] they continued along their conflicted track longer than necessary. I believe there should have been a heading or a lower altitude assigned to keep us at a safer separation criterion.

Related reports:

Google
 

Original NASA ASRS Text

Title: Embraer jet First Officer reported executing precautionary evasive maneuver from an airborne conflict.

Narrative: Departing out of Richmond on the LUCYL4 departure; off runway 2; we were giving the clearance of climb via the SID. This calls for runway heading until 687 feet then right turn direct SJAYY to cross at or above 5;000. After liftoff tower called traffic northeast of the field at 2;700. We did not have that traffic in sight; so tower asked the Skyhawk traffic if they had us in sight. They replied that they did and tower asked them to maintain visual separation from that traffic. We still did not have the traffic in sight when tower handed us over to departure but he did mention the Skyhawk has us in sight and would maintain visual. We could see them on TCAS. As we climbed via the SID; it called for a turn directly towards the aircraft. Climbing through about 2;200 feet it became clear that we were going to be very close. We got a traffic alert but no RA.Around this time; we both saw the traffic; it was flying directly at us and then began a left turn to fly behind us. When we saw the plane flying at us; it was decided we needed to take corrective action without the RA resolution. We made a descending left turn away from traffic; back down to around 2;000 feet. When we checked in with Departure; he asked if we had the traffic; and we informed him we were descending.Once the traffic had passed; we commenced our climb and the flight continued without any further incident. Suggestions: In this case; the Controller believed that the Skyhawk would maintain visual separation [but] they continued along their conflicted track longer than necessary. I believe there should have been a heading or a lower altitude assigned to keep us at a safer separation criterion.

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.