37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 304189 |
Time | |
Date | 199505 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : tbc |
State Reference | AZ |
Altitude | msl bound lower : 35000 msl bound upper : 35000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zla |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise other |
Route In Use | enroute airway : v-236 |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : flight engineer pilot : cfi pilot : atp |
Experience | flight time last 90 days : 225 flight time total : 13500 flight time type : 225 |
ASRS Report | 304189 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : second officer |
Qualification | pilot : flight engineer pilot : atp |
Experience | flight time last 90 days : 260 flight time total : 5000 flight time type : 240 |
ASRS Report | 304455 |
Events | |
Anomaly | conflict : airborne less severe non adherence : clearance non adherence : published procedure other spatial deviation |
Independent Detector | other controllera other flight crewa |
Resolutory Action | controller : issued new clearance other |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 18000 vertical : 2000 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Approaching the tbc VOR, the captain was flying. ZDV issued a frequency change to lax perceived by all as 128.37. I (first officer), was on the PA pointing out the grand canyon and the captain made the frequency change. We could hear attempts to make contact with ZLA by the aircraft as well as ourselves, but didn't hear lax respond. I assumed lax was on the 'land line' or using another frequency at the moment and too busy to respond. At this time the captain was slightly off course to the left and started a turn to the right. I had completed my PA announcement and given up on receiving lax on 128.37 and thus returned to den on (I think 127.35) asking for a repeat of the frequency. I was given 128.07 and upon changeover was called by ZLA the second I tuned in. They then asked us to turn left and descend to FL330. We complied quickly and shortly thereafter given instructions to turn right to 270 degrees and climb again to FL350. As we made the first turn to the left we could see another aircraft off to our right at a pretty good distance away (estimated at 3-4 mi plus). Lax then asked us to call the center upon landing to discuss a possible pilot deviation. ZLA asked the other aircraft if they had a TCASII alert and they advised, no. We did not get a TCASII alert either. After landing, the captain spoke with ZLA by phone and was advised we had been off course and getting close to another aircraft. Lax also said they got no computer alert nor did it print an occurrence. The captain and the ATC supervisor discussed the frequency change problem and the off course situation, plus the other traffic converging at FL350. To prevent another occurrence of this type situation in the future I will increase my alertness to what is happening with the aircraft tracking and help or make accurate frequency changes as soon as possible. If a frequency is in question I will immediately make a second attempt if no contact quickly return to the previous frequency for verification. For ATC frequency changes, I would like to see them as far away from busy airway intxns as possible. PA announcements in the future, I will make only when nothing else is going on. I do now wonder about the filed course clrncs of both our aircraft, and the other off to our right, since we were both approaching the tuba city VOR at FL350. Even though we were slightly off course, was there an altitude change planned for one of us when reaching the vicinity of the tbc VOR?
Original NASA ASRS Text
Title: DEV FROM CLRNC RTE -- AN OFF COURSE AND OFF FREQ ACR CAUSES THE CTLRS TO HAVE TO MANEUVER IT TO AVOID A POTENTIAL CONFLICT.
Narrative: APCHING THE TBC VOR, THE CAPT WAS FLYING. ZDV ISSUED A FREQ CHANGE TO LAX PERCEIVED BY ALL AS 128.37. I (FO), WAS ON THE PA POINTING OUT THE GRAND CANYON AND THE CAPT MADE THE FREQ CHANGE. WE COULD HEAR ATTEMPTS TO MAKE CONTACT WITH ZLA BY THE ACFT AS WELL AS OURSELVES, BUT DIDN'T HEAR LAX RESPOND. I ASSUMED LAX WAS ON THE 'LAND LINE' OR USING ANOTHER FREQ AT THE MOMENT AND TOO BUSY TO RESPOND. AT THIS TIME THE CAPT WAS SLIGHTLY OFF COURSE TO THE L AND STARTED A TURN TO THE R. I HAD COMPLETED MY PA ANNOUNCEMENT AND GIVEN UP ON RECEIVING LAX ON 128.37 AND THUS RETURNED TO DEN ON (I THINK 127.35) ASKING FOR A REPEAT OF THE FREQ. I WAS GIVEN 128.07 AND UPON CHANGEOVER WAS CALLED BY ZLA THE SECOND I TUNED IN. THEY THEN ASKED US TO TURN L AND DSND TO FL330. WE COMPLIED QUICKLY AND SHORTLY THEREAFTER GIVEN INSTRUCTIONS TO TURN R TO 270 DEGS AND CLB AGAIN TO FL350. AS WE MADE THE FIRST TURN TO THE L WE COULD SEE ANOTHER ACFT OFF TO OUR R AT A PRETTY GOOD DISTANCE AWAY (ESTIMATED AT 3-4 MI PLUS). LAX THEN ASKED US TO CALL THE CTR UPON LNDG TO DISCUSS A POSSIBLE PLT DEV. ZLA ASKED THE OTHER ACFT IF THEY HAD A TCASII ALERT AND THEY ADVISED, NO. WE DID NOT GET A TCASII ALERT EITHER. AFTER LNDG, THE CAPT SPOKE WITH ZLA BY PHONE AND WAS ADVISED WE HAD BEEN OFF COURSE AND GETTING CLOSE TO ANOTHER ACFT. LAX ALSO SAID THEY GOT NO COMPUTER ALERT NOR DID IT PRINT AN OCCURRENCE. THE CAPT AND THE ATC SUPVR DISCUSSED THE FREQ CHANGE PROB AND THE OFF COURSE SIT, PLUS THE OTHER TFC CONVERGING AT FL350. TO PREVENT ANOTHER OCCURRENCE OF THIS TYPE SIT IN THE FUTURE I WILL INCREASE MY ALERTNESS TO WHAT IS HAPPENING WITH THE ACFT TRACKING AND HELP OR MAKE ACCURATE FREQ CHANGES AS SOON AS POSSIBLE. IF A FREQ IS IN QUESTION I WILL IMMEDIATELY MAKE A SECOND ATTEMPT IF NO CONTACT QUICKLY RETURN TO THE PREVIOUS FREQ FOR VERIFICATION. FOR ATC FREQ CHANGES, I WOULD LIKE TO SEE THEM AS FAR AWAY FROM BUSY AIRWAY INTXNS AS POSSIBLE. PA ANNOUNCEMENTS IN THE FUTURE, I WILL MAKE ONLY WHEN NOTHING ELSE IS GOING ON. I DO NOW WONDER ABOUT THE FILED COURSE CLRNCS OF BOTH OUR ACFT, AND THE OTHER OFF TO OUR R, SINCE WE WERE BOTH APCHING THE TUBA CITY VOR AT FL350. EVEN THOUGH WE WERE SLIGHTLY OFF COURSE, WAS THERE AN ALT CHANGE PLANNED FOR ONE OF US WHEN REACHING THE VICINITY OF THE TBC VOR?
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.