Originally Posted by CBrF3

This is one aspect of this accident that almost no one has acknowledged (that I've seen, at least) or identified as contributing to the mishap. And it drives me crazy. As a DCA based PSA pilot up until a few months before the accident, I can vouch for the fact that among the myriad of information in our company pages, I had never seen that helo route depiction, nor had anyone I ever flew with spoke about its existence. The picture that would've spoken 1,000 words in building an accurate mental model of potential risks in an already busy airport was never provided to us. At best all we ever knew was what tower sometimes said, "helicopter crossing the river east to west at XXXX altitude, has you in sight" as you're busy watching your profile and airspeed while flying the River Visual or circling to land 33. Basically - impossible to acquire visually while remaining stable.

Years ago I became very interested in the organizational and management issues that contribute to accidents, as I was in the front row to a fatal crash involving members of my unit. There were cultural and management standards that laid the groundwork for that crash - never acknowledged except in private discussions among people who had more intimate knowledge of the event and the culture. So I'm especially critical of the components that aren't as glamorous or easily identifiable to point to and say, "A ha!", but are significant contributors nonetheless.

And you're right. There was already widespread reluctance to accept a circle to 33 under marginal conditions, nighttime being one of them. Unfortunately the winds favored 33 that night and likely tipped the scales to accept the circle.

If nothing else this accident should remind us to evaluate what our company norms are and how much risk we accept as standard. For example, how often do we accept taxi clearance in a rushed environment and the FO goes heads down doing checklists, changing runways, etc?