- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
re: .
Posted on 2/1/25 at 9:15 am to jizzle6609
Posted on 2/1/25 at 9:15 am to jizzle6609
SIAP
Heard on the news last night that a controller was approved to end their shift early, a few hours before the crash.
Also, ATC recording from the night before the crash indicates a jet had aborted a landing due to helo traffic.
Heard on the news last night that a controller was approved to end their shift early, a few hours before the crash.
Also, ATC recording from the night before the crash indicates a jet had aborted a landing due to helo traffic.
Posted on 2/1/25 at 9:17 am to Hateradedrink
quote:
We need to know who was on the plane that was crashed into
It would be almost impossible to identify the correct plane at night.
Either a colossal screwup or a random target.
Posted on 2/1/25 at 9:28 am to Bestbank Tiger
quote:
It would be almost impossible to identify the correct plane at night.
Nah. Foreflight, which is a general aviation app not used by airlines, has this capability. If Foreflight has it, I’d imagine it wouldn’t be difficult if they wanted to.
I’m not at all suggesting that’s what happened, just pointing out it wouldn’t be too hard. It’d be much more difficult to time that collision than it would be to ID the aircraft.
Posted on 2/1/25 at 10:19 am to Tuscaloosa
Of all the things I've seen so far, the theory of them looking at the wrong plane makes the most sense to me. I'd expect the black box to be definitive.
Which of the helo pilots were communicating with the air control? Didn't sound like a female voice
Which of the helo pilots were communicating with the air control? Didn't sound like a female voice
Posted on 2/1/25 at 10:58 am to castorinho
quote:
Of all the things I've seen so far, the theory of them looking at the wrong plane makes the most sense to me.
I think that’s the most plausible scenario, but the “wrong airplane” has frequently been referred to as a departing aircraft, which isn’t plausible. I think the consensus is if this theory is true, they were likely looking at AA3130, who was inbound to Rwy 1.
That still doesn’t explain their altitude deviations or relative position even to that other aircraft. Odd, either way.
Pilot on the radios was most likely the instructor pilot.
This post was edited on 2/1/25 at 11:00 am
Posted on 2/1/25 at 11:17 am to Tuscaloosa
I know virtually nothing about how all of this operates, but the thing that strikes me as odd is at the time that the Helo pilot acknowledges the plane that he says he's going to keep an eye on, wouldn't 3130 have been 2-3+ miles away?
The remarks about the departing aircraft, (which are STILL being made) are silly. It would have been sitting on the runway, hurtling down the runway or again, a couple of miles away to the NNW, (at impact).
The remarks about the departing aircraft, (which are STILL being made) are silly. It would have been sitting on the runway, hurtling down the runway or again, a couple of miles away to the NNW, (at impact).
This post was edited on 2/1/25 at 11:21 am
Posted on 2/1/25 at 11:22 am to Tuscaloosa
Doesn't it explain the relative position though? If AA3130 proceeds to land from that position the helo passes behind it tracking along east bank river. Add some spatial disorientation or.misjudging of visual cues and it's feasible helo thought they were laterally separated (which they were.from AA3130).
As in most mishaps several mistakes compound. There was presumably a mistaken visual on wrong a/c plus an altitude deviation. We don't know what CRM and/or equipment issues were at play. Hopefully data reveals if there was some task fixation, broken crew contracts/coordination, etc...
As in most mishaps several mistakes compound. There was presumably a mistaken visual on wrong a/c plus an altitude deviation. We don't know what CRM and/or equipment issues were at play. Hopefully data reveals if there was some task fixation, broken crew contracts/coordination, etc...
Posted on 2/1/25 at 11:24 am to TorchtheFlyingTiger
quote:
Doesn't it explain the relative position though? If AA3130 proceeds to land from that position the helo passes behind it tracking along east bank river. Add some spatial disorientation or.misjudging of visual cues and it's feasible helo thought they were laterally separated (which they were.from AA3130).
You certainly could be right about this, especially considering their track along the river. Makes sense.
Posted on 2/1/25 at 12:08 pm to Tuscaloosa
This is just my conjecture but it just came to mind.
Assuming helo crew has wrong a/c visual and thinks they are well clear. Their biggest concern is presumably avoiding water while proceeding low level. Is it conceivable that the landing lights of aircraft converging from above and off peripheral creates a sudden visual effect / distortion as it casts shadows off helo/rotor and glare off water. (Not to mention possible NVG) Since aircraft is turning and descending from above.and.at an angle it seems it might have created a sort of spotlighting effect on the helo.
If so, aircrew may have instinctively pulled up in final seconds to avoid perceived CFIT unaware of the converging aircraft?
Assuming helo crew has wrong a/c visual and thinks they are well clear. Their biggest concern is presumably avoiding water while proceeding low level. Is it conceivable that the landing lights of aircraft converging from above and off peripheral creates a sudden visual effect / distortion as it casts shadows off helo/rotor and glare off water. (Not to mention possible NVG) Since aircraft is turning and descending from above.and.at an angle it seems it might have created a sort of spotlighting effect on the helo.
If so, aircrew may have instinctively pulled up in final seconds to avoid perceived CFIT unaware of the converging aircraft?
This post was edited on 2/1/25 at 12:18 pm
Posted on 2/1/25 at 12:17 pm to Tuscaloosa
quote:
which isn’t plausible.
It is certainly “plausible”
A common call from ATC is to “maintain visual separation” from aircraft that are departing the runway.
If it was the departing aircraft that caught their attention based on their position, both pilot’s heads would’ve been turned to the right looking at the aircraft departing RWY 1. The call for visual separation is still issued despite not ever being in a real position to collide. If their eyes were outside and right, they could’ve easily not seen the aircraft coming at them that they ran into.
Is this what really happened? Maybe not and we’ll likely never know. But it’s certainly plausible that the departing aircraft could’ve been where their eyes were.
Posted on 2/1/25 at 12:25 pm to 0x15E
The earlier traffic point out was for a descending a/c at 1200ft near the bridge south of airfield though. I guess they could have associated follow on ATC call with completely different traffic. That would def be a critical mistake as that traffic wasnt relevant to their flight path and wouldnt warrant ATC point out. I was unsatisfied w the lack of specificity for the last minute ATC call but others that are actual pilot seem comfortable with it.
This post was edited on 2/1/25 at 12:32 pm
Posted on 2/1/25 at 12:34 pm to TorchtheFlyingTiger
(no message)
This post was edited on 4/13/25 at 1:39 am
Posted on 2/1/25 at 12:42 pm to 0x15E
The unidentified soldier was an experienced pilot with more than 500 hours of flying experience, the Telegraph reported, citing Jonathan Koziol, chief of staff of the army’s aviation directorate.
At a press conference Thursday, Secretary of Defense Pete Hegseth described the crew of the UH-60 Black Hawk crew “fairly experienced.”
pilot had 500 hours and seems like everybody on board with familar with the DC fly paths and the obvious 200 feet height rule
LINK
The unidentified soldier was an experienced pilot with more than 500 hours of flying experience, the Telegraph reported, citing Jonathan Koziol, chief of staff of the army’s aviation directorate.
The Army on Friday formally identified Staff Sgt. Ryan Austin O’Hara, 28, and Chief Warrant Officer 2 Andrew Loyd Eaves, 39, as the two other service members who were on the Black Hawk helicopter when it went down in the fiery crash into the Potomac River.
Staff Sgt. Ryan Austin O’Hara was the crew chief of the Black Hawk helicopter involved in the tragic accident Wednesday. 3
Eaves, the instructor pilot on the flight, is reported to have logged more than 1,000 hours of flight time, Koziol said, according to the Telegraph.
Koziol further dismissed claims that DEI policies were to blame for the crash — something that was suggested by President Trump Thursday.
“Both pilots had flown this specific route before at night — this wasn’t something new to either one of them,” Koziol said.
At a press conference Thursday, Secretary of Defense Pete Hegseth described the crew of the UH-60 Black Hawk crew “fairly experienced.”
pilot had 500 hours and seems like everybody on board with familar with the DC fly paths and the obvious 200 feet height rule
LINK
The unidentified soldier was an experienced pilot with more than 500 hours of flying experience, the Telegraph reported, citing Jonathan Koziol, chief of staff of the army’s aviation directorate.
The Army on Friday formally identified Staff Sgt. Ryan Austin O’Hara, 28, and Chief Warrant Officer 2 Andrew Loyd Eaves, 39, as the two other service members who were on the Black Hawk helicopter when it went down in the fiery crash into the Potomac River.
Staff Sgt. Ryan Austin O’Hara was the crew chief of the Black Hawk helicopter involved in the tragic accident Wednesday. 3
Eaves, the instructor pilot on the flight, is reported to have logged more than 1,000 hours of flight time, Koziol said, according to the Telegraph.
Koziol further dismissed claims that DEI policies were to blame for the crash — something that was suggested by President Trump Thursday.
“Both pilots had flown this specific route before at night — this wasn’t something new to either one of them,” Koziol said.
Posted on 2/1/25 at 12:42 pm to Tuscaloosa
Anyone here w rotary wing experience that might be able to shed some light on typical/standard crew contracts? I've heard co-pilot usually manages comms w ATC (checks out w audio we've heard). But who usually has primary task to maintain airspace adhearance, nav routing, altitude monitoring etc? Which is primary for declaring/maintaining visual w traffic and avoidance?
(Think I have a good idea of typical crew responsibilities and task delegation but can anyone w experience confirm?)
(Think I have a good idea of typical crew responsibilities and task delegation but can anyone w experience confirm?)
Posted on 2/1/25 at 1:19 pm to TorchtheFlyingTiger
quote:
The earlier traffic point out was for a descending a/c at 1200ft near the bridge south of airfield though.
I can’t remember time lapse between this which I think was at 2 miles south of the Wilson bridge, and when the helicopter acknowledged visual contact with plane and then asked for visible separation. I also don’t know visibility that night for them.
But around the Wilson bridge the plane adjusted to land on 33 with an initial turn to its right taking it over south section of Bolling and closer to 295 before turning to the left to line up with 33.
Helicopter was told it was using 33 to land, but did they not realize it was going to be making that type of turn? And/or did they not know which runway was 33? Then due to turn and visibility factors they lost it (or one of them did and poor communication caused them to not be on same page) or never saw it before picking up on the 2nd plane coming in to land on different runway which is what they were actually acknowledging.
I don’t know if the timing of plane’s turn to the right before going left or if the helicopter’s ability to see the 2nd plane match up with timing of radio acknowledgement.
Posted on 2/1/25 at 1:27 pm to TorchtheFlyingTiger
I realize most of the pilots on here probably haven’t been close to a head on collision with a jet but from any of y’all’s experience would that be something that could potentially blind/disorient you? Kinda like turn your brights off bro I can’t see shite. Would not seeing their lights even be a possibility, assuming they were paying attention? Would there be an altitude/distance difference or lack thereof where a problem like that could occur? Just curious.
Eta: I guess that scenario would have yielded some radio traffic about it.
Eta: I guess that scenario would have yielded some radio traffic about it.
This post was edited on 2/1/25 at 1:29 pm
Posted on 2/1/25 at 2:16 pm to Cornbeef
Watching that video from other angle I don’t understand how helicopter pilot did not see plane, it was right in front of him
Its like he flew right into it
Didn’t even look like he tried to avoid it
Its like he flew right into it
Didn’t even look like he tried to avoid it
Posted on 2/1/25 at 2:22 pm to RelicBatches86
quote:
“Both pilots had flown this specific route before at night — this wasn’t something new to either one of them,” Koziol said.
This doesn’t mean one or both didn’t have issues with past flights that just didn’t result in similar tragedy or have an incoming flight have it’s runway changed from coming nearly straight up the western side of the river to making that wide turn over land to then cross their path almost perpendicularly from the east bank. It doesn’t seem to address if previous flights were under similar weather conditions, or if previous flights were exact same type of training scenario, using visual separation, and with same type of helicopter. Koziol might be assuming the public knows he also means those night flights were the same training scenario and under the same conditions, but if so he could have stated this with less ambiguity.
Also is Jonathan Koziol new to the job, or has he been around long enough to be part of decision making on these pilots being ready or not and their training which is likely to be reviewed? He may not be as objective as he should be.
He also either misstates what the issue with DEI really is, or was actually commenting on women being pilots and not on DEI initiatives and quotas with the press then turning it into being about DEI on their own. It’s not about hiring or promoting qualified women based on their merit when equally compared to all the other candidates (or whatever this pilot was), but instead of placing and promoting the best candidates based on merit DEI can focus on hitting quotas of political identity groups at the sake of hiring the best.
I also saw the below, but I don’t know if helicopter declared an emergency situation, but article seems ready to drop blame on the publicly named male soldier involved. If the unnamed pilot was solely hired or promoted based on merit than she be named like Eaves. The army is the one making it seem like there is something fishy about this unnamed pilot.
quote:
The Black Hawk helicopter was conducting a training flight for a female pilot who has not yet been identified. She was being overseen by Chief WO2 Eaves, who had more than 1,000 hours of flying experience and would have been expected to take over the controls in the event of an emergency.
This post was edited on 2/1/25 at 2:25 pm
Posted on 2/1/25 at 2:41 pm to Cornbeef
quote:
it was right in front of him
Its like he flew right into it
That's the thing, it wasn't head on. The plane was turning into the helo's path and rapidly descending on approach.
Haven't all of you had a moment on interstate where you were surprised by a rapidly passing vehicle? The closure rate was probably 40mph or less. Closure rate in this situation was well above 150mph. Plus the plane was descending (possibly from outside forward field of view) Helo crew would have needed to visually aquire the jet by scanning above and to left but missed it in their scan pattern and locked eyes on wrong traffic.
This post was edited on 2/1/25 at 2:42 pm
Posted on 2/1/25 at 2:44 pm to VABuckeye
quote:
VABuckeye
I notice you didn't address my point, but rather just insulted me.
This post was edited on 2/1/25 at 2:45 pm
Popular
Back to top


0





