Last edited:
...
I'm not sure that the controller did anything wrong here, but there will be a push to blame him and the regional jet crew simply to preserve the hero status of the military guys. It happens every time.
...
But what happens when that aircraft has wrongly identified the traffic?
...
Exactly. From a non-expert perspective, it seems like air traffic control would be the only entity to be able to accurately identify the mistake and potential collision.
Correct.
The traffic collision and avoidance system should have given the rj crew an indication of where the helicopter was if the helo's transponder was on and in a mode that was civilian decypherable.
The TCAS would not give a conflict action warning less than 1000 above the ground.
Not that this is a total pass, but a night visual approach to a short runway can be quite difficult and the crew has better things to do than look 90 degrees out the window for possible traffic when you are 350' above the ground.
...
So, if this is accurate, there were some collision warnings given prior to impact.
it appears that AA5342 was making a slow turn for final, what us small fry would call out as "base leg to final", while the PAT25 maintained course and speed.
https://x.com/rawsalerts/status/1884827088437264387
25 second warning isn't very helpful unless it is blaring in the actual cockpits.
And so much for the hypothesis since the beginning that the helicopter has it's transponder turned off, and thus was off the radar.
BH pilot also ignored multiple orders to land.
Is there positive proof of this?