Narrative:

We were on the mount vernon visual approach to runway 01 at dca. The tower then cleared us to circle the runway 33 and we were cleared to land. When our airplane was roughly 1/2 to 3/4 mile final to runway 33; the tower then cleared an airliner to takeoff from runway 01 and to expedite as there was an aircraft on a 2 mile final to runway 33. I was the pilot flying and I immediately said to the pilot not flying; 'they have mis-judged our distance; this is not going to work.' sure enough; as we were established on final at about 500 ft AGL; we were told to go-around. We executed the go-around; climbed to a safe altitude and switched to departure. We were instructed to turn to a heading of 270 at 2000 ft and were vectored back for another mount vernon visual to runway 01. All other portions of flight were uneventful. This was the second go-around our small flight department has been issued by dca tower in 1 month's time. In fact; other than dca; as a flight department we have not been issued or have had to execute any go-around at any other airport this year. More spacing needs to be provided for arrivals at dca. It appears to me that at peak times there is a major push by controllers to squeeze aircraft in and out of this airport. As pilots we certainly appreciate the controller's hard work and efforts to accommodate all the aircraft in this confined space. Unfortunately sometimes it is too congested. With all the restricted airspace surrounding the airport; it makes it very tight when airplanes are routinely going around. As we were discussing the flight as a crew on the ramp; we witnessed anther airplane executing a go-around which solidified in my mind the need for more spacing.

Google
 

Original NASA ASRS Text

Title: A corporate jet crew reported being switched from a DCA Runway 1 Mount Vernon Visual to a Runway 33 visual. Then; ATC issued them a go around because an air carrier departing Runway 1 interfered with them.

Narrative: We were on the Mount Vernon visual approach to Runway 01 at DCA. The Tower then cleared us to circle the Runway 33 and we were cleared to land. When our airplane was roughly 1/2 to 3/4 mile final to Runway 33; the Tower then cleared an airliner to takeoff from Runway 01 and to expedite as there was an aircraft on a 2 mile final to Runway 33. I was the pilot flying and I immediately said to the pilot not flying; 'they have mis-judged our distance; this is not going to work.' Sure enough; as we were established on final at about 500 FT AGL; we were told to go-around. We executed the go-around; climbed to a safe altitude and switched to Departure. We were instructed to turn to a heading of 270 at 2000 FT and were vectored back for another Mount Vernon visual to Runway 01. All other portions of flight were uneventful. This was the second go-around our small flight department has been issued by DCA Tower in 1 month's time. In fact; other than DCA; as a flight department we have not been issued or have had to execute any go-around at any other airport this year. More spacing needs to be provided for arrivals at DCA. It appears to me that at peak times there is a major push by controllers to squeeze aircraft in and out of this airport. As pilots we certainly appreciate the Controller's hard work and efforts to accommodate all the aircraft in this confined space. Unfortunately sometimes it is too congested. With all the restricted airspace surrounding the airport; it makes it very tight when airplanes are routinely going around. As we were discussing the flight as a crew on the ramp; we witnessed anther airplane executing a go-around which solidified in my mind the need for more spacing.

Data retrieved from NASA's ASRS site as of July 2013 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.