Date: 201204
Local time of day: 0601-1200
Location: DCA.Airport, DC
Flight conditions: VMC
Weather elements / visibility: 6
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B DCA
ATC / advisory: Tower DCA
Reporter organization: Corporate
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion; Situational Awareness; Workload; Distraction
Second reporter function: Pilot Not Flying; Captain
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Environment - Non Weather Related; Airport; Airspace Structure; Procedure
Primary problem: Procedure

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.


Second narrative: The Departure Controllers were sorry for the mishandling and gave a heading to the south and for us to plan on landing Runway 01 at DCA. The visual approach was executed to Runway 01 DCA and the runway was exited in a normal manner. Taxi to the FBO was uneventful and the aircraft was shut down and secured for the 10 hour or so stay at DCA. At this point; the mission was uneventful and no further actions needed. No phone numbers were given to the crew to contact anyone at Potomac Approach not the Tower. The next month; an FAA Safety Inspector contacted me to inform me of a possible pilot deviation on the missed approach that occurred last month.


Synopsis: 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.