Narrative:

Flying vector 220 on the initial approach to pdk. My skywatch display showed a contact 300 ft low and climbing at 12 o'clock; inside 6 miles; but I didn't receive notification of this particular contact from TRACON (they had pointed out other traffic ahead; but I don't believe they mentioned this one). The contact seemed to level at my altitude and continued towards me; but I was unable to obtain a visual on it (atlanta in the background may have made that difficult). When I got the audible warning from skywatch about a potential collision I climbed about 200 ft and turned left while simultaneously notifying TRACON that I was taking evasive action. Their reply was along the lines of 'we just got a conflict alert here'. I continued turning left; to a heading of approximately 360; all the while scanning for the traffic (and asking my passenger to do the same). According to the skywatch display; the traffic was very close for another 20-30 seconds but we were never able to make visual contact.(my estimate of estimated miss distance in the previous section is completely speculative; based on the fact that I never saw the other aircraft. It may have been much closer; or it could have been significantly further away.) after a short while; I was given instructions to descend to 3;000 and to turn inbound to pdk. The rest of the flight proceeded uneventfully.my diversion from an assigned vector and altitude was made without explicit ATC permission; and I did not declare an emergency when I notified TRACON of my actions. I believe these actions were justified as self-protection; especially in light of the fact that I seemed to have more timely information about the flight path of the other aircraft than did TRACON at the time.this incident occurred at the end of an almost 3 hour flight; but I don't believe there were any human performance considerations involved. I am IFR current; and was alert and well-rested.

Google
 

Original NASA ASRS Text

Title: A C182 pilot took evasive action from an unsighted aircraft to which he was alerted by a Skywatch CAS which does not provide Resolution Advisories.

Narrative: Flying vector 220 on the initial approach to PDK. My Skywatch display showed a contact 300 FT low and climbing at 12 o'clock; inside 6 miles; but I didn't receive notification of this particular contact from TRACON (they had pointed out other traffic ahead; but I don't believe they mentioned this one). The contact seemed to level at my altitude and continued towards me; but I was unable to obtain a visual on it (Atlanta in the background may have made that difficult). When I got the audible warning from Skywatch about a potential collision I climbed about 200 FT and turned left while simultaneously notifying TRACON that I was taking evasive action. Their reply was along the lines of 'we just got a conflict alert here'. I continued turning left; to a heading of approximately 360; all the while scanning for the traffic (and asking my passenger to do the same). According to the Skywatch display; the traffic was very close for another 20-30 seconds but we were never able to make visual contact.(My estimate of estimated miss distance in the previous section is completely speculative; based on the fact that I never saw the other aircraft. It may have been much closer; or it could have been significantly further away.) After a short while; I was given instructions to descend to 3;000 and to turn inbound to PDK. The rest of the flight proceeded uneventfully.My diversion from an assigned vector and altitude was made without explicit ATC permission; and I did not declare an emergency when I notified TRACON of my actions. I believe these actions were justified as self-protection; especially in light of the fact that I seemed to have more timely information about the flight path of the other aircraft than did TRACON at the time.This incident occurred at the end of an almost 3 hour flight; but I don't believe there were any human performance considerations involved. I am IFR current; and was alert and well-rested.

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.