37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 342834 |
Time | |
Date | 199607 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : yay |
State Reference | NF |
Altitude | msl bound lower : 31000 msl bound upper : 35000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : czqx |
Operator | common carrier : air carrier |
Make Model Name | B747-100 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | cruise other |
Route In Use | enroute : atlantic |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 100 flight time total : 8000 flight time type : 700 |
ASRS Report | 342834 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 190 flight time total : 17000 flight time type : 300 |
ASRS Report | 342840 |
Events | |
Anomaly | altitude deviation : excursion from assigned altitude |
Independent Detector | other controllera |
Resolutory Action | none taken : anomaly accepted |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Coasting in to canada at FL310 from frankfurt, requested FL350 from gander on HF 8879 and also VHF 134.30. VHF controller told us to expect FL350 west of carpe. We then received a SELCAL on HF and received clearance 'cleared from FL310 to FL350, report reaching.' we climbed to FL350 and reported level on VHF, not HF. VHF controller was not amused. Obviously, gander HF and VHF controller were not in agreement. The VHF controller was waiting until he had radar contact before clearing us (I assume). But since we hadn't passed position carpe we were technically still working with the HF controller consequently, we assumed it was a valid clearance. Gander VHF told us we should not be working 2 controllers simultaneously. I agree, and we weren't. We were on VHF. The HF controller contacted us. We questioned why that occurred in the cockpit, but we accepted the clearance to climb as valid since gander SELCAL'ed us to deliver it. Gander does not agree that we received the clearance to climb.
Original NASA ASRS Text
Title: REQUESTED CLRNC CLB FL350 ON HF AND VHF. VHF CTLR ADVISED EXPECT HIGHER BY CARPE. SELCAL'ED ON HF WITH CLRNC TO FL350. RPTED LEVEL ON VHF. CTLR SAID NOT CLRED AND VERY UPSET. B747-200F.
Narrative: COASTING IN TO CANADA AT FL310 FROM FRANKFURT, REQUESTED FL350 FROM GANDER ON HF 8879 AND ALSO VHF 134.30. VHF CTLR TOLD US TO EXPECT FL350 W OF CARPE. WE THEN RECEIVED A SELCAL ON HF AND RECEIVED CLRNC 'CLRED FROM FL310 TO FL350, RPT REACHING.' WE CLBED TO FL350 AND RPTED LEVEL ON VHF, NOT HF. VHF CTLR WAS NOT AMUSED. OBVIOUSLY, GANDER HF AND VHF CTLR WERE NOT IN AGREEMENT. THE VHF CTLR WAS WAITING UNTIL HE HAD RADAR CONTACT BEFORE CLRING US (I ASSUME). BUT SINCE WE HADN'T PASSED POS CARPE WE WERE TECHNICALLY STILL WORKING WITH THE HF CTLR CONSEQUENTLY, WE ASSUMED IT WAS A VALID CLRNC. GANDER VHF TOLD US WE SHOULD NOT BE WORKING 2 CTLRS SIMULTANEOUSLY. I AGREE, AND WE WEREN'T. WE WERE ON VHF. THE HF CTLR CONTACTED US. WE QUESTIONED WHY THAT OCCURRED IN THE COCKPIT, BUT WE ACCEPTED THE CLRNC TO CLB AS VALID SINCE GANDER SELCAL'ED US TO DELIVER IT. GANDER DOES NOT AGREE THAT WE RECEIVED THE CLRNC TO CLB.
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.