Narrative:

Upon landing on runway 27 at memphis, tn, executed a rejected landing (due to a long landing and exiting traffic) on climb out, (a beam runway 17) received an urgent call from tower to level off. Captain took control of aircraft and descended slightly to avoid a midair collision with another aircraft on final to runway 17, estimate 300 ft. After the avoidance maneuver, executed a normal go around and first officer landed on runway 27 uneventful. Simultaneous apches to perpendicular runways was taking place. Supplemental information from acn 544971: captain took control of aircraft and descended slightly upon sighting conflicting aircraft to avoid an impending collision with an air carrier landing on runway 17 (estimated altitude 300). I recommend that visual apches not be conducted when using perpendicular runways for landing. Consideration (more separation) needs to be given in the event of a missed approach. Pilot flying, (first officer), distracted by late clearing aircraft in front got high in close to runway and we touched down just outside landing zone. Had tower not called us, or if we had executed our go around a few seconds earlier, we most likely would have been involved in a mid-air collision. This is a case where everyone acted properly and we still had a potentially catastrophic result. Callback conversation with reporter revealed the following information: reporter advised that the local controller alerted them to the conflict as they were climbing through approximately 240 ft. The capts actions descended them back down to approximately 200 ft as the DC9 crossed approximately 100 ft overhead. There was no indication that the DC9 saw their aircraft on the go around. The captain and a company official discussed the event with a mem tower supervisor. The reporter states that the DC9 was on the other local control frequency. The reason a go around was initiated was due to previous landing traffic slowly exiting runway 27.

Google
 

Original NASA ASRS Text

Title: MD11 ON GAR FROM MEM RWY 27 MAKES AVOIDANCE MANEUVER TO AVOID COLLISION WITH ANOTHER ACFT LNDG RWY 17.

Narrative: UPON LNDG ON RWY 27 AT MEMPHIS, TN, EXECUTED A REJECTED LNDG (DUE TO A LONG LNDG AND EXITING TFC) ON CLBOUT, (A BEAM RWY 17) RECEIVED AN URGENT CALL FROM TWR TO LEVEL OFF. CAPT TOOK CTL OF ACFT AND DSNDED SLIGHTLY TO AVOID A MIDAIR COLLISION WITH ANOTHER ACFT ON FINAL TO RWY 17, ESTIMATE 300 FT. AFTER THE AVOIDANCE MANEUVER, EXECUTED A NORMAL GAR AND FO LANDED ON RWY 27 UNEVENTFUL. SIMULTANEOUS APCHES TO PERPENDICULAR RWYS WAS TAKING PLACE. SUPPLEMENTAL INFO FROM ACN 544971: CAPT TOOK CTL OF ACFT AND DSNDED SLIGHTLY UPON SIGHTING CONFLICTING ACFT TO AVOID AN IMPENDING COLLISION WITH AN ACR LNDG ON RWY 17 (ESTIMATED ALTITUDE 300). I RECOMMEND THAT VISUAL APCHES NOT BE CONDUCTED WHEN USING PERPENDICULAR RWYS FOR LNDG. CONSIDERATION (MORE SEPARATION) NEEDS TO BE GIVEN IN THE EVENT OF A MISSED APCH. PLT FLYING, (FO), DISTRACTED BY LATE CLRING ACFT IN FRONT GOT HIGH IN CLOSE TO RWY AND WE TOUCHED DOWN JUST OUTSIDE LANDING ZONE. HAD TWR NOT CALLED US, OR IF WE HAD EXECUTED OUR GAR A FEW SECONDS EARLIER, WE MOST LIKELY WOULD HAVE BEEN INVOLVED IN A MID-AIR COLLISION. THIS IS A CASE WHERE EVERYONE ACTED PROPERLY AND WE STILL HAD A POTENTIALLY CATASTROPHIC RESULT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR ADVISED THAT THE LCL CTLR ALERTED THEM TO THE CONFLICT AS THEY WERE CLBING THROUGH APPROX 240 FT. THE CAPTS ACTIONS DSNDED THEM BACK DOWN TO APPROX 200 FT AS THE DC9 CROSSED APPROX 100 FT OVERHEAD. THERE WAS NO INDICATION THAT THE DC9 SAW THEIR ACFT ON THE GAR. THE CAPT AND A COMPANY OFFICIAL DISCUSSED THE EVENT WITH A MEM TWR SUPVR. THE RPTR STATES THAT THE DC9 WAS ON THE OTHER LCL CTL FREQ. THE REASON A GAR WAS INITIATED WAS DUE TO PREVIOUS LNDG TFC SLOWLY EXITING RWY 27.

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.