37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 303614 |
Time | |
Date | 199504 |
Day | Fri |
Local Time Of Day | 0001 To 0600 |
Place | |
Locale Reference | atc facility : hnl |
State Reference | HI |
Altitude | msl bound lower : 31000 msl bound upper : 33000 |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B747-400 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | cruise other |
Route In Use | enroute : pacific enroute airway : zoa |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : instrument pilot : flight engineer pilot : commercial |
Experience | flight time last 90 days : 80 flight time total : 13000 flight time type : 800 |
ASRS Report | 303614 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : instrument pilot : commercial |
Events | |
Anomaly | non adherence : clearance non adherence : far |
Independent Detector | atc equipment other atc equipment : unspecified |
Resolutory Action | flight crew : exited adverse environment other |
Consequence | faa : investigated |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
The B-747-400 has the capability of communicating with oakland via satellite communication. This international flight was initially cleared to a cruise altitude of FL290. Later, at AA26Z we requested a block altitude of FL290-FL330. The request was approved by ZOA, an initial cruise climb to FL310 was initiated. We stayed at that altitude for some time. Approximately 3 hours later we initiated a climb to FL330. At 145W, time BB22Z, a position report was sent, our altitude was FL330. At BB23Z we received an acceptance of our position report. 4 mins later at BB27Z we received the following message from oak via satellite communication: OAK3 ATC clears air carrier X maintain FL330. Say time able FL350. We felt this clearance, to maintain FL330, odd because we had reported at FL330 in an earlier position report. At BB27Z the message was accepted and at BB29Z we sent another confirmation that we were level at FL330. 3 mins later at BB32 we sent a message stating that we could be level at FL350 by approximately 160W. 16 mins later at BB48Z we received the following satellite communication message from ZOA: oaks ATC clears air carrier X descend to and maintain FL310 report reaching. Descent necessary due to opposite direction company traffic. When this message, via the satellite, appeared on the ACARS screen the ACARS provided 2 prompts 'accept' or 'reject.' the way it is presented to the pilot makes it seem that you do have an option. The lower altitude was unfavorable because of winds and because of the fact that we were down on our fuel score I, as the captain felt that I needed to reject the clearance. When you reject a clearance on the ACARS, a list of reasons present themselves on the ACARS screen, eg, unable, unable due to WX, etc. I selected the unable prompt. A few mins later we were selcaled and a conversation took place between me and hnl. They wanted to know why we didn't want to descend. I told them, because of fuel burn concerns, and I reinforced the fact that they had just cleared us to FL330 and they relayed this to ZOA. In the meantime, we started to reevaluate the higher altitude. The FMC provided and optimum altitude of FL337. This altitude being just 1300 ft below FL350 and the winds looking better than forecast, I then felt that FL350 would be acceptable. When hnl came back to us I advised him of such and we were then cleared via voice communication to climb to and maintain FL350. With that, we started a 1000 FPM climb to FL340 and then climbed the last 1000 ft at 500 FPM. We were level at FL350 at some time prior to CC05Z. This was later confirmed by the relief first officer who remembers being briefed at that altitude, by me, just prior to the first officer relieving the captain at CC05Z. Later, at CC49Z, we received the following message: oak supervisor ATC advises air carrier X possible pilot deviation advise contact ZOA (phone number). Later, at CC58Z, we received the following message: oak supervisor ATC advises air carrier X contact ZOA at arrive station. After our arrival at akl I immediately called oak ATC where I discussed the situation with an ATC supervisor. I told him that I did not understand at the time why the juggling of altitudes, especially when they had just cleared us to FL330. I also told him that I felt that I had the authority/authorized to reject the clearance because of my concerns of fuel score being down and since I was given the option via the ACARS. He inquired as to what rate of climb did we use when climbing to FL350. I told him and he calculated that we had reached FL350 by CC10Z. He explained to me that the criteria they needed was for my flight to reach FL350 by CC12Z. I told him that I felt for sure that we had. He said that he would be sending the report up to quality assurance. It was later, during a debriefing with my crew, that one of the first officer's pointed out that we were level by CC05Z and that ZOA never gave us a time to be level at FL350. Callback conversation with reporter revealed the following information: reporter stated that he believed the ACARS machine (data link) gave a clearance which could be accepted or rejected because that is what the options were on the selection menu of the air carrier's receiver. The captain rejected the clearance to descend as requested from the ACARS message because it did not fit into his fuelconsumption planning. He felt that the 3 people involved (himself, the opposite direction traffic, and the ATC controller) could work out a plan that would be acceptable to all involved. How he was going to do this he could not explain. He was counseled that if he ever gets a clearance to descend, he must follow that clearance. Reporter wanted to negotiate a better solution to his problems at his convenience. He never tried to explain his problem to the ARTCC. His clearance did not help his ability to conserve fuel that's why he turned it down. Analyst knows he did not have a fuel problem, he just thought he did. There are techniques he should better understand to conserve fuel. Once flight crew knew at what altitudes they should be at, and when, they did all they could to comply. They apparently made it. Had the cleared altitude been given, 'cleared to descend FL310 by XX05Z,' analyst believes clearance would have been obeyed.
Original NASA ASRS Text
Title: ALTDEV AS A RESULT OF A FLC THAT REFUSES CLRNC.
Narrative: THE B-747-400 HAS THE CAPABILITY OF COMMUNICATING WITH OAKLAND VIA SATELLITE COM. THIS INTL FLT WAS INITIALLY CLRED TO A CRUISE ALT OF FL290. LATER, AT AA26Z WE REQUESTED A BLOCK ALT OF FL290-FL330. THE REQUEST WAS APPROVED BY ZOA, AN INITIAL CRUISE CLB TO FL310 WAS INITIATED. WE STAYED AT THAT ALT FOR SOME TIME. APPROX 3 HRS LATER WE INITIATED A CLB TO FL330. AT 145W, TIME BB22Z, A POS RPT WAS SENT, OUR ALT WAS FL330. AT BB23Z WE RECEIVED AN ACCEPTANCE OF OUR POS RPT. 4 MINS LATER AT BB27Z WE RECEIVED THE FOLLOWING MESSAGE FROM OAK VIA SATELLITE COM: OAK3 ATC CLRS ACR X MAINTAIN FL330. SAY TIME ABLE FL350. WE FELT THIS CLRNC, TO MAINTAIN FL330, ODD BECAUSE WE HAD RPTED AT FL330 IN AN EARLIER POS RPT. AT BB27Z THE MESSAGE WAS ACCEPTED AND AT BB29Z WE SENT ANOTHER CONFIRMATION THAT WE WERE LEVEL AT FL330. 3 MINS LATER AT BB32 WE SENT A MESSAGE STATING THAT WE COULD BE LEVEL AT FL350 BY APPROX 160W. 16 MINS LATER AT BB48Z WE RECEIVED THE FOLLOWING SATELLITE COM MESSAGE FROM ZOA: OAKS ATC CLRS ACR X DSND TO AND MAINTAIN FL310 RPT REACHING. DSCNT NECESSARY DUE TO OPPOSITE DIRECTION COMPANY TFC. WHEN THIS MESSAGE, VIA THE SATELLITE, APPEARED ON THE ACARS SCREEN THE ACARS PROVIDED 2 PROMPTS 'ACCEPT' OR 'REJECT.' THE WAY IT IS PRESENTED TO THE PLT MAKES IT SEEM THAT YOU DO HAVE AN OPTION. THE LOWER ALT WAS UNFAVORABLE BECAUSE OF WINDS AND BECAUSE OF THE FACT THAT WE WERE DOWN ON OUR FUEL SCORE I, AS THE CAPT FELT THAT I NEEDED TO REJECT THE CLRNC. WHEN YOU REJECT A CLRNC ON THE ACARS, A LIST OF REASONS PRESENT THEMSELVES ON THE ACARS SCREEN, EG, UNABLE, UNABLE DUE TO WX, ETC. I SELECTED THE UNABLE PROMPT. A FEW MINS LATER WE WERE SELCALED AND A CONVERSATION TOOK PLACE BTWN ME AND HNL. THEY WANTED TO KNOW WHY WE DIDN'T WANT TO DSND. I TOLD THEM, BECAUSE OF FUEL BURN CONCERNS, AND I REINFORCED THE FACT THAT THEY HAD JUST CLRED US TO FL330 AND THEY RELAYED THIS TO ZOA. IN THE MEANTIME, WE STARTED TO REEVALUATE THE HIGHER ALT. THE FMC PROVIDED AND OPTIMUM ALT OF FL337. THIS ALT BEING JUST 1300 FT BELOW FL350 AND THE WINDS LOOKING BETTER THAN FORECAST, I THEN FELT THAT FL350 WOULD BE ACCEPTABLE. WHEN HNL CAME BACK TO US I ADVISED HIM OF SUCH AND WE WERE THEN CLRED VIA VOICE COM TO CLB TO AND MAINTAIN FL350. WITH THAT, WE STARTED A 1000 FPM CLB TO FL340 AND THEN CLBED THE LAST 1000 FT AT 500 FPM. WE WERE LEVEL AT FL350 AT SOME TIME PRIOR TO CC05Z. THIS WAS LATER CONFIRMED BY THE RELIEF FO WHO REMEMBERS BEING BRIEFED AT THAT ALT, BY ME, JUST PRIOR TO THE FO RELIEVING THE CAPT AT CC05Z. LATER, AT CC49Z, WE RECEIVED THE FOLLOWING MESSAGE: OAK SUPVR ATC ADVISES ACR X POSSIBLE PLTDEV ADVISE CONTACT ZOA (PHONE NUMBER). LATER, AT CC58Z, WE RECEIVED THE FOLLOWING MESSAGE: OAK SUPVR ATC ADVISES ACR X CONTACT ZOA AT ARRIVE STATION. AFTER OUR ARR AT AKL I IMMEDIATELY CALLED OAK ATC WHERE I DISCUSSED THE SIT WITH AN ATC SUPVR. I TOLD HIM THAT I DID NOT UNDERSTAND AT THE TIME WHY THE JUGGLING OF ALTS, ESPECIALLY WHEN THEY HAD JUST CLRED US TO FL330. I ALSO TOLD HIM THAT I FELT THAT I HAD THE AUTH TO REJECT THE CLRNC BECAUSE OF MY CONCERNS OF FUEL SCORE BEING DOWN AND SINCE I WAS GIVEN THE OPTION VIA THE ACARS. HE INQUIRED AS TO WHAT RATE OF CLB DID WE USE WHEN CLBING TO FL350. I TOLD HIM AND HE CALCULATED THAT WE HAD REACHED FL350 BY CC10Z. HE EXPLAINED TO ME THAT THE CRITERIA THEY NEEDED WAS FOR MY FLT TO REACH FL350 BY CC12Z. I TOLD HIM THAT I FELT FOR SURE THAT WE HAD. HE SAID THAT HE WOULD BE SENDING THE RPT UP TO QUALITY ASSURANCE. IT WAS LATER, DURING A DEBRIEFING WITH MY CREW, THAT ONE OF THE FO'S POINTED OUT THAT WE WERE LEVEL BY CC05Z AND THAT ZOA NEVER GAVE US A TIME TO BE LEVEL AT FL350. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT HE BELIEVED THE ACARS MACHINE (DATA LINK) GAVE A CLRNC WHICH COULD BE ACCEPTED OR REJECTED BECAUSE THAT IS WHAT THE OPTIONS WERE ON THE SELECTION MENU OF THE ACR'S RECEIVER. THE CAPT REJECTED THE CLRNC TO DSND AS REQUESTED FROM THE ACARS MESSAGE BECAUSE IT DID NOT FIT INTO HIS FUELCONSUMPTION PLANNING. HE FELT THAT THE 3 PEOPLE INVOLVED (HIMSELF, THE OPPOSITE DIRECTION TFC, AND THE ATC CTLR) COULD WORK OUT A PLAN THAT WOULD BE ACCEPTABLE TO ALL INVOLVED. HOW HE WAS GOING TO DO THIS HE COULD NOT EXPLAIN. HE WAS COUNSELED THAT IF HE EVER GETS A CLRNC TO DSND, HE MUST FOLLOW THAT CLRNC. RPTR WANTED TO NEGOTIATE A BETTER SOLUTION TO HIS PROBS AT HIS CONVENIENCE. HE NEVER TRIED TO EXPLAIN HIS PROB TO THE ARTCC. HIS CLRNC DID NOT HELP HIS ABILITY TO CONSERVE FUEL THAT'S WHY HE TURNED IT DOWN. ANALYST KNOWS HE DID NOT HAVE A FUEL PROB, HE JUST THOUGHT HE DID. THERE ARE TECHNIQUES HE SHOULD BETTER UNDERSTAND TO CONSERVE FUEL. ONCE FLC KNEW AT WHAT ALTS THEY SHOULD BE AT, AND WHEN, THEY DID ALL THEY COULD TO COMPLY. THEY APPARENTLY MADE IT. HAD THE CLRED ALT BEEN GIVEN, 'CLRED TO DSND FL310 BY XX05Z,' ANALYST BELIEVES CLRNC WOULD HAVE BEEN OBEYED.
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.