Narrative:

Near midair collision. We taxied out for takeoff to runway 26 at abq. There were thunderstorms in the area with virga extending south to west of the airport. The surface wind was 240 degrees at 15 KTS. Tower cleared us on hold. We requested a heading after takeoff of 300 degrees to avoid the WX, and were cleared for takeoff. Tower had a light twin aircraft on final for runway 21, and requested they fly a flight path behind us to land on runway 21. They said they would comply. We did not have the light twin in sight. Takeoff, rotation and gear retraction were normal. As we were climbing through approximately 250-300 ft AGL, I saw the twin at 1 O'clock position, slightly high, descending right to left. I initiated a pull to the stick shaker to pass above. Prior to takeoff, our primary attention was the WX and avoiding it on departure, not on other aircraft in the traffic pattern. We assumed tower and the light twin would deconflict our flight paths. Building situational awareness on other traffic is a big player at airports with crossing runway configns. Upon arrival in phx, I called and talked to ZAB supervisor. Supplemental information from acn 516796: on jun/fri/01 at approximately XA51, operating as flight XXX from abq to phx, we were cleared for takeoff on runway 26 at abq where we encountered an near midair collision with another aircraft landing on runway 21 at approximately 300 ft AGL. According to abq tower, a twin cessna was supposed to go behind us and land on runway 21 but instead went straight for runway 21 and created a conflict with us. I did not see the other aircraft, but the captain who was flying the aircraft did and performed an evasive maneuver by pulling the nose up to between 20-25 degrees and held it there for 10-15 degrees, at V2, until we were clear of the other aircraft. There were thunderstorms and rain showers all around the abq airport, and we had been delayed about 1 hour waiting for fuel because of lightning over the airport. While taxiing out, we had been issued a flow time window into phx and I believe the tower controller was preoccupied with us making our flow time and with all the WX in the area that they were not monitoring the aircraft landing on runway 21. We spent a few moments on runway 26 looking at the WX on the departure path on the radar to decide on a heading after takeoff. The tower approved our heading request and cleared us for takeoff, and as far as I can remember, did not mention the aircraft on runway 21. I do not believe that we were at fault, but a combination of the other aircraft not following instructions and the tower controller not monitoring their progress that were at fault.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B737-300 AND TWIN CESSNA HAD NMAC WHEN DEPARTING ABQ.

Narrative: NMAC. WE TAXIED OUT FOR TKOF TO RWY 26 AT ABQ. THERE WERE TSTMS IN THE AREA WITH VIRGA EXTENDING S TO W OF THE ARPT. THE SURFACE WIND WAS 240 DEGS AT 15 KTS. TWR CLRED US ON HOLD. WE REQUESTED A HDG AFTER TKOF OF 300 DEGS TO AVOID THE WX, AND WERE CLRED FOR TKOF. TWR HAD A LIGHT TWIN ACFT ON FINAL FOR RWY 21, AND REQUESTED THEY FLY A FLT PATH BEHIND US TO LAND ON RWY 21. THEY SAID THEY WOULD COMPLY. WE DID NOT HAVE THE LIGHT TWIN IN SIGHT. TKOF, ROTATION AND GEAR RETRACTION WERE NORMAL. AS WE WERE CLBING THROUGH APPROX 250-300 FT AGL, I SAW THE TWIN AT 1 O'CLOCK POS, SLIGHTLY HIGH, DSNDING R TO L. I INITIATED A PULL TO THE STICK SHAKER TO PASS ABOVE. PRIOR TO TKOF, OUR PRIMARY ATTN WAS THE WX AND AVOIDING IT ON DEP, NOT ON OTHER ACFT IN THE TFC PATTERN. WE ASSUMED TWR AND THE LIGHT TWIN WOULD DECONFLICT OUR FLT PATHS. BUILDING SITUATIONAL AWARENESS ON OTHER TFC IS A BIG PLAYER AT ARPTS WITH XING RWY CONFIGNS. UPON ARR IN PHX, I CALLED AND TALKED TO ZAB SUPVR. SUPPLEMENTAL INFO FROM ACN 516796: ON JUN/FRI/01 AT APPROX XA51, OPERATING AS FLT XXX FROM ABQ TO PHX, WE WERE CLRED FOR TKOF ON RWY 26 AT ABQ WHERE WE ENCOUNTERED AN NMAC WITH ANOTHER ACFT LNDG ON RWY 21 AT APPROX 300 FT AGL. ACCORDING TO ABQ TWR, A TWIN CESSNA WAS SUPPOSED TO GO BEHIND US AND LAND ON RWY 21 BUT INSTEAD WENT STRAIGHT FOR RWY 21 AND CREATED A CONFLICT WITH US. I DID NOT SEE THE OTHER ACFT, BUT THE CAPT WHO WAS FLYING THE ACFT DID AND PERFORMED AN EVASIVE MANEUVER BY PULLING THE NOSE UP TO BTWN 20-25 DEGS AND HELD IT THERE FOR 10-15 DEGS, AT V2, UNTIL WE WERE CLR OF THE OTHER ACFT. THERE WERE TSTMS AND RAIN SHOWERS ALL AROUND THE ABQ ARPT, AND WE HAD BEEN DELAYED ABOUT 1 HR WAITING FOR FUEL BECAUSE OF LIGHTNING OVER THE ARPT. WHILE TAXIING OUT, WE HAD BEEN ISSUED A FLOW TIME WINDOW INTO PHX AND I BELIEVE THE TWR CTLR WAS PREOCCUPIED WITH US MAKING OUR FLOW TIME AND WITH ALL THE WX IN THE AREA THAT THEY WERE NOT MONITORING THE ACFT LNDG ON RWY 21. WE SPENT A FEW MOMENTS ON RWY 26 LOOKING AT THE WX ON THE DEP PATH ON THE RADAR TO DECIDE ON A HDG AFTER TKOF. THE TWR APPROVED OUR HDG REQUEST AND CLRED US FOR TKOF, AND AS FAR AS I CAN REMEMBER, DID NOT MENTION THE ACFT ON RWY 21. I DO NOT BELIEVE THAT WE WERE AT FAULT, BUT A COMBINATION OF THE OTHER ACFT NOT FOLLOWING INSTRUCTIONS AND THE TWR CTLR NOT MONITORING THEIR PROGRESS THAT WERE AT FAULT.

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.