Narrative:

Flight was being vectored for a visual approach to runway 33 at dca. At approximately 7 mi from the airport, we called the field in sight. Dca approach control cleared us for the visual to runway 33 and instructed us to provide maximum forward airspeed to the field and contact tower. When we checked in, dca tower informed us that we were number 3 for the airport, to reduce to final approach speed and perform s-turns for spacing. We reduced to approach speed, performed a couple of s-turns, but it was becoming increasingly obvious that we were lower and closer to the airport than the dash-8 on final for runway 1. We informed tower that this was not going to work. Dca tower then informed us that it would work, because the dash-8 was cleared to land runway 1 and hold short of runway 33. Still not cleared to land, we continued for runway 33. Now below 200 ft, I reconsidered my go around options when I noticed the dash-8 off our left side was going around for runway 1. Tower immediately cleared us to land runway 33. As we touched down on runway 33, the dash-8 flew directly overhead of our aircraft. We continued to the gate without further incident. Callback conversation with reporter revealed the following information: there was no landing clearance given until short final. The dash-8 passed overhead at an unknown altitude in its go around as the reporter's aircraft went through the intersection of runway 1 and runway 33. The dash-8 appeared to start its go around at about 200 ft AGL. Lahso was not in progress and no mention of it was made until spacing was questioned. The reporter does not recall hearing xmissions to or from the dash-8. This led him to surmise that the runways were under the control of separate controllers.

Google
 

Original NASA ASRS Text

Title: TWO ACR CREWS ARRIVING AT RONALD REAGAN WASHINGTON NAT'L ARPT DETERMINE SPACING FOR LNDG ON INTERSECTING RWYS IS INADEQUATE. ONE GOES AROUND AND THE OTHER BEGINS A GAR BUT ABANDONS IT FOR A LNDG ALLOWING THE OTHER ACFT TO PASS OVERHEAD.

Narrative: FLT WAS BEING VECTORED FOR A VISUAL APCH TO RWY 33 AT DCA. AT APPROX 7 MI FROM THE ARPT, WE CALLED THE FIELD IN SIGHT. DCA APCH CTL CLRED US FOR THE VISUAL TO RWY 33 AND INSTRUCTED US TO PROVIDE MAX FORWARD AIRSPEED TO THE FIELD AND CONTACT TWR. WHEN WE CHECKED IN, DCA TWR INFORMED US THAT WE WERE NUMBER 3 FOR THE ARPT, TO REDUCE TO FINAL APCH SPEED AND PERFORM S-TURNS FOR SPACING. WE REDUCED TO APCH SPEED, PERFORMED A COUPLE OF S-TURNS, BUT IT WAS BECOMING INCREASINGLY OBVIOUS THAT WE WERE LOWER AND CLOSER TO THE ARPT THAN THE DASH-8 ON FINAL FOR RWY 1. WE INFORMED TWR THAT THIS WAS NOT GOING TO WORK. DCA TWR THEN INFORMED US THAT IT WOULD WORK, BECAUSE THE DASH-8 WAS CLRED TO LAND RWY 1 AND HOLD SHORT OF RWY 33. STILL NOT CLRED TO LAND, WE CONTINUED FOR RWY 33. NOW BELOW 200 FT, I RECONSIDERED MY GAR OPTIONS WHEN I NOTICED THE DASH-8 OFF OUR LEFT SIDE WAS GOING AROUND FOR RWY 1. TWR IMMEDIATELY CLRED US TO LAND RWY 33. AS WE TOUCHED DOWN ON RWY 33, THE DASH-8 FLEW DIRECTLY OVERHEAD OF OUR ACFT. WE CONTINUED TO THE GATE WITHOUT FURTHER INCIDENT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THERE WAS NO LANDING CLRNC GIVEN UNTIL SHORT FINAL. THE DASH-8 PASSED OVERHEAD AT AN UNKNOWN ALTITUDE IN ITS GO AROUND AS THE RPTR'S ACFT WENT THROUGH THE INTXN OF RWY 1 AND RWY 33. THE DASH-8 APPEARED TO START ITS GO AROUND AT ABOUT 200 FT AGL. LAHSO WAS NOT IN PROGRESS AND NO MENTION OF IT WAS MADE UNTIL SPACING WAS QUESTIONED. THE RPTR DOES NOT RECALL HEARING XMISSIONS TO OR FROM THE DASH-8. THIS LED HIM TO SURMISE THAT THE RWYS WERE UNDER THE CTL OF SEPARATE CTLRS.

Data retrieved from NASA's ASRS site as of July 2007 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.