37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 955565 |
Time | |
Date | 201106 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ABQ.Tower |
State Reference | NM |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Boeing Company Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Military Transport |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying First Officer |
Experience | Flight Crew Last 90 Days 191 Flight Crew Type 2700 |
Person 2 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 290 Flight Crew Type 17000 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
Departing out of abq on runway 26; we were cleared for takeoff and assigned a left turn to heading 210. Rolling out of the turn at approximately 6;300 ft; we received a traffic alert (TA) from the TCAS. Shortly after that we received a resolution advisory (RA) to 'monitor vertical speed' followed by a 'climb' command and I believe next a 'maintain vertical speed' command. I complied with the climb command which was approximately a 4;000 FPM climb. Shortly afterwards; the pilot not flying visually acquired the threat aircraft which was an air force cargo aircraft and directed me to make a right turn in conjunction with the climb to avoid threat aircraft. The pilot not flying also said afterwards that the air force cargo aircraft also made an aggressive right turn away from us as well. Due to the TA and RA; the pilot not flying at this point had not switched over to departure. Once we were clear of the conflict; the pilot not flying then contacted the departure controller and we were assigned a turn to 270. The air force cargo aircraft was on an ILS approach into runway 3 which was NOTAM'd closed. The air force cargo aircraft then queried the departure controller as to why the controller didn't break him off of the approach and the controller replied; 'because the traffic had visual contact on you.' this was not true. We never had visual contact on the air force cargo aircraft; nor did we receive a traffic call from the tower or the departure controller until after both the TA and RA. The ironic part of this was that even though the active runway at the time was 26; we had requested runway 8 for departure and were subsequently told that runway 8 was not available due to traffic. The remainder of the flight was uneventful.
Original NASA ASRS Text
Title: A Boeing departing Runway 26 at ABQ responded to a TCAS RA generated by an Air Force cargo aircraft flying a practice ILS to Runway 3.
Narrative: Departing out of ABQ on Runway 26; we were cleared for takeoff and assigned a left turn to heading 210. Rolling out of the turn at approximately 6;300 FT; we received a Traffic Alert (TA) from the TCAS. Shortly after that we received a Resolution Advisory (RA) to 'monitor vertical speed' followed by a 'climb' command and I believe next a 'maintain vertical speed' command. I complied with the climb command which was approximately a 4;000 FPM climb. Shortly afterwards; the pilot not flying visually acquired the threat aircraft which was an Air Force cargo aircraft and directed me to make a right turn in conjunction with the climb to avoid threat aircraft. The pilot not flying also said afterwards that the Air Force cargo aircraft also made an aggressive right turn away from us as well. Due to the TA and RA; the pilot not flying at this point had not switched over to Departure. Once we were clear of the conflict; the pilot not flying then contacted the Departure Controller and we were assigned a turn to 270. The Air Force cargo aircraft was on an ILS approach into Runway 3 which was NOTAM'd closed. The Air Force cargo aircraft then queried the Departure Controller as to why the Controller didn't break him off of the approach and the Controller replied; 'Because the traffic had visual contact on you.' This was not true. We never had visual contact on the Air Force cargo aircraft; nor did we receive a traffic call from the Tower or the Departure Controller until after both the TA and RA. The ironic part of this was that even though the active runway at the time was 26; we had requested Runway 8 for departure and were subsequently told that Runway 8 was not available due to traffic. The remainder of the flight was uneventful.
Data retrieved from NASA's ASRS site as of April 2012 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.