37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 541576 |
Time | |
Date | 200203 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : tus.airport |
State Reference | AZ |
Altitude | agl single value : 500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : tus.tower |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | climbout : takeoff |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : tus.tower |
Operator | other |
Make Model Name | Fighting Falcon F16 |
Operating Under FAR Part | Part 91 |
Flight Phase | landing : go around |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 210 flight time total : 7800 flight time type : 5300 |
ASRS Report | 541576 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time last 90 days : 200 flight time total : 4050 flight time type : 1700 |
ASRS Report | 541579 |
Events | |
Anomaly | conflict : nmac incursion : runway non adherence : far non adherence : published procedure non adherence : required legal separation |
Independent Detector | aircraft equipment : tcas other flight crewa other flight crewb |
Resolutory Action | controller : issued advisory flight crew : took evasive action flight crew : took precautionary avoidance action |
Consequence | faa : reviewed incident with flight crew other |
Miss Distance | horizontal : 200 vertical : 200 |
Supplementary | |
Problem Areas | ATC Human Performance Airport Environmental Factor Flight Crew Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
Tus had just changed the active runway from 11 to 29 and we were the first of three air carriers at the end waiting departure. Tower frequency was extremely heavy with numerous (at least four) small GA planes to parallel runway in the pattern and several ANG F-16's working the pattern as well. Tower told us to position and hold on 29R, followed shortly by instructions to taxi off the runway as approach wasn't accepting departures. We were told to take the first right. The first right off was A15, about 2000 ft from the numbers of runway 29R. As we approached A-15 the tower told us we were then cleared for takeoff. As we had just put 2000 ft of runway behind us, I wanted to check the performance and told the tower we would need a few seconds to do that. I believe we said 15 seconds and we wanted to hold our position. Tower said fine and continued with working his VFR pattern traffic. Satisfied with the performance, I wanted to verify with the tower we were still cleared for takeoff which took some time to break in on the frequency. The tower controller said we were cleared for takeoff and said there was an F-16 on final. We started down the runway and heard numerous xmissions over the radio regarding cessna's and the like and rotated normally. After rotation (first officer's leg), I noticed a yellow TA on the TCAS and assumed it was a GA airplane on the parallel runway. Tower then said something to the effect 'previously called F-16 traffic no factor, switch to departure'. About that time, the TCAS gave 'monitor vertical speed' and I noticed the target at 300 ft below us and slightly to the right. At that time, we were climbing through about 700 ft. Next came 'climb' and the red arc on the TCAS. The first officer said he saw the F-16 below and about two wing lengths to the right of us turning away. Before switching to departure, I asked the tower about the F-16 and he said he called it. The first officer then reminded me, he said the F-16 was on final. We thought he was behind us. After discussing what happened with the first officer, we came to the conclusion the F-16 had come from behind, accelerated at low altitude. Until below and ahead of us, and then turned right for his downwind. His maneuver caused our TCAS to give a 'climb' RA even though we were already climbing at maximum rate following takeoff. We did not hear any xmissions from the F-16 and I do not know if he even ever saw us. The tower controller seemed very disinterested in our concerns. Supplemental information from acn 541579: I noticed the F-16 approximately 200 ft below us and approximately 200 ft to my right and climbing. He passed us and made a crosswind turn away from us. I never heard the tower controller point out the traffic after he initially told us the F-16 was on final. The captain queried the tower and they responded he notified us it was no factor and gave us a switch to departure. Tower was very busy and could easily have told the F-16 to go around prior to our takeoff. This would have prevented the problem. There was no reason for the F-16 to be where he was. Callback conversation with reporter revealed the following information: captain advised incident was elevated through company to its ATC coordinator. As of yet, no response has been received by reporter.
Original NASA ASRS Text
Title: DEPING B737 ON INITIAL TKOF CLB FROM TUS RWY 29R IS PASSED BY F-16 ON GAR.
Narrative: TUS HAD JUST CHANGED THE ACTIVE RWY FROM 11 TO 29 AND WE WERE THE FIRST OF THREE AIR CARRIERS AT THE END WAITING DEP. TWR FREQ WAS EXTREMELY HEAVY WITH NUMEROUS (AT LEAST FOUR) SMALL GA PLANES TO PARALLEL RWY IN THE PATTERN AND SEVERAL ANG F-16'S WORKING THE PATTERN AS WELL. TWR TOLD US TO POSITION AND HOLD ON 29R, FOLLOWED SHORTLY BY INSTRUCTIONS TO TAXI OFF THE RWY AS APCH WASN'T ACCEPTING DEPARTURES. WE WERE TOLD TO TAKE THE FIRST RIGHT. THE FIRST RIGHT OFF WAS A15, ABOUT 2000 FT FROM THE NUMBERS OF RWY 29R. AS WE APCHED A-15 THE TWR TOLD US WE WERE THEN CLRED FOR TKOF. AS WE HAD JUST PUT 2000 FT OF RWY BEHIND US, I WANTED TO CHECK THE PERFORMANCE AND TOLD THE TWR WE WOULD NEED A FEW SECONDS TO DO THAT. I BELIEVE WE SAID 15 SECS AND WE WANTED TO HOLD OUR POSITION. TWR SAID FINE AND CONTINUED WITH WORKING HIS VFR PATTERN TFC. SATISFIED WITH THE PERFORMANCE, I WANTED TO VERIFY WITH THE TWR WE WERE STILL CLRED FOR TKOF WHICH TOOK SOME TIME TO BREAK IN ON THE FREQ. THE TWR CTLR SAID WE WERE CLRED FOR TKOF AND SAID THERE WAS AN F-16 ON FINAL. WE STARTED DOWN THE RWY AND HEARD NUMEROUS XMISSIONS OVER THE RADIO REGARDING CESSNA'S AND THE LIKE AND ROTATED NORMALLY. AFTER ROTATION (FO'S LEG), I NOTICED A YELLOW TA ON THE TCAS AND ASSUMED IT WAS A GA AIRPLANE ON THE PARALLEL RWY. TWR THEN SAID SOMETHING TO THE EFFECT 'PREVIOUSLY CALLED F-16 TFC NO FACTOR, SWITCH TO DEP'. ABOUT THAT TIME, THE TCAS GAVE 'MONITOR VERTICAL SPEED' AND I NOTICED THE TARGET AT 300 FT BELOW US AND SLIGHTLY TO THE R. AT THAT TIME, WE WERE CLIMBING THROUGH ABOUT 700 FT. NEXT CAME 'CLIMB' AND THE RED ARC ON THE TCAS. THE FO SAID HE SAW THE F-16 BELOW AND ABOUT TWO WING LENGTHS TO THE RIGHT OF US TURNING AWAY. BEFORE SWITCHING TO DEP, I ASKED THE TWR ABOUT THE F-16 AND HE SAID HE CALLED IT. THE FO THEN REMINDED ME, HE SAID THE F-16 WAS ON FINAL. WE THOUGHT HE WAS BEHIND US. AFTER DISCUSSING WHAT HAPPENED WITH THE FO, WE CAME TO THE CONCLUSION THE F-16 HAD COME FROM BEHIND, ACCELERATED AT LOW ALTITUDE. UNTIL BELOW AND AHEAD OF US, AND THEN TURNED RIGHT FOR HIS DOWNWIND. HIS MANEUVER CAUSED OUR TCAS TO GIVE A 'CLIMB' RA EVEN THOUGH WE WERE ALREADY CLIMBING AT MAX RATE FOLLOWING TKOF. WE DID NOT HEAR ANY XMISSIONS FROM THE F-16 AND I DO NOT KNOW IF HE EVEN EVER SAW US. THE TWR CTLR SEEMED VERY DISINTERESTED IN OUR CONCERNS. SUPPLEMENTAL INFO FROM ACN 541579: I NOTICED THE F-16 APPROX 200 FT BELOW US AND APPROX 200 FT TO MY R AND CLIMBING. HE PASSED US AND MADE A CROSSWIND TURN AWAY FROM US. I NEVER HEARD THE TWR CTLR POINT OUT THE TFC AFTER HE INITIALLY TOLD US THE F-16 WAS ON FINAL. THE CAPT QUERIED THE TWR AND THEY RESPONDED HE NOTIFIED US IT WAS NO FACTOR AND GAVE US A SWITCH TO DEPARTURE. TWR WAS VERY BUSY AND COULD EASILY HAVE TOLD THE F-16 TO GO AROUND PRIOR TO OUR TKOF. THIS WOULD HAVE PREVENTED THE PROB. THERE WAS NO REASON FOR THE F-16 TO BE WHERE HE WAS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: CAPT ADVISED INCIDENT WAS ELEVATED THROUGH COMPANY TO ITS ATC COORDINATOR. AS OF YET, NO RESPONSE HAS BEEN RECEIVED BY RPTR.
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.