37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 716934 |
Time | |
Date | 200611 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : tus.airport |
State Reference | AZ |
Altitude | agl single value : 100 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : tus.tower |
Operator | common carrier : air carrier |
Make Model Name | MD-80 Series (DC-9-80) Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : takeoff |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : tus.tower |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
ASRS Report | 716934 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | conflict : airborne critical |
Independent Detector | aircraft equipment : tcas other flight crewa |
Resolutory Action | flight crew : took evasive action |
Miss Distance | unspecified : 300 |
Supplementary | |
Problem Areas | Chart Or Publication Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Situations | |
Chart | airport : tus.airport |
Narrative:
This is some follow up information for the previously submitted report concerning an near midair collision after takeoff from tus. After talking to the tower supervisor and reviewing the 10-9 chart; I have come to find out that there is a separate tower frequency for the parallel runway at tus that is not printed on the 10-9. I feel that my situational awareness and understanding of the event would have been enhanced had I been aware of this information. Is this an omission from the tus 10-9 chart that needs to be rectified? Immediately after takeoff; I noticed a light aircraft ahead of us and took evasive maneuvers. I had not yet called for gear up. It was an immediate response but not violent to where the passenger were even aware of it. During the evasive maneuver; there was a TCAS TA; I believe that it read out 300 ft. We told tower that we would file an near midair collision report and advised dispatch after we reached cruise altitude. My best guess is that the light aircraft had taken off from the parallel runway and turned the wrong direction.
Original NASA ASRS Text
Title: AN MD80 EXPERIENCED A CONFLICT ON TKOF OUT OF TUS. RPTR CITES UNLISTED COM FREQ FOR PARALLEL RWY AS CONTRIBUTORY.
Narrative: THIS IS SOME FOLLOW UP INFO FOR THE PREVIOUSLY SUBMITTED RPT CONCERNING AN NMAC AFTER TKOF FROM TUS. AFTER TALKING TO THE TWR SUPVR AND REVIEWING THE 10-9 CHART; I HAVE COME TO FIND OUT THAT THERE IS A SEPARATE TWR FREQ FOR THE PARALLEL RWY AT TUS THAT IS NOT PRINTED ON THE 10-9. I FEEL THAT MY SITUATIONAL AWARENESS AND UNDERSTANDING OF THE EVENT WOULD HAVE BEEN ENHANCED HAD I BEEN AWARE OF THIS INFO. IS THIS AN OMISSION FROM THE TUS 10-9 CHART THAT NEEDS TO BE RECTIFIED? IMMEDIATELY AFTER TKOF; I NOTICED A LIGHT ACFT AHEAD OF US AND TOOK EVASIVE MANEUVERS. I HAD NOT YET CALLED FOR GEAR UP. IT WAS AN IMMEDIATE RESPONSE BUT NOT VIOLENT TO WHERE THE PAX WERE EVEN AWARE OF IT. DURING THE EVASIVE MANEUVER; THERE WAS A TCAS TA; I BELIEVE THAT IT READ OUT 300 FT. WE TOLD TWR THAT WE WOULD FILE AN NMAC RPT AND ADVISED DISPATCH AFTER WE REACHED CRUISE ALT. MY BEST GUESS IS THAT THE LIGHT ACFT HAD TAKEN OFF FROM THE PARALLEL RWY AND TURNED THE WRONG DIRECTION.
Data retrieved from NASA's ASRS site as of January 2009 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.