 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B767-300 flight crew forgets to advise oceanic clearance delivery of the fact that they had their oceanic clearance which had been received by datalink.
| Attributes | |
| ACN | 403630 |
| Time | |
| Date | 199805 |
| Day | Fri |
| Local Time Of Day | 0001 To 0600 |
| Place | |
| Locale Reference | atc facility : czqx |
| State Reference | NF |
| Altitude | msl bound lower : 36000 msl bound upper : 36000 |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | artcc : czqx tower : phl |
| Operator | common carrier : air carrier |
| Make Model Name | B767-300 and 300 ER |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other 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 |
| ASRS Report | 403630 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : commercial |
| ASRS Report | 403629 |
| Events | |
| Anomaly | non adherence : published procedure |
| Independent Detector | other controllera |
| Resolutory Action | other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Location: west of 4950N. At XA28Z we received clearance from datalink with appropriate and successful miscellaneous 90/91 entries. Approximately 10 mins after we received our clearance, we told gander that we had our oceanic clearance with, 'expect FL360' and that we would like to climb to FL360 now. Clearance to FL360 was given and we climbed. At approximately XB30Z, 10 mins prior to 4950N, gander on 122.37 requested we return to previous frequency of 132.05. This controller informed us that we did not confirm with oceanic clearance delivery that we had received our clearance, but that he had already done it for us and, not to worry, just to make sure you do it next time. I believe that our call to gander informing them that we had our oceanic clearance with our request for an early climb to FL360 might have caused the omission of the call to clearance delivery -- even though the first officer and myself had highlighted the frequency to do this on the release and the track message.
Original NASA ASRS Text
Title: A B767-300 FLC FORGETS TO ADVISE OCEANIC CLRNC DELIVERY OF THE FACT THAT THEY HAD THEIR OCEANIC CLRNC WHICH HAD BEEN RECEIVED BY DATALINK.
Narrative: LOCATION: W OF 4950N. AT XA28Z WE RECEIVED CLRNC FROM DATALINK WITH APPROPRIATE AND SUCCESSFUL MISC 90/91 ENTRIES. APPROX 10 MINS AFTER WE RECEIVED OUR CLRNC, WE TOLD GANDER THAT WE HAD OUR OCEANIC CLRNC WITH, 'EXPECT FL360' AND THAT WE WOULD LIKE TO CLB TO FL360 NOW. CLRNC TO FL360 WAS GIVEN AND WE CLBED. AT APPROX XB30Z, 10 MINS PRIOR TO 4950N, GANDER ON 122.37 REQUESTED WE RETURN TO PREVIOUS FREQ OF 132.05. THIS CTLR INFORMED US THAT WE DID NOT CONFIRM WITH OCEANIC CLRNC DELIVERY THAT WE HAD RECEIVED OUR CLRNC, BUT THAT HE HAD ALREADY DONE IT FOR US AND, NOT TO WORRY, JUST TO MAKE SURE YOU DO IT NEXT TIME. I BELIEVE THAT OUR CALL TO GANDER INFORMING THEM THAT WE HAD OUR OCEANIC CLRNC WITH OUR REQUEST FOR AN EARLY CLB TO FL360 MIGHT HAVE CAUSED THE OMISSION OF THE CALL TO CLRNC DELIVERY -- EVEN THOUGH THE FO AND MYSELF HAD HIGHLIGHTED THE FREQ TO DO THIS ON THE RELEASE AND THE TRACK MESSAGE.
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.