Narrative:

While making an initial descent toward T57 as part of solo training operations in pursuit of a private helicopter rating; I received a traffic alert for a traffic conflict at 10 [o'clock] less than 1 mile same altitude. It was the first warning or indication of traffic in my proximity that I received. By the time I located the conflicting traffic; the traffic was less than 1/2 mile and on a converging course. I did not want to turn away from the conflicting traffic and risk losing sight of the traffic; so I began a climb while watching to ensure that the conflicting traffic did not climb also. It appeared that I would pass over the traffic and was unclear if the conflicting traffic began a descent. Based upon when I lost sight of the conflicting traffic; I estimate that I passed directly overhead of that traffic with a vertical separation of approximately 300'.once clear of the conflict; I continued my descent for the helipad at T57. I'm not sure if the conflicting traffic had just popped up on the traffic alert display immediately prior to giving the aural warning. Usually the traffic alert will turn a target yellow and provide additional time to locate the traffic. In this case the warning proved sufficient to avoid a collision; but insufficient to maintain the desired vertical separation.additional factors were the relatively low-time in category and proximity to the helipad which caused my attention to be focused on finding the helipad and reduced my traffic scan area.

Related reports:

Google
 

Original NASA ASRS Text

Title: Helicopter pilot reported a NMAC with another helicopter at T57.

Narrative: While making an initial descent toward T57 as part of solo training operations in pursuit of a Private Helicopter Rating; I received a Traffic alert for a traffic conflict at 10 [o'clock] less than 1 mile same altitude. It was the first warning or indication of traffic in my proximity that I received. By the time I located the conflicting traffic; the traffic was less than 1/2 mile and on a converging course. I did not want to turn away from the conflicting traffic and risk losing sight of the traffic; so I began a climb while watching to ensure that the conflicting traffic did not climb also. It appeared that I would pass over the traffic and was unclear if the conflicting traffic began a descent. Based upon when I lost sight of the conflicting traffic; I estimate that I passed directly overhead of that traffic with a vertical separation of approximately 300'.Once clear of the conflict; I continued my descent for the helipad at T57. I'm not sure if the conflicting traffic had just popped up on the Traffic Alert display immediately prior to giving the aural warning. Usually the Traffic Alert will turn a target yellow and provide additional time to locate the traffic. In this case the warning proved sufficient to avoid a collision; but insufficient to maintain the desired vertical separation.Additional factors were the relatively low-time in category and proximity to the helipad which caused my attention to be focused on finding the helipad and reduced my traffic scan area.

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.