Anonymous wrote:OK, it's been 12 hours since the crash.
Not one word, not one peep out of DoD.
Where the hell is Hegseth, or at a minimum, his "crackerjack" experienced spokesman John Ullyot?
Ullyot had no problem getting the word out that they were stripping Milley of clearances just a few hours earlier.
Be he's mum on this???
Anonymous wrote:Anonymous wrote:DP. It is the helicopter but mistakes happen. The issue is not allowing human error to impact devastatingly. Do you can't let pilots take the responsibility of hopefully seeing everything that may impede their flights. You need to ensure other safety measures like providing them with specific 411 on where the prob may be and/or tech to help do same. Europe does not allow these incidents to happen for example.
There's never been a crash in Europe?
Anonymous wrote:Anonymous wrote:Anonymous wrote:Does anyone know whether helicopters crossing are supposed to wait for an affirmative okay to cross from the ATC, or whether they can cross unless told NOT to cross by ATC?
This does seem like a crazy intersection to me.
Military missions have different rules. They also are on different frequencies (although monitoring tower.) This is their normal route. It intersects the circle to land pattern for the short runway. It’s a dumb as crap situation and has been a disaster waiting to happen for years. Has nothing to do with how many flights there are at DCA or politics. The scopes are out and show this was a developing situation that ATC didn’t deconflict. And the helo pilot didn’t maintain visual separation. This was completely avoidable and while claiming trump or musk might feel good this one isn’t their fault.
The helo was flying too high.
Anonymous wrote:The was an accident waiting to happen. The airport is so congested because the technology allows the airplanes to fly with very little separation. They were landing at DCA like in a conga line.
Clearly, the helicopter pilot was seeing a different plane.
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Does anyone know whether helicopters crossing are supposed to wait for an affirmative okay to cross from the ATC, or whether they can cross unless told NOT to cross by ATC?
This does seem like a crazy intersection to me.
Military missions have different rules. They also are on different frequencies (although monitoring tower.) This is their normal route. It intersects the circle to land pattern for the short runway. It’s a dumb as crap situation and has been a disaster waiting to happen for years. Has nothing to do with how many flights there are at DCA or politics. The scopes are out and show this was a developing situation that ATC didn’t deconflict. And the helo pilot didn’t maintain visual separation. This was completely avoidable and while claiming trump or musk might feel good this one isn’t their fault.
It has everything to do with more flights. The helicopter pilot was confused because there were three planes up there with him. He thought he was visualizing the one ATC asked about. But oops! There was another plane up there he couldn’t see! The industry knew this was just a matter of time, but they wanted to keep adding new flights to the busiest runway in the nation.
https://www.protectregionalairports.com/2024/01/26/dca-is-still-the-busiest-runway-in-the-nation/
Where are you getting info that the pilot was "confused" -- how could he not see the plane he was literally flying toward for most of the end of its flight path?
I agree about the bad flight path and the overcrowding of the airport, but this made up narrative makes not sense in this situation.
Because on the ATC recording, they ask the helicopter if he sees the plane approaching and he says yes. Unfortunately ATC and the helicopter were not referring to the same plane.
Anonymous wrote:They keep sticking to the plan to reopen DCA at 11 but with so much recovery still to do will they really?
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Biden and their administration signed off on the added flights a year ago. Again the blame game doesn't work. This is a tragedy some changes will need to happen like making sure helos and airplanes are on the same frequency , this could have happened with a police or even news chopper.
The number of flights wasn't the issue here. Helicopter routes shouldn't be so close to the runway approach. Especially at night.
Why was the helicopter so close to the plane
It didn’t see it approaching. There were a couple other close by planes they were visualizing and when ATC asked them if they say it, it wasn’t clear which plane they were referring to
how do you know this? why wouldn't it be looking/seeing the plane that was directly in front of them?
Unlike jets, helicopters can fly straight up and down. While I don’t know, it is my thought that since the helicopter thought ATC was talking about another plane, it was visualizing that one. The plane they hit was not in their forward or peripheral visual field, rather it was directly above or below the helicopter and they ended up flying directly down or up into it.
but is that what happened? Or am I totally misunderstanding the video? It looks like the plane hit was directly in their forward visual field. What are you seeing that I am missing?
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Does anyone know whether helicopters crossing are supposed to wait for an affirmative okay to cross from the ATC, or whether they can cross unless told NOT to cross by ATC?
This does seem like a crazy intersection to me.
Military missions have different rules. They also are on different frequencies (although monitoring tower.) This is their normal route. It intersects the circle to land pattern for the short runway. It’s a dumb as crap situation and has been a disaster waiting to happen for years. Has nothing to do with how many flights there are at DCA or politics. The scopes are out and show this was a developing situation that ATC didn’t deconflict. And the helo pilot didn’t maintain visual separation. This was completely avoidable and while claiming trump or musk might feel good this one isn’t their fault.
It has everything to do with more flights. The helicopter pilot was confused because there were three planes up there with him. He thought he was visualizing the one ATC asked about. But oops! There was another plane up there he couldn’t see! The industry knew this was just a matter of time, but they wanted to keep adding new flights to the busiest runway in the nation.
https://www.protectregionalairports.com/2024/01/26/dca-is-still-the-busiest-runway-in-the-nation/
Where are you getting info that the pilot was "confused" -- how could he not see the plane he was literally flying toward for most of the end of its flight path?
I agree about the bad flight path and the overcrowding of the airport, but this made up narrative makes not sense in this situation.
Because on the ATC recording, they ask the helicopter if he sees the plane approaching and he says yes. Unfortunately ATC and the helicopter were not referring to the same plane.
I asked a pilot and he said no way, the other plane was too far away for this error.
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Does anyone know whether helicopters crossing are supposed to wait for an affirmative okay to cross from the ATC, or whether they can cross unless told NOT to cross by ATC?
This does seem like a crazy intersection to me.
Military missions have different rules. They also are on different frequencies (although monitoring tower.) This is their normal route. It intersects the circle to land pattern for the short runway. It’s a dumb as crap situation and has been a disaster waiting to happen for years. Has nothing to do with how many flights there are at DCA or politics. The scopes are out and show this was a developing situation that ATC didn’t deconflict. And the helo pilot didn’t maintain visual separation. This was completely avoidable and while claiming trump or musk might feel good this one isn’t their fault.
It has everything to do with more flights. The helicopter pilot was confused because there were three planes up there with him. He thought he was visualizing the one ATC asked about. But oops! There was another plane up there he couldn’t see! The industry knew this was just a matter of time, but they wanted to keep adding new flights to the busiest runway in the nation.
https://www.protectregionalairports.com/2024/01/26/dca-is-still-the-busiest-runway-in-the-nation/
Where are you getting info that the pilot was "confused" -- how could he not see the plane he was literally flying toward for most of the end of its flight path?
I agree about the bad flight path and the overcrowding of the airport, but this made up narrative makes not sense in this situation.
DP. Sounds like the helicopter had visual contact with the other plane taking off that is seen in the crash video. They likely hit the plane at the wing so the airline pilots had no idea it was coming and no time to react.
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Biden and their administration signed off on the added flights a year ago. Again the blame game doesn't work. This is a tragedy some changes will need to happen like making sure helos and airplanes are on the same frequency , this could have happened with a police or even news chopper.
The number of flights wasn't the issue here. Helicopter routes shouldn't be so close to the runway approach. Especially at night.
Why was the helicopter so close to the plane
It was focused on other planes and thought it was Ok. Poor comms. Dark at night.
You are guessing. But that seems implausible given the flight path and the fact that they had to be looking straight at the plane before impact. It seems impossible for them to not see the brightly lit plane they flying toward.
Who gets to listen to the dark box and wtf was really going in or discussing in the cockpit of the helo the last 2 mins of its river trip?
Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Anonymous wrote:Biden and their administration signed off on the added flights a year ago. Again the blame game doesn't work. This is a tragedy some changes will need to happen like making sure helos and airplanes are on the same frequency , this could have happened with a police or even news chopper.
The number of flights wasn't the issue here. Helicopter routes shouldn't be so close to the runway approach. Especially at night.
Why was the helicopter so close to the plane
It didn’t see it approaching. There were a couple other close by planes they were visualizing and when ATC asked them if they say it, it wasn’t clear which plane they were referring to
how do you know this? why wouldn't it be looking/seeing the plane that was directly in front of them?
Unlike jets, helicopters can fly straight up and down. While I don’t know, it is my thought that since the helicopter thought ATC was talking about another plane, it was visualizing that one. The plane they hit was not in their forward or peripheral visual field, rather it was directly above or below the helicopter and they ended up flying directly down or up into it.
but is that what happened? Or am I totally misunderstanding the video? It looks like the plane hit was directly in their forward visual field. What are you seeing that I am missing?