1998-10 · NASA ASRS report 416285
A B747-400 FLYING FROM LAX TO AKL RECEIVES A DATA LINK MESSAGE TO CLB; BUT IT IS INTENDED FOR ANOTHER FLT. MESSAGE TO CLB WAS NOT DIRECTED TO PROPER ACFT.
AT APPROX XX41Z OUR POS WAS ALONG TRACK X AND HAD RECENTLY PASSED N0400.0 W15000.0 AT FL310. WE WERE IN CONTACT WITH OAKLAND OCEANIC CTL VIA COMMERCIAL RADIO; BECAUSE THE NORMAL METHOD OF FANS (DATA LINK) WAS INOP FOR THE PAST 24 HRS. WE COMMUNICATED WITH COMMERCIAL RADIO THROUGH ACARS DATA LINK. AT XX46Z WE RECEIVED A MESSAGE TO CLB AND MAINTAIN FL350. UNLIKE THE USE OF FANS; WE MUST EITHER REJECT OR ACCEPT A MESSAGE BEFORE PRINTING FOR VERIFICATION. WE NOTED 'ACR XYZ' AT BOTTOM OF MESSAGE BUT DID NOT CATCH THE DISCREPANCY 'ACR ABC' IN THE CLRNC MESSAGE ITSELF. SHORTLY AFTERWARDS; WE WERE ABOUT TO QUESTION THE CLRNC ISSUED AND RECEIVED A SELCAL FROM SAN FRANCISCO COMMERCIAL RADIO ON HF RADIO. THEY WANTED TO KNOW OUR SELCAL CODE AND IF WE WERE STILL AT FL310. WE CONFIRMED THE CODE AND BEING LEVEL AT FL310. APPROX 15 MINS LATER; WE RECEIVED A CLB CLRNC TO FL330. WE CONFIRMED AND ACCEPTED; THEN CLBED AND RPTED LEVEL FL330 (WHICH WAS CORRECT FOR US). I BELIEVE ZAN USED THE WRONG TAIL NUMBER FOR SELCAL OR THE WRONG SELCAL CODE AND ISSUED A CLRNC MEANT FOR FLT ACR ABC (IN THEIR SECTOR); BUT THE MESSAGE WAS RECEIVED BY US (ACR XYZ). WE ARE USED TO PRINTING AND VERIFYING THE CLRNC BEFORE ACCEPTING OR REJECTING ON FANS DATA LINK. WHEN RECEIVING ON ACARS DATA LINK; THE PROCESS IS ACCEPT OR REJECT PRIOR TO PRINTING FOR VERIFICATION. WE WILL BE EVEN MORE AWARE OF DATA LINK PITFALLS IN THE FUTURE; RESOLVING ANY QUESTIONS BEFORE ACCEPTANCE OF CLRNCS IN THIS MODE OF COMMUNICATING WITH ATC. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR WAS MENTALLY SET TO ACCEPT A HIGHER ALT. WHEN THIS CLRNC WAS RECEIVED; IT SEEMED APPROPRIATE. THE CLRNC SOUNDED GOOD; SO THE CLRNC WAS ACCEPTED; EVEN THOUGH THE WRONG FLT NUMBER APPEARED AT THE TOP. PLT WAS CONCENTRATING ON THE BOTTOM OF THE CLRNC THAT CAN ONLY BE SEEN AFTER THE CLRNC IS ACCEPTED. FLC REVIEWED THE CLRNC IN ITS ENTIRETY; THEN THEY DISCOVERED THE WRONG FLT NUMBER AT THE TOP OF THE PRINTED CLRNC. THEY HAD NOT LEFT THEIR CRUISE ALT BECAUSE VERIFICATION OF CLRNC WAS NOT COMPLETE. THE FLC DECIDED TO CALL ARTCC TO VERIFY THE CLB CLRNC. AS THEY WERE ABOUT TO CALL; ARTCC CALLED THEM ON HF GENERAL PURPOSE RADIO AND QUERIED THEM AS TO WHAT THEIR CALL SIGN WAS AND SELCAL CODE. ARTCC ALSO ASKED THEIR ALT TO VERIFY THEY WERE STILL AT FL310. LATER; ARTCC CALLED THEM BACK AND CLRED THE FLC TO FL330. RPTR STATES THAT TO SEE THE ENTIRE CLRNC; IT HAS TO BE ACCEPTED OR REJECTED; NOT UNTIL THEN CAN IT BE FULLY READ TO ASCERTAIN ALL OF THE INSTRUCTIONS. RPTR FEELS THAT ZAN MADE THE MISTAKE IN SENDING A FALSE MESSAGE TO HIS ACFT.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.