Narrative:

Just after sunset; cleared visual approach to xxl in ZZZ. On the base turn; while getting set up on the approach and checking in with tower; they mention that there will be VFR traffic in the pattern for runway xy at a nearby airport; ZZZ1. We acknowledge but did not yet see the traffic; and were still turning in. The first officer (first officer) was flying; and set up on a good stabilized visual approach using the ILS as backup. I did see one TCAS hit to the left of course and a few miles away; initially assumed that was our traffic.closer in; around the FAF; tower again mentions traffic; but I respond that we didn't see it. I don't recall my exact words; probably negative contact. At this point we look in and see a TCAS hit directly ahead and slightly below. I continue to look outside for the traffic; but don't see it due to lots of lights against the dark ground. Initially I wasn't concerned as we didn't have an RA (resolution advisory); or even a yellow colored traffic icon. But at this point I see we are only 400 feet away. My first officer was on the ball; and before I could even say anything he leveled off and offset to the right. We were near the fix zzzzz at this point; about 800 AGL; and were on course and glide path when we stopped the descent. The closest we saw on the TCAS was 300 feet separation; and the TCAS traffic icon was merged with ours; no separation. We never acquired the traffic visually.if we had not stopped the descent and offset; we would have been much closer than 300 feet. I can't say we would have collided; but it is definitely in the realm of possibilities. I can't emphasize enough how high a threat this situation was. When we landed we queried the tower; and they just said it was traffic in the pattern; as if it happened all the time. At no point did they display any urgency as to the position of the traffic relative to us.furthermore; we then realized that the reason we never got an RA was that we had just descended below 900 feet; and TCAS was therefore inhibited. In real time; that had not occurred to us; as we were too busy trying to find the traffic; fly the approach; then make corrections to avoid a collision.our best guess is that the VFR traffic had just departed runway xy; was somewhere around 500 AGL and either level or slightly climbing; but still flying towards ZZZ; i.e.; had not yet turned crosswind. This meant it was flying directly in to the glide path for runway xxl at ZZZ; which we happened to be on at the time. We could not see them due to ground light clutter and deck angle; they were probably flying in the same direction as us and therefore could not see us descending from behind; no RA was available due to altitude inhibit; and we were not getting any kind of avoidance instructions from tower. We were exactly where we were supposed to be; in full communication with ATC; yet still were placed in a dangerous situation.

Related reports:

Google
 

Original NASA ASRS Text

Title: A320 Captain reported experiencing a near mid-air collision during approach to landing.

Narrative: Just after sunset; cleared visual approach to XXL in ZZZ. On the base turn; while getting set up on the approach and checking in with Tower; they mention that there will be VFR traffic in the pattern for Runway XY at a nearby airport; ZZZ1. We acknowledge but did not yet see the traffic; and were still turning in. The FO (First Officer) was flying; and set up on a good stabilized visual approach using the ILS as backup. I did see one TCAS hit to the left of course and a few miles away; initially assumed that was our traffic.Closer in; around the FAF; Tower again mentions traffic; but I respond that we didn't see it. I don't recall my exact words; probably negative contact. At this point we look in and see a TCAS hit directly ahead and slightly below. I continue to look outside for the traffic; but don't see it due to lots of lights against the dark ground. Initially I wasn't concerned as we didn't have an RA (Resolution Advisory); or even a yellow colored traffic icon. But at this point I see we are only 400 feet away. My FO was on the ball; and before I could even say anything he leveled off and offset to the right. We were near the fix ZZZZZ at this point; about 800 AGL; and were on course and glide path when we stopped the descent. The closest we saw on the TCAS was 300 feet separation; and the TCAS traffic icon was merged with ours; no separation. We never acquired the traffic visually.If we had not stopped the descent and offset; we would have been much closer than 300 feet. I can't say we would have collided; but it is definitely in the realm of possibilities. I can't emphasize enough how high a threat this situation was. When we landed we queried the Tower; and they just said it was traffic in the pattern; as if it happened all the time. At no point did they display any urgency as to the position of the traffic relative to us.Furthermore; we then realized that the reason we never got an RA was that we had just descended below 900 feet; and TCAS was therefore inhibited. In real time; that had not occurred to us; as we were too busy trying to find the traffic; fly the approach; then make corrections to avoid a collision.Our best guess is that the VFR traffic had just departed Runway XY; was somewhere around 500 AGL and either level or slightly climbing; but still flying towards ZZZ; i.e.; had not yet turned crosswind. This meant it was flying directly in to the glide path for Runway XXL at ZZZ; which we happened to be on at the time. We could not see them due to ground light clutter and deck angle; they were probably flying in the same direction as us and therefore could not see us descending from behind; no RA was available due to altitude inhibit; and we were not getting any kind of avoidance instructions from Tower. We were exactly where we were supposed to be; in full communication with ATC; yet still were placed in a dangerous situation.

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.