Posts about: "AA5342" [Posts: 21 Page: 1 of 2]

Oro-o
January 30, 2025, 02:52:00 GMT
permalink
Post: 11816788
Updated info says it is a DC Police Eurocopter, others say US Army. PSA operating as AA5342, Wichita to DCA.

Collision captured on Kennedy Center web cam, link to X post with it:


Subjects AA5342  DCA

Links are to this post in the relevant subject page so that this post can be seen in context.

No recorded likes for this post (could be before pprune supported 'likes').

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

MitrePeak
January 30, 2025, 04:14:00 GMT
permalink
Post: 11816850
Video of collision

Originally Posted by Anti Skid On
News coming in of an incident with an American Eagle CRJ operating AA5342 colliding with a military Sikorsky over Washington
Plane crashes near Washington DC after mid-air collision with military helicopter \x96 follow live
Flightradar24 snot showing anything of note.

Update - everything grounded at Reagan International and Helicopters searching over the Potomac
Video of collision..


Subjects AA5342  CRJ  FAA

Links are to this post in the relevant subject page so that this post can be seen in context.

No recorded likes for this post (could be before pprune supported 'likes').

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

TachyonID
January 30, 2025, 20:39:00 GMT
permalink
Post: 11817633
Comms

Since the Blackhawk pilot was on a different (military) band is it possible he thought AA5342 was landing on 1, not 33?
He may have missed the landing permission to 33 for 5342, even as he lost SA being focused on a plane further out on approach to 1.
He clearly heard the instructions of the LC and responded to the LC, but was badly out of position WRT the approach to 33.
The recreation makes it appear that he was staying parallel to the 1 approach, probably waiting for the "next in line", the landing lights he probably was fixated on.


Subjects AA5342  Blackhawk (H-60)  Situational Awareness

Links are to this post in the relevant subject page so that this post can be seen in context.

5 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

KRviator
January 30, 2025, 21:42:00 GMT
permalink
Post: 11817677
Originally Posted by TachyonID
Since the Blackhawk pilot was on a different (military) band is it possible he thought AA5342 was landing on 1, not 33?
He may have missed the landing permission to 33 for 5342, even as he lost SA being focused on a plane further out on approach to 1.
He clearly heard the instructions of the LC and responded to the LC, but was badly out of position WRT the approach to 33.
The recreation makes it appear that he was staying parallel to the 1 approach, probably waiting for the "next in line", the landing lights he probably was fixated on.
What makes you think the BlackHawk crew were on UHF, not VHF? Every military aircraft I've ever flown in - and there's been a few - speak to civilian controllers on civil VHF frequencies.

Subjects AA5342  Blackhawk (H-60)  Situational Awareness

Links are to this post in the relevant subject page so that this post can be seen in context.

1 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

artee
January 31, 2025, 03:15:00 GMT
permalink
Post: 11817877
Originally Posted by dr dre
TWR gives AA5342 as traffic to the helicopter, stating they are over the Woodrow (Wilson) bridge, however the helicopter crew keeps flying into the final approach path of R33. 40 seconds later TWR again asks if they have the “CRJ” in sight, and they reply they have, but at this point the CRJ is less than 200’ above them and only 0.5nm away. At the same time the following aircraft on approach to R01, an AA A319 on flight 3130, is above the Woodrow Bridge on finals. Possibly the helicopter crew at some point confused the A319 for the CRJ.

The helicopter crew again confirms they have “the aircraft” in sight and requests visual separation, but surely if they had the CRJ in sight at less than 200’ vertically and half a mile away they would be taking immediate evasive action and not requesting visual separation???
SLF here, so please don't shout.

It doesn't seem "fair" for aircraft like the CRJ, that in busy, complex airspace, another aircraft can request and receive VFR, meaning in broad terms, they're outside of ATC's guardrails. CRJ now have an aircraft in the vicinity that isn't being controlled by ATC.

Doesn't seem like a good process to an outsider.

Subjects AA5342  ATC  CRJ  Separation (ALL)  VFR  Visual Separation

Links are to this post in the relevant subject page so that this post can be seen in context.

3 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

WideScreen
January 31, 2025, 04:58:00 GMT
permalink
Post: 11817916
Originally Posted by dr dre
TWR gives AA5342 as traffic to the helicopter, stating they are over the Woodrow (Wilson) bridge, however the helicopter crew keeps flying into the final approach path of R33. 40 seconds later TWR again asks if they have the “CRJ” in sight, and they reply they have, but at this point the CRJ is less than 200’ above them and only 0.5nm away. At the same time the following aircraft on approach to R01, an AA A319 on flight 3130, is above the Woodrow Bridge on finals. Possibly the helicopter crew at some point confused the A319 for the CRJ.

The helicopter crew again confirms they have “the aircraft” in sight and requests visual separation, but surely if they had the CRJ in sight at less than 200’ vertically and half a mile away they would be taking immediate evasive action and not requesting visual separation???
The whole mechanism of "aircraft in sight" no longer works, when the airspace is crowded: "Which aircraft are you supposed to have in sight" ???????

Originally Posted by Ollie Onion
It seems pretty clear what happened. The helicopter crew had confirmed they had the CRJ in sight and were happy to remain clear and pass behind. The ATC cleared them to maintain visual separation, the helicopter turned right as presumably this put them on the shortest course to where they wanted to go. At this point the ATC has NO further responsibility for separation, that is now the SOLE responsibility of the helicopter crew who accepted it. Clearly they did not have the CRJ in sight, what they were looking at will only ever be conjecture. Visual separation at night in such a busy piece of airspace is clearly a ridiculous procedure..... but it is a procedure that can currently be used. The ATC did nothing wrong, the CRJ crew did nothing wrong and more than likely the helicopter crew PROBABLY didn't do anything g wrong on purpose, there was o ly one airaft though out of place, a situation ONLY possible through an outdated and potentially dangerous procedure. My airline doesn't allow visual separation either day or night and only allows visual approaches by day, why be GA in Jets with paying passengers?
Yep, the system in place just does not work once the airspace becomes crowded, "IE which airplane are you supposed to have in sight" ?

With only one other airplane, it's clear, with more than 1, it becomes a gamble.


Originally Posted by galaxy flyer
This has been “litigated” before on PPRUNE. In the US, there is NO Missed Approach Procedure.

AIM 5-4-23

e. A visual approach is not an IAP and therefore has no missed approach segment. If a go around is necessary for any reason, aircraft operating at controlled airports will be issued an appropriate advisory/clearance/instruction by the tower. At uncontrolled airports, aircraft are expected to remain clear of clouds and complete a landing as soon as possible. If a landing cannot be accomplished, the aircraft is expected to remain clear of clouds and contact ATC as soon as possible for further clearance. Separation from other IFR aircraft will be maintained under these circumstances.
For VFR there is a missed approach procedure: Back into the circuit. Which will be a bit hairy, when the "miss" happens (long) before reaching the runway. Depending on the aircraft type, 2 circuit types may be defined: A small one for slow stuff and a large one for the bigger ones. And as usual with VFR traffic, ATC or self-communication is needed to pick the moment of the next landing attempt.

One can discuss whether this is a procedure or not, though there is at least "something".

Subjects AA5342  ATC  CRJ  IFR  Pass Behind  Pass Behind (All)  Separation (ALL)  VFR  Visual Separation

Links are to this post in the relevant subject page so that this post can be seen in context.

No recorded likes for this post (could be before pprune supported 'likes').

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

T28B
February 01, 2025, 03:14:00 GMT
permalink
Post: 11818731
I shall remind you all again, as Pilot DAR has already reminded you all: keep the politics out of this.
If you can't post professionally on the aviation matters to hand, then don't post.

Whether or not the FAA has, or has not, fulfilled it's role is a functional, not political, matter if you can be bothered to constrain yourselves to the functional aspects of regulation.

You will not be warned again.

EDITED this post due to a link problem:
AA5342 Down DCA

The moderators have had a background discussion about this situation, and agreed to stand by the exclusion of political discussion as is the policy of PPRuNe. That said, this accident, and the investigation and introspection to come are going to run the ragged edge of political discussion. We want the aviation safety discussion, we don't want it lost in discussion and emotion about politics - we just don't have the page space! (and it's a lot of work to moderate!).

Posts referencing actual facts, reported from authoritative sources, and primarily on the topic of the accident, the investigation, and associated safety are welcomed here. If in doubt, just leave out the political part of what you're thinking to write, we all know that you have an opinion, we don't need to read it here. If your post touches to role of a government official as a factor of the event, without inflaming discussion, the moderation team will do it's best to find a favourable interpretation.

Thanks for working with the moderation team on this...

Pilot DAR
Carry on.

Last edited by T28B; 2nd February 2025 at 19:01 . Reason: link problem required an edit

Subjects AA5342  DCA  FAA  Thread Moderation

Links are to this post in the relevant subject page so that this post can be seen in context.

No recorded likes for this post (could be before pprune supported 'likes').

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

T28B
February 02, 2025, 19:09:00 GMT
permalink
Post: 11820017
Greetings, esteemed colleagues.
Before Monday arrives and the posting rate increases, I will repeat the guidance that Pilot DAR provided a few days ago.
AA5342 Down DCA

The moderators have had a background discussion about this situation, and agreed to stand by the exclusion of political discussion as is the policy of PPRuNe. That said, this accident, and the investigation and introspection to come are going to run the ragged edge of political discussion. We want the aviation safety discussion, we don't want it lost in discussion and emotion about politics - we just don't have the page space! (and it's a lot of work to moderate!).

Posts referencing actual facts, reported from authoritative sources, and primarily on the topic of the accident, the investigation, and associated safety are welcomed here. If in doubt, just leave out the political part of what you're thinking to write, we all know that you have an opinion, we don't need to read it here. If your post touches to role of a government official as a factor of the event, without inflaming discussion, the moderation team will do it's best to find a favourable interpretation.

Thanks for working with the moderation team on this...

Pilot DAR
I will offer one further point of guidance:

If you are (as many PPRuNe members are) a fixed wing civil aviator, or air transport pilot, I'll ask you not to post about (1) helicopter operations and (2) military flying unless you also have experience in both of those areas of endeavor that relates to this tragic accident. There are a number of our members who have that experience, so let's not let our noise drown out their signal.

We've had to remove some noise. I have received a few well founded complaints about the uninformed commentary about both rotary wing flying, and military flying.

Please do not play the role of the sciolist, but instead speak from your own actual professional experience and knowledge. If you have something to critique about the mixing of helicopter and fixed wing operations at and around civil airports, please be temperate and professional in your language.

Thank you all in advance for your cooperation in keeping this discussion professional.

Subjects AA5342  DCA  Thread Moderation

Links are to this post in the relevant subject page so that this post can be seen in context.

23 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

airplanecrazy
February 05, 2025, 19:16:00 GMT
permalink
Post: 11822469
Originally Posted by JohnDixson
Dibo/fdr: keep wondering why the Hawk crew made that last correction to the right.
I don't think it make a significant turn right, and I believe that what you are seeing is positional inaccuracy due to MLAT position limitations in the ADS-B Exchange data. According to Flightradar24, " MLAT position calculations have a general accuracy of 10-100 meters and 1000 meters in the worst cases." Given that, I believe this previous post from MikeSnow AA5342 Down DCA represents our best current understanding of the actual helicopter track and its relation to Route 4 (until we get more information from the NTSB). I generated my own zoomed overlay and got essentially the same results



The position of the collision shown in the radar data overlay is consistent with the position of the RJ as shown in ADS-B Exchange at the time of the collision (approximately 01:47:59Z according to the NTSB timeline). See this link from DIBO for the RJ Track with timing AA5342 Down DCA In my experience, times in ADS-B Exchange are generally accurate to within 2 seconds. Given all that, I believe that the Black Hawk was within the horizontal bounds of Route 4 at the time of the collision and that it did not make the right turn we see in the ADS-B Exchange map.

Edit: Corrected route number and helicopter








Last edited by airplanecrazy; 6th February 2025 at 01:24 .

Subjects AA5342  ADSB (All)  Blackhawk (H-60)  DCA  NTSB  Radar  Route 4

Links are to this post in the relevant subject page so that this post can be seen in context.

3 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

PPRuNeUser548247
February 07, 2025, 10:20:00 GMT
permalink
Post: 11823511
The deactivation of the PAT25's ADS-B system meant that it was not broadcasting its position, making it invisible to systems that rely on ADS-B data for situational awareness, including those on AA534. There would be no signal from PAT25 to trigger TCAS alerts to pilots of AA5342. NTSB also said it was 'likely' PAT25 crew were wearing night-vision goggles, which have greatly reduced field of view, as little as 40 degrees

Quite extraordinary for a supposed 'recertification' flight.


Subjects AA5342  ADSB (All)  NTSB  PAT25  Situational Awareness  TCAS (All)

Links are to this post in the relevant subject page so that this post can be seen in context.

No recorded likes for this post (could be before pprune supported 'likes').

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

hoistop
February 07, 2025, 11:01:00 GMT
permalink
Post: 11823555
Originally Posted by The Brigadier
The deactivation of the PAT25's ADS-B system meant that it was not broadcasting its position, making it invisible to systems that rely on ADS-B data for situational awareness, including those on AA534. There would be no signal from PAT25 to trigger TCAS alerts to pilots of AA5342. NTSB also said it was 'likely' PAT25 crew were wearing night-vision goggles, which have greatly reduced field of view, as little as 40 degrees

Quite extraordinary for a supposed 'recertification' flight.

Yes, but their ATC transponder was obviously operating normally in C mode. That should be enough to show PAT25 on CRJ screen as traffic, even if no RA was given (bearing in mind, they were cca 300ft AGL) It is of course completelly unreasonable to expect that CRJ crew should see or even avoid the Blackhawk incoming from (slightly) right, as they were merely 20-ish seconds from touchdown and manually aligning with the runway. Also, I believe that operating ATC transponder on Blackhawk allowed for clear view on ATC screen and I wonder if there was no alarm triggered on ATC computers - they probably do have such guard software in operation on DCA?
In another midair collision report, that happened in July 2022 at NorthLas Vegas airport, NTSB put out this:
Interviews with personnel at the air traffic control tower indicated that staffing was deficient, and most staff were required to work mandatory overtime shifts, reaching an annual average of 400 to 500 hours of overtime per controller. According to the air traffic manager (ATM), the inadequate staffing had resulted in reduced training discissions, and the management team was unable to appropriately monitor employee performance. The ATM stated that everyone on the team was exhausted, and that work/life balance was non-existent. It is likely that the cumulative effects of continued deficient staffing, excessive overtime, reduced training, and inadequate recovery time between shifts took a considerable toll on the control tower workforce.
I wonder, how this situation is with DCA ATC service.
I am not trying to blame ATC either. He issued clearance to PAT25 to cross behind and asked (and got) confirmation for CRJ in sight twice. It seems quite clear that helicopter crew did not look at the same airplane that ATC was asking about.
What baffles me here is, that it was obvious a routine procedure to let helicopters cross active runway heading less than 2 miles from runway treshold, leaving practically zero margin for error. Backups, designed to catch pilots or ATC errors (TCAS and ATC alarms) cannot catch up in short time left if someone makes a mistake, so this arrangement as based on "see and avoid" concept, in the night, with many lights in the background and a fact, that other aircraft on collision course does not move relatively on the screen, but just grows bigger. Unfortunatelly, that dot on the screen that will kill you starts growing bigger only in the last few seconds.
If I would ask ATC to cross runway heading DAY VFR so close to runway treshold at my airport with incoming commercial traffic, I would be denied 100 times out of 100 attempts. (and probably called nuts).
My guess on this tragedy is, that thru the years, the system was trying to pack more and more aircraft in the same space and same infrastructure, by gradually squeezing margins and safegueards, until one day, Jenga tower collapsed.




Subjects AA5342  ADSB (All)  ATC  Blackhawk (H-60)  CRJ  DCA  NTSB  PAT25  See and Avoid  Situational Awareness  TCAS (All)  VFR

Links are to this post in the relevant subject page so that this post can be seen in context.

3 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

Capn Bloggs
February 07, 2025, 11:52:00 GMT
permalink
Post: 11823587
Originally Posted by The Brigadier
There would be no signal from PAT25 to trigger TCAS alerts to pilots of AA5342.
TCAS does not require, nor use, ADS-B information (yet). If the PAT had it's Mode C ON, the TCAS on the CRJ would give full warnings... if it was high enough, which it wasn't. However, the TCAS issued a Traffic Advisory "Traffic Traffic" as the CRJ passed through 500ft (as per the NTSB briefing).

Subjects AA5342  ADSB (All)  CRJ  NTSB  PAT25  TCAS (All)

Links are to this post in the relevant subject page so that this post can be seen in context.

2 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

51bravo
February 07, 2025, 11:55:00 GMT
permalink
Post: 11823592
Originally Posted by paulross
The original NYT article thanks to the Internet Archive (archive.org) .
Thanks for the picture. So three possible light blobs very close together AA5307 (short of landing), AA5342 (the CRJ), AA3130 (which was picked by PAl25 as conflict)

Regarding to the Pavlovian - if PAL25 wouldnt have requested 'visual separation', what "punishment" would they expect from the Tower? Orbit(s)? Vectors? Or somethin wild, considering 200/300' altitude limits along the river and buildings/infrastructure left and right (what diameter would an orbit cost with a Blackhawk, is it feasible over black water at 200')? Therefore I am asking - would a non-request of a 'visual separation' mean major complications to such a helicopter at night? That as well would then be a significant flaw in the design.

Subjects AA5342  Blackhawk (H-60)  CRJ  New York Times  Separation (ALL)  Visual Separation

Links are to this post in the relevant subject page so that this post can be seen in context.

1 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

Someone Somewhere
February 07, 2025, 12:05:00 GMT
permalink
Post: 11823605
Originally Posted by 51bravo
Thanks for the picture. So three possible light blobs very close together AA5307 (short of landing), AA5342 (the CRJ), AA3130 (which was picked by PAl25 as conflict)

Regarding to the Pavlovian - if PAL25 wouldnt have requested 'visual separation', what "punishment" would they expect from the Tower? Orbit(s)? Vectors? Or somethin wild, considering 200/300' altitude limits along the river and buildings/infrastructure left and right (what diameter would an orbit cost with a Blackhawk, is it feasible over black water at 200')? Therefore I am asking - would a non-request of a 'visual separation' mean major complications to such a helicopter at night? That as well would then be a significant flaw in the design.
I believe visual separation from other aircraft is a very different scenario to visual separation from ground obstacles (VFR).

Waiting for the tower to have no aircraft below ~700ft in the approach area, if we're assuming a 1.5Nm separation, could be quite a while.

Subjects AA5342  Blackhawk (H-60)  CRJ  Separation (ALL)  VFR  Visual Separation

Links are to this post in the relevant subject page so that this post can be seen in context.

No recorded likes for this post (could be before pprune supported 'likes').

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

YRP
February 07, 2025, 22:36:00 GMT
permalink
Post: 11823982
Originally Posted by The Brigadier
The deactivation of the PAT25's ADS-B system meant that it was not broadcasting its position, making it invisible to systems that rely on ADS-B data for situational awareness, including those on AA534. There would be no signal from PAT25 to trigger TCAS alerts to pilots of AA5342. NTSB also said it was 'likely' PAT25 crew were wearing night-vision goggles, which have greatly reduced field of view, as little as 40 degrees

Quite extraordinary for a supposed 'recertification' flight.
As someone mentioned above, ADS-B isn't used by/for TCAS. TCAS doesn't work below 500' for various reasons.

The recertification flight might specifically need to be at night. It might even specifically require NVG. I also wonder if both pilots would be on NVG or just one of the two.

Last edited by YRP; 7th February 2025 at 22:49 . Reason: Edited to sound 10% less grumpy

Subjects AA5342  ADSB (All)  NTSB  Night Vision Goggles (NVG)  PAT25  Situational Awareness  TCAS (All)

Links are to this post in the relevant subject page so that this post can be seen in context.

2 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

missy
February 22, 2025, 13:16:00 GMT
permalink
Post: 11833660
Originally Posted by Fortissimo
The glide path for London City is 5\xbd\xb0 and obviously requires some bespoke training and approvals. I am not suggesting that you would do the same at DCA, but a 4\xb0 slope should be achievable for R33, which would add a margin that would take out many of the 'incursions' shown in airplancrazy's excellent diagram. If you don't have the training to fly a 4\xb0 slope, you simply refuse the request to circle.
Interesting theory. As we all know AA5342 was switched from RWY 01 to a visual approach to RWY 33. Is it just me but I fail to see how a 4\xb0 slope would be achieved on a visual approach.

Subjects AA5342  DCA

Links are to this post in the relevant subject page so that this post can be seen in context.

No recorded likes for this post (could be before pprune supported 'likes').

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

Old Boeing Driver
March 26, 2025, 03:33:00 GMT
permalink
Post: 11854333
I have 2 questions

I have used HUD and FLIR, but never NVG's. Could the helo crew actually see the aircraft on final for 01? I think at the time they were 6 miles apart.

Also, AA5342 received a TA and continued the approach for 18 seconds until the collision occurred. I realize an RA would not occur there, but would their SOP's suggest a G/A on receiving a TA at that position on the approach?

Apologize if these have been answered.

Regards,

OBD

Last edited by Old Boeing Driver; 26th March 2025 at 03:35 . Reason: Grammar

Subjects AA5342  HUD  Night Vision Goggles (NVG)

Links are to this post in the relevant subject page so that this post can be seen in context.

1 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

MechEngr
July 31, 2025, 23:36:00 GMT
permalink
Post: 11931584
No matter, radalt only gives the altitude above some actual thing, not a shared pressure altitude that all air vehicles can agree on. AA5342 was not on a radalt path. AA5342 was flying over buildings.

EDIT: I also appreciate the arriving jet was on a geometric glide slope and that radalt under the glideslope could have been sufficient, but if one is expecting that vertical separation is sufficient then there needs to be certainty to that altitude and clearly that isn't possible on barometric altimeter and should never have been accepted by anyone.

Last edited by MechEngr; 1st August 2025 at 05:39 .

Subjects AA5342  Barometric Altimeter  Separation (ALL)  Vertical Separation

Links are to this post in the relevant subject page so that this post can be seen in context.

No recorded likes for this post (could be before pprune supported 'likes').

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

missy
August 12, 2025, 04:41:00 GMT
permalink
Post: 11937043
Originally Posted by Sailvi767
As I posted on here before I had that exact same scenario happen to me on runway 33 in DCA. Traffic closing on a collision course on TCAS. Tower reported the traffic had us in sight. When the traffic closed to \xbd mile with no vector change apparent We went around from 400 feet. We never saw the traffic. Tower chewed my butt saying the traffic had us in sight. I didn\x92t care.
Actually, it's not the exact same scenario.

In the case you quote, Tower reported the traffic had you in sight. In the case in question, AA5342 was not provided traffic by the DCA LC.
In the case you quote, did Tower say that the traffic was going to maintain own separation? Did Tower provide a bearing/direction and distance to this traffic? Did Tower provide the height of the traffic?


Subjects AA5342  DCA  Separation (ALL)  TCAS (All)  Traffic in Sight

Links are to this post in the relevant subject page so that this post can be seen in context.

1 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.

Sailvi767
August 23, 2025, 02:15:00 GMT
permalink
Post: 11942779
Originally Posted by missy
Actually, it's not the exact same scenario.

In the case you quote, Tower reported the traffic had you in sight. In the case in question, AA5342 was not provided traffic by the DCA LC.
In the case you quote, did Tower say that the traffic was going to maintain own separation? Did Tower provide a bearing/direction and distance to this traffic? Did Tower provide the height of the traffic?
Tower stated helo traffic was transiting the river at 200 feet and had us in sight. When he closed to less than 3000 feet on a constant bearing on TCAS we went around. Probably would have been fine 999 out of 1000 times. Not odds I accept.

Subjects AA5342  DCA  Separation (ALL)  TCAS (All)  Traffic in Sight

Links are to this post in the relevant subject page so that this post can be seen in context.

1 recorded likes for this post.

Reply to this quoting this original post. You need to be logged in. Not available on closed threads.