I know a lot of pilots who would take a 20-knot gusty headwind over a 20-knot gusty crosswind.
Yes, and those guys should be called real pilots.
And just FYI, that new closeup video disturbs me. It disturbs me enough
to write this lengthy post.
I'll just come out and say it - I don't think that those helicopter pilots were
"real pilots."That's because, in my view, a "real pilot" in that situation should
prioritize safety over the training mission
all of the time. Maybe it's just me (and
hopefully it isn't) but I've been under the hood several times simulating
an instrument approach when traffic is called out - either by ATC or on
the TCAS. The first thing I do (if it continues to get closer) is take the
hood off and scrap the practice approach - my priority is to look for that
traffic along with the check pilot in the right seat.
In my view, that's what those helicopter pilots should have done. They
were given a specific landmark and altitude to identify the RJ - which was
the Wilson Bridge and 1,200'. At least one of the three pilots on PAT 25 should
have known exactly where that bridge was. At least one of those pilots should
have known that runway 33 was a big conflict for the route they were flying on.
At least one of those pilots should have known to hug the eastern Potomac and fly
at least 200 feet or below - preferably 150' over shore. That's what I would have
done. Am I saying this in hindsight? No, because every time I've flown the Hudson
River Corridor over the years, that's the way that I operated - never bust altitude
and give the max altitude a margin of safety by 100' or so - that's because
the Laguardia traffic above used to get pretty close back in the day - the airliners
above looked big! I think the max altitude was 1,000' feet back in the day,
so I'd often fly at 900'. Since the helicopter was already close to the ground in
the accident case, I thought giving a 50' margin might suffice. But why not go for
100' margin of safety? You're a helicopter pilot and that's what "you do" (or should
do) as long as there's no high-tension wires and I don't see any on the chart.
I haven't flown the Hudson corridor in years because I'm down in FL now and every time
I go up the KHPN, I'm IFR. I'm not sure if it's the same now or not.
But to have the three pilots on PAT 25 act so nonchalantly about the traffic is
disturbing. I've thought about it for a couple of days now and I decided that I'd just
come out and say it on this board. They could have done, much, much better.
They could have identified the Wilson Bridge and started looking for traffic
from
that starting point. We have three bridges where I fly (Palm City,
Roosevelt and Veteran's Memorial) and traffic is often called out over those bridges.
There's lots of ground light at night and sometimes it's very hard to find the runway
lights on any type of circling approach - that includes downwind, base to
final. But those bridges help a lot for orientation at night -
to spot traffic
as well as give an understand of when to turn base, etc.
I almost can't believe how three pilots could be so focused on a mission
(that can be practiced later) that at least one couldn't have taken off
those goggles and made spotting the CRJ (that they should have known
the RJ was going into 33 because that's what DCA tower told them) and
given that RJ the utmost of priority relative to finding it near the Wison
Bridge - and inside that bridge after it was called out.
Just looking at that close up video where the RJ was gently turning
final (it wasn't even close to 90 degrees) where it was lit up like a damn
Christmas tree indicated to me that those PAT 25 pilots were more than
half asleep - and that's tragic.
PS:
This is a whole other story, but I don't think that the DC tower
controller had back up. If he did, he might have had more time
(or the check controller could have done it) to give PAT 25 a heading
to avoid the RJ. But the controller 'believed' what PAT 25 had the
traffic in sight. Too bad that Airbus was the wrong traffic going into
runway 01 and it wasn't even close to the Wilson bridge at the time of
impact.