DCA Circle 33 risk assessment and avoidance

averettpilot

averettpilot

Well-Known Member
I wanted to start a discussion around risk assessment and avoidance on circling to 33 at DCA if you’re capable. I have very strong opinions about it post 5342, and cards on the table I work at PSA so I have a bit of skin in the game on this subject.

There’s been discussion about it within the pilot group and I wanted to see what opinions there are outside.

I don’t want to sway the discussion either way with how I feel about it, but with conditions as they currently stand I’m an almost never circle outside very specific operational considerations and needs (example a crosswind on 1 out of the west that exceeds the aircraft’s capability). Before the accident I used to love circling to 33. It’s not really a challenge in my opinion, but it did break the monotony of flying 20 mile straight in finals all the time. Since then I can’t justify the increased risk with helicopter traffic in that vicinity even since the route closure. Joint Base Anacostia-Bolling is still active and just .7 miles away from 33 final. Add that to the fact ATC still has trouble communicating with helos in the area, specifically losing separation with Marine One two months ago because they couldn’t hear each other, I just can’t see any way to mitigate the risk to an acceptable level other than not going over there. Especially when there isn’t a justifiable benefit to operations. Shoot just last night departing DCA, ATC couldn’t communicate with an airborne PAT and it had to be relayed.

Anyway, those are my top line thoughts on the subject. I’m interested to hear what others think.
 
The circle to 33 maneuver from an approach to 1 isn’t risky of a maneuver in and of itself, as it’s kind of a mild circle maneuver really and is pretty easy to accomplish. But like you mention, it’s all the factors outside the actual maneuver itself, that are of concern. If there are still issues with aircraft transiting the airspace there with regards to control, comms, etc, especially ones in the area where the circling maneuver is being undertaken, then yeah, that would increase risk; risk of factors you aren’t able to control.

Big question is, why is the circle being performed, which you also mention. Necessity, or convenience? Seems it’s been a convenience thing there at DCA, and again, in and of itself wasn’t anything risky….other than the outside factors. Convenient for both the airlines as well as for ATC, so it was being undertaken….land traffic on 33, launch traffic off of 1. Regardless, no flight should have to be compelled to land 33 if they don’t want to, when 1 is also in use and the approach is to 1.

Should be players choice, since it’s not mandatory. If one crew is comfortable doing it, cool. If another crew isn’t comfortable doing it due to perceived risk, cool. If 33 is the duty runway and everyone is using it at the moment, then that’s a different story,
 
I flew in and out of DCA for 8 years (also with PSA). For much of that time helicopter traffic was considerably busier (due to the post 9-11 world) than it is today, although traffic operations in and out the airport are (per the FAA) 6% busier now.

My concerns around circling to 33 were mostly around low level, low speed, high angle bank turns to align when they pushed you to stay over the river on final, and traffic conflicts with Runway 1. Helicopters were a concern, but in my experience then, much more so when landing 19 or, especially, when circling to 15 with the Pentagon helo pads right there.

At that time, it was necessary to get 33 arrivals in, mostly to build breaks for Runway 1 departures. Back then (maybe still?) if you had a long sit between flights, you could call up ground and coordinate a tower visit for your crew. I took a lot of FOs (and some FAs too) up there and get to know some of the tower cab guys over the years. Seeing the operation from that perspective gave me a way better understanding of how the pieces all fit together.

It's a risk vs. reward thing. Obviously, no crash makes any operating risk worth it (in a civilian context) but I'm not sure that the error chain that ended at 5342 couldn't be solved in some way that didn't prohibit Runway 33 ops.
 
My fear with the circle to 33 wasn’t so much the risk from helicopter traffic on short final but rather the risk from a ground collision due to the intersecting runways, crossing points and the incredibly tight spacing at DCA.
 
The job as a whole has always been dangerous. Whether it’s risk of death on 33, smacking a helicopter down the river, hitting a glider with no transponder, parachute jumpers blown off course, buzzards, etc. Now I have to watch out for bread trucks? Ok. Fly like your family is on board. Do the best you can. There’s a thrill in the risk of this job. You could always sit at a desk or attend a trade show.

I enjoyed the circle to 33, river visual to 19 and the maneuver to 15. DCA made you a better pilot.
 
Richman said:
When making any risk assessment, run through your head how the NTSB report will read.
Click to expand...
This.

Also, I am so very sick of hearing "back in my day X was worse." Even if well-intentioned, it is (unintentionally or not) demeaning, and unresponsive to the emergent challenges and changing risk environment that crews currently face.
 
N826AW said:
My fear with the circle to 33 wasn’t so much the risk from helicopter traffic on short final but rather the risk from a ground collision due to the intersecting runways, crossing points and the incredibly tight spacing at DCA.
Click to expand...
That could be present landing on any runway at DCA though.
 
You must log in or register to reply here.
Back
Top