Intersecting runway landing takeoff situation.

Attributes
ACN	286259
Time
Date	199410
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : dca
State Reference	DC
Altitude	agl bound lower : 100 agl bound upper : 100
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : dca
Operator	common carrier : air carrier
Make Model Name	MD-88
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent : approach landing : go around landing other
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Phase	climbout : takeoff
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : local oversight : supervisor
Qualification	controller : non radar
Experience	controller non radar : 2 controller radar : 8
ASRS Report	286259
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : developmental
Events
Anomaly	conflict : airborne less severe other anomaly other
Independent Detector	other controllera
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

An MD88 on final to runway 33. A B737 cleared for takeoff on runway 36. The B737 would not have been clear of the runway 33 intersection before the MD88 crossed the threshold of runway 33. The MD88 was issued a go around. The MD88 passed behind and above the B737. Legal in accordance with 7110.65, but closer than I felt comfortable with. Training was being accomplished and the situation was probably allowed to develop more than if I had been working alone. Supplemental information from acn 286403: we were cleared for takeoff on runway 36 -- there was conflicting landing traffic cleared to land on runway 33. The landing traffic was given a low altitude go around with a left turn-out by tower -- we were given an immediate right turn (596 ft washington monument to right). It would be a great deal less exciting and safer if the dca tower would resolve their traffic conflicts by giving the landing aircraft go around instructions earlier.

Original NASA ASRS Text

Title: INTERSECTING RWY LNDG TKOF SIT.

Narrative: AN MD88 ON FINAL TO RWY 33. A B737 CLRED FOR TKOF ON RWY 36. THE B737 WOULD NOT HAVE BEEN CLR OF THE RWY 33 INTXN BEFORE THE MD88 CROSSED THE THRESHOLD OF RWY 33. THE MD88 WAS ISSUED A GAR. THE MD88 PASSED BEHIND AND ABOVE THE B737. LEGAL IN ACCORDANCE WITH 7110.65, BUT CLOSER THAN I FELT COMFORTABLE WITH. TRAINING WAS BEING ACCOMPLISHED AND THE SIT WAS PROBABLY ALLOWED TO DEVELOP MORE THAN IF I HAD BEEN WORKING ALONE. SUPPLEMENTAL INFO FROM ACN 286403: WE WERE CLRED FOR TKOF ON RWY 36 -- THERE WAS CONFLICTING LNDG TFC CLRED TO LAND ON RWY 33. THE LNDG TFC WAS GIVEN A LOW ALT GAR WITH A L TURN-OUT BY TWR -- WE WERE GIVEN AN IMMEDIATE R TURN (596 FT WASHINGTON MONUMENT TO R). IT WOULD BE A GREAT DEAL LESS EXCITING AND SAFER IF THE DCA TWR WOULD RESOLVE THEIR TFC CONFLICTS BY GIVING THE LNDG ACFT GAR INSTRUCTIONS EARLIER.

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.