CRA

number

Region Status

Title

Description

Findings

1108SN

NAT

CLOSED

NoautotransferfromSanta
MariatoNewYork

CPDLCDIDNOTAUTOMATICALLYSWITCHOVERFROMSANTAMARIATONEWYORKAT44N040W.LOGGEDONTONEWYORKMANUALLY.LOG SantaMaria(automationorcontroller)neglectedtoinitiatethetransfertoKZWY(nocontactadvisoryandnoENDSERVICE).
ONWASSUCCESSFUL.
Therewasnothinginthelogtoindicateanairplane,network,orgroundsystemautomationproblem,sothiswaslikelydueto
controllererror.Asubsequentmanuallogonwassuccessful.

1109SN

NAT

CLOSED

IssuewithDigitalATISatEDDF DIGITALATISATEDDFISSHOWINGUSDEPARTUREATISFORBOTHARRIVALANDDEPARTURE.DIGITALATISISSHOWINGINFODFORARRIVAL ARINCResponse17Jan2012:EDDFswitchedfromacombinedATISmessagetosplitArrival/Departuremessages.ARINC

WHENITSHOULDBEU.
updatedconfigurationstoreflectthischange.

1110GS

NAT

CLOSED

UnabletoLogontoATC

CPCLCINOP.UNABLETOLOGONTOANYATCFACILITIES.ATTEMPTEDDATALINKRESET.

TheairplaneattemptedlogonswithNewYork(KZWY),SantaMaria(LPPO),ZZZZ(Iguesshewasgettingdesperate)andCape
Verde(GVSC).
Thefirsttworespondedwithareject(reasoncode4flightplanmismatch).
ThereasonforthatisalmostcertainlythatthecrewloggedonasadifferentflightIDthanwasfiled(logoncontainedthe2char
airlineIDandtheflightfiledwiththe3charID)andanexactmatchisrequired.
CapeVerdedidn'trejectthem(probablyimplyingtheydon'tdotherequiredflightplancheck),butatleastdidn'testablisha
CPDLCconnection.

1111GS

SOPAC

OPEN

InvalidATCuplinks

FlightrequiredtodiverttoPHNLduetoapassengermedicalissue.Theysentseveralfreetextrerouterequestsandreceived'INVALIDATC
UPLINK'responsetoeachone.FlightrequestedandreceivedclearanceviaHFradio.

ThefreetextdownlinkrequestincludedthetextDCTtoindicateDirectrouting.ThecontrollerusedDCTasarouteelementin
theclearanceandthegroundautomationencodeditincorrectly.Theoperatorcommented,Idon'tbelieveourcrew
requestingadiversionbyfreetextisthebestmethod.

1112GS

SOPAC

OPEN

SATCOMUplinksNot
Delivered,ButDownlinksAre

TRANSFERAND3LOGONSFAILED.D/LRESETAND1LOGONFAILED.CVHFSWITCHEDTODATALOGONOKAT1206Z.

ReferenceISPACG/26FIT/19WP06:IssueswithUplinkMessageDeliveryDiscoveredduringFITPRInvestigation
Intheeventthatthesatcomsystemhasbecometemporarilyunavailablebuttherehasnotbeenacompletelossof
connectivity(e.g.,VHFisstillavailable),someaircraftdonotgenerateaSatcomEstablishedMediaAdvisorywhensatcom
becomesavailableagain.Whenthisoccurs,SITAstrackinglogicmaynotallowforsuccessfuldeliveryofuplinkmessages.

1113GS

1114SN

NOPAC

SOPAC

CLOSEDAS
DUPLICATE

ACTIVE

MissingAirwayIntersection
Waypoints

Incorrectestimatesfollowing
routemodification

TheairplanewasexecutingaDARPrerouteprocedure.
TherouteuplinkwasreceivedfromDispatch,includingthefixwhereairwaysOTR11andY811intersect.
TheroutewasthenrequestedfromOaklandCenter,andtheclearancereceiveddidnotincludetheintersectionwaypoint.
Thismakesitdifficultfortheflightcrewtoverifythattheclearanceisthesameastthecompanyproposedreroute.

AnincorrectestimatewasreceivedfromanA320followingareroute.

TheoriginalAOCuplinkincludedthefixSCOREbetweenthetwoairways(OTR11andY811).Thatwasmissingfromthe
downlinkrequest,andthereforealsomissingfromtheactualclearance.
ThisisaknownissuewithB777(notincludingairwayintersectionfixesinroutedownlinks).IthasbeenreportedintheSouth
PacificaspresentingaproblemforDARPSwherethecoordinationmessagespassedfromoneATCcentertoanotherrequirea
fullydevelopedroute,includingairwayintersections.However,thestandarddefiningdatalinkoperation(RTCADO
258A/EUROCAEED100A)doesnotincludeanyspecificrequirementsforwhattoinclude.
Airbusinvestigationinprogress.

AsubsequentADSCreportcorrectedtheerror.
1115SN

SOPAC

6 SN
1116SN

NAT

CLOSEDAS
DUPLICATE
ACTIVE
ACTIV

Multiplelogonanddownlink
issues
N XT and N XT reports
NEXTandNEXT+1reports
GrosslyOutofConformance

MultipleattemptsrequiredtologontoWAAF.InYBBBATCunabletorespondtodownlinks,noADSC.

Closedasaduplicateof1112.

Aircraft was east bound going from TFFF to FPO. Cleared route of flight was 8N058W N056W 9N050W 37N040W 4 N030W 46N0 0W
AircraftwaseastboundgoingfromTFFFtoLFPO.Clearedrouteofflightwas18N058W21N056W29N050W37N040W42N030W46N020W
47N015WETIKIUN480REGHIUN482KURISUN482NIMER.FlightwasADSCandCPDLCconnected.

Airbusinvestigationinprogress.
Airbus
investigation in progress.

AllADSCreportswerenormaluntiltheperiodicreportthatwasreceivedjustaftertheaircrafthadreportedovertheFIRbetweenNYand
SantaMaria(37N040W).Whenthisperiodicwasreceived,theNEXTandNEXT+1weregrosslyoutofconformance.InsteadofreportingaNEXT
of42N030WandaNEXT+1of46N020Wtheaircraftreported4847N00240Eand48746N00236E.
Ifyoulookatthewaypointreportorperiodicsthatcameinat0144Zor0203Z,youwillseethattheNEXTandNEXT+1werecorrect.However
ifyoulookattheperiodicthatcameinat0205Z,youwillseetheincorrectNEXTandNEXT+1.
Afterreceivingthisreportat0205Z,aDEMANDwasinitiatedandtheADSCreportthatwasreturnedcontainedthecorrectinformation.

CRA
number

Region Status

Title

1117SN

NAT

A333receivesCPDLCmessages TheaircrafthadbeenincontactwithBIRDviaARINC'sVHFnetwork(withintermittentSATCOMmessages)andwiththeexceptionofaverylate Issueidentifiedwithoperator'ssatcomsystem.Airbusisworkingwiththeoperatortocorrecttheproblem.

viaSATCOMbutresponsesare CLAmessagereceivedat12:10(possiblyheldbytheaircraftuntilVHFcontactmade?)nothingremarkableoccurreduntil15:23(otherthana
rejecteduplinkat15:01,NoAck)atwhichtimeaclearancewassent,aMAS/Sreceivedbutnooperationalresponsefollowed.Theclearance
lost
wasrepeatedat15:29withthesameresult.Whentheclearancewasdeliveredviavoiceshortlyafterwardsitturnedoutthatthecrewwere
alreadyattheclearedlevel,havingreceivedtheCPDLCmessage(s).Thecrewadvisedof"intermittentcontact"viadatalink.

ACTIVE

Description

Findings

Interestingly,startingat16:03wereceived,viaVHF,anumberofFANSmessagesthathadobviouslybeenwaitingfortransmisison,these
incudedtheresponsetoourENDSERVICEandanumberofADSmessagesbutNOTtheWILCOmessagesthatwerepresumablyactionedbythe
crewinresponsetotheclearancemessages.
TwoissuesareraisedbythisoneiswhytheaircraftwasusingSATCOMinthefirstplace(itshouldhavebeenwithinreliablerangeofSFJRGS)
andsecondlywhySATCOMwas,apparently,"oneway".Itwouldalsobeinterestingtogetclarificationofjustwhatmessagesareheldand
queuedfor(delayed)transmissionandforhowlong.

1118MM

NAT

OPEN

FirstRCLTimeoutRejection
experiencedfromShanwick

RequestedNATOceanicClearancefromEGGXviaORCA.Wewerewithin90minutewindowwhenrequestwasmade.Receivedusualinitial
"XXXNNNRCLRECEIVEDIFNOCLEARANCEWITHIN15MINUTESREVERTTOVOICEPROCEDURES"messageat1157Z.At1205Zreceivedthe
following:"RCLRECEIVEDSHANWICKCLEARANCENOTACKNOWLEDGEDSENDDATALINKACCEPTANCENOW".Theproblemwasthatwehad
notreceivedanydatalinkclearancetoacknowledge.

ThePRinvestigationrevealedthat(1)Shanwickdidinfactsendtheoceanicclearanceat1158Z(seeA620uplinkbelow)and(2)
theavionicsrejecteditasinvalid.Areviewoftheaircraftoperator'sAirlineModifiableInformation(AMI)tableindicatedthat
theAMIrejectedtheoceanicclearancebecauseitcontainedtwelvelines(i.e.,<CR><LF>s)intheclearancetext(i.e.,thepartof
theclearancefollowing"/PIKCLYA.CLX")whiletheAMIonlyallowstenlines.

At1208Zwereceivedthefollowing:"XXXNNNRCLREJECTEDTRANSACTIONTIMEOUTREVERTTOVOICEPROCEDURESENDOFMESSAGE".
WhileIhaveexperiencedandwrittenupthisproblemonnumerousoccasionsfromGanderOCL,thisisthefirsttimethatIhaveexperienced
thisfromShanwickusingORCA.
IamawareoftheoperatorspecificissueswhichhavebeenarticulatedbytheDLMAandwhichtheoperatorhassaidthattheyhaveafixfor;in
fact,oneofmypreviousreportsremainsopenuntilthisfixhasbeenimplemented.TodateIamunawarethatthishasoccurred,asmoretimes
thannotontheGandersidewehavetoreverttovoicetoreceiveourOCL.
WhatisdisturbinghereisthatthosesamespecificaircraftthathadissueswithGanderdidNOThavethesameissuewithShanwick.Soforthe
firsttimetheproblemhascreptinontheeastsideoftheAtlantic.

1119GS

NAT

OPEN

Failedlogonsandtransfers

AdvisedbyBIRDthataddressforwardingtoCZQXhadfailedandtologonmanually.Crewqueriedthisasaccordingtothechartthenext
airspacewasCZUL.AttemptedmanuallogontoCZQX,sucessfulforabout1min,ADSCestablishedthendisplayedCZULasNextCentrebut
transfertoCZULfailed.TwoorthreeatteptedlogonstoCZULfailed.

ReykjaviksetupGanderastheNDA,andthentheaddressforwardingtoGander(CZQX)failedat1917z.Ganderrejecteditasa
flightplanmismatch(FAK4).ReykjavikthensentaCPDLCfreetext"DESIGNATIONOFCZQXASCPDLCNEXTDATAAUTHORITY
HASFAILED.LOGONMANUALLYTOCZQXWHENENTERINGTHECZQXAIRSPACE".

NoteforCRA:CZQXtransferCPDLCwithoutaCONTACTorMONITORinstruction.

ThemanuallogontoCZQXaftertheoneintheautomatictransferhadfailedwasactuallysuccessful.Ganderthentriedto
transferthemtoMontreal(CYUL).Thatfailed,andthemanuallogonattemptstoCYULalsofailed(allreasoncode4flightplan
mismatch).
Thecrewreportwasthattheydidn'tthinktheyshouldbeloggingontoGanderanyway,astheyweren'tenteringtheirairspace,
becausetheywereNorthofN65.Theflightplan,basedonADSwaypointchangeeventreportswas:
N65W040N65W050N65W060N6430W063...
Afterfurtherinvestigation,itappearsthatthereasonthatGanderrejectedtheinitiallogonwasbecausetheyhadnotreceived
thefiledflightplan.TheyhadreceivedaCPLfromReykjavikat1913z.ThiswillcreateaflightplanintheGandersystembutthis
flightplanwillnotcontaintheregistration.ItalsoonlycontainedroutingasfarasNALDIwithanindicationthattherewas
additionalrouting.Afterthefailedlogon,GandermadearequestfortheflightplanfromEurocontrol.Hencethesuccessful
secondlogon.
Montrealdidinfactreceiveaflightplanfromtheairline;howeverthecoreproblemherewasthattheydidnotfileonewith
GanderandassuchthemostrecentdataMontrealhadwastheinformationsenttothembyGandermissingtheregistration.
ThedatawastransferredtoMontrealpriortoupdatingtheregistration.
ThecoreissuewasthereforethefailuretosendtheflightplantoGander.TheroutewentthroughN65W060,whichisactually
ontheboundarybetweenGanderandEdmontonFIRs.However,theairspaceinthatareaisdelegatedtoGanderOceanic.
Theairlineislookingtoensurethattheirflightplanfilingprocessreflectsthis,andthatcrewsareawareoftheairspace
delegation.

CRA
number

Region Status

Title

Description

Findings

1120SN

SOPAC

OPEN

A388CPDLCuplinkssentvia
HFDL

Oneoperator'sA388CPDLCuplinksareagainbeingincorrectlyroutedviaHFDL.ThisissuestartedagaininMarch2011afteranearlierproblem ARINCupdatedconfigson9Feb12forthistailtochooseSITASATCOMoverHFDLregardlessofmostrecentmediaadvisory.
withthisthatwasnotedinFANSPR#711wasresolvedbyARINCinMarch2010.
Waitingforanalysisofperformancedatatoclose.

1121SN

IO

OPEN

DelayedADSpositionforone
operator'sB744aircraft

AircraftsentaADSpositionreportthatwasdelayedby6minuteswhileaircraftwasontheground.AircraftwasexchangingACARSmessages
betweenbothADSreports.

TheFMCgeneratedawaypointchangeeventreportandaperiodicreportgeneratedattheexactsametime(tothetenthofa
second).Theeventwentstraightaway.Theotheronetookseveralminutes,whileotherdownlinksgotsent.

1122SN

NOPAC

CLOSEDAS
DUPLICATE

DelayedADSreport

Aircraftsent2WaypointChangeADSreports,onetoRJJJandtheothertoPAZN.Secondonewasdelayedby12minutes.

Closedasaduplicateof1121.

ThisistheresultofaknownRockwellCollinsCCMUproblem.

TheFMCgeneratedtwoidenticaleventreports.Thefirstgoesimmediately.Thesecondtakesalongtime.Again,thereare
downlinks(andADSuplinks)inbetween.There'salsoa"lostHF"mediaadvisoryrightbeforethesecondonecamedown.
ThisistheresultofaknownRockwellCollinsCCMUproblem.
1123GS

SOPAC

OPEN

DelayedADSreport

AircrafthadmultipleADSandCPDLCmessagesdelayed.AircraftwasgoingfromNFFFFIRtoYBBBFIR.AircraftsentaWilcooverHFDLfollowed TheonlyparticularlyunusualaspectisthedeliveryoftheWILCOonHFDLbeforeitsdeliveryoverSATCOM,butthatmayjustbe
bythesameWilcoonSATCOM.SubsequentCPDLCPOSreportandADSreportsweredelayedbyseveralminutes.AllDBIsandMSNsare
anartifactofthewaySATCOMwasperforming.
sequential.reportsthatweredelayedbyseveralminutes.
Apartfromthat,thelogappearstoshowverypoorSATCOMperformance.TheWILCO(timestamp06:01:25)wasreceivedon
SATCOMat06:10:56(nineandahalfminutes),butthatwasactually8minutesafterthelastdownlink(receivedat6:03:03)
nottooinconsistentwithmultipleretriesonSATCOM(andperhapsadditionaldelaysingettingachannelassignedonthelast
attempt).Laterdownlinkswereprobablysimplyqueuedbehindthisdownlink(andbuildingonthedelaywiththeirownpoor
SATCOMperformance).

1124SN

IO

CLOSED

UnableLOGONVABF

TriedseveraltimestoLogontoVABF,MSGreturnedsays"ReLOGONtoATC"MumbaiVHF132.7informed,theybelievedtherewasno
problemwiththeirsystem.
Techlogentrymade,NoapparenttechinicalProblem

ThefollowingNOTAMWASprovidedbythereportingoperator:"FANS1/AEQUIPPEDACFTOPRWICHENNAIFIROVERBAYOF
BENGALINOCEANICAIRSPACEONATSROUTESB466E,N877,P628,P761,P762,P574,N571,N563,L645ANDL510DESIRING
DATALINKSERVICESAREREQUIREDTOLOGONTOTHEADDRESS'VOMM'AND'VOMF'.CPDLCWILLBEAVBLONLYWITHAFN
LOGONADDRESS'VOMM'".Thelogonwasapparentlysenttothewrongaddress.

1125SN

NOPAC

CLOSED

ADSEmergencyPosition
ReportSenttoPAZN

AircraftwasflyingeasttowestfromPAZAtoPAZN.InitialcontractrequestandhandoffwerebothEmergencyreports.Aircrewconfirmedno
emergencyexistedandthattheyhadnotinitiatedanycontrolpanelactions.Asimilareventoccurredwithanotheraircraftbutwasnot
capturedinatroublereport.Isitpossiblethatanavionicsproblemmighthaveledtothefalseemergencycondition?

1126SN

NOPAC

CLOSEDAS
DUPLICATE

IntermitantADSCandCPDLC AircraftwaseastboundfromKADWtoLPAZon10February2012.AFNLOGONreceivedat12:44andtheproperADSCcontractswere
connection
established.CPDLCalsoestablished.

Basedonareviewofthelogsforthisevent,wesuspectthatthisistheresultofanissuewe'veseenafewtimesoverthelast
severalyears.The747400hasafootrestforthefirstofficeronthesideoftheaislestand,neartotheMCDU(theprimary
interfacetotheflightmanagementcomputer).WhentheFOhastheATCLOGON/STATUSpagedisplayedontheMCDU,itis
possibleforhimtoinadvertentlyactivateADSinemergencymodewithhisfoot.
Closedasaduplicateof1112.

ReceivedallADSCreportsupuntiltheaircraftreached41N050W.Startingat1445Z,wecouldnotcontacttheairplaneviaCPDLC.All
messagessenttotheaircrafteitherdidnotgetthroughordidgetthoughandwedidnotreceivearesponse.
Startingat1506Z,transferoftheCPDLCconnectiontoSantaMariadidnotoccursincetheaircraftwasnotacknowledgingourNDAorany
othertransfermessages(FN_CAD,etc).
Sameproblemoccurredwiththesameaircraftgoingwestboundon11Feb2012fromLPLAtoKADW.
AircraftcameuponHFat1239ZwithoutapositionreportbutinsteadwiththetypicalmessagethatwereceivewhenaCPDLCaircraftcallsfora
SELCALcheck.OnthisHFcontact,theaircraftrequestedF430.ItisobviousthattheaircraftwasthinkingthatitwasconnectedviaCPDLCand
ADSCbutitactuallywasnot.
At1244Z,thefirstAFNLOGONisreceivedfromtheaircraft.Bythistime,theaircraftis5minuteswestof40W.StartingwiththeLOGON
attempt,theaircraftdoesnotrespondtoanyofouruplinkmessagestryingtoestablishbothanADSCconnectionoraCPDLCconnection.All
attemptstoreachtheaircraftviaCPDLCareunsuccessful.
1127GS

NAT

CLOSED

IncorrectaddressusedinNDA OntheeveningofFeb.6th,controllersinGanderreportedreceivinga"notcurrentdataauthority"messageonaircraftontheYtrack.
PrestwickalsoreportedtoGanderthattheywererecievingCPDLCrequestsfromflightsthatwerestillinourarea.

FurtherinvestigationshowedthatNewYorkhasbeenusinganincorrectCPDLCaddressforGander(CYQXinsteadofCZQX).
NewYorkhasadvisedthattheywillbeupdatingtheiradaptationinthenextweek.

InvestigationbyGandershowedthatwewerenottheCDAforflightscomingfromNewYorkontheYtrackhoweverwhenwereceivedthe
FN_ACK,wedidnominatePrestwickastheNDA.TheendservicefromNewYorkresultedinPrestwickbecomingtheCDA.

1128SN

SOPAC

OPEN

Incorrectlat/longuplinkedin
routeclearance

1129SN

SOPAC

CLOSED

ADSCreportspossibly
containedInactiveroutedata

Thecontrolleruplinkedthefollowingrouteclearance:CLEARD34N170E32N180E28N170WDANNOArrivalProcedure:ARRIVALBOOKE8.The Thisbehaviorisactuallytheresultofa"fix"tocorrectasoftwareresetthatcausedtheFMCflightplantoclearwhena
pilotreportedreceiving32N179Eratherthan32N180E.ThedecodedmessageintheOaklanddatashowedthecorrectlat/long:32N180Ewas longitudeofEorW180wasentered.Thefixwastochange180to179.9998topreventthevariablefromblowingup.
uplinkedratherthanwhatthepilotreported:32N179E.
Unfortunately,thisisdisplayedintheflightplanas179.Notethat777and787currentlyhavethesamebehavior.Thereisan
additionalfixinworkforthesetwoairplanestoallowforentryanddisplayofE/W180.Therearecurrentlynoplansforthe
poorold767.
Thepilotchangedtheflightplanforthediversionpriortorequestingclearance,butcontinuedtrackingtoYBBNuntilcleared.
AircraftwasrequestingadiversiontoNWWW.Foraperiodoftime,ADSCreportscontainedPRGindicatingthattheaircraftwasflyingeast
Executionoftheflightplanchangewouldhavetriggeredtheoutofconformance.The(old)744FMCdoesnotcompute
(towardsNWWW),buttheBasicpositionsindicatedthattheaircraftwasactuallyflyingwest(towardsYBBN).
predictionsfortheinactiveroute,sothepilothadtoactivatethediversionflightplantogetpreds.TheFMCappearstohave
behaveditself.

CRA
number

Region Status

Title

Description

Findings

1130SN

SOPAC

IncorrectADSCestimatefor
NEXTB777

ADSCreportscontainedincorrectestimateforNEXTposition

Thisproblemcanoccurunderthefollowingcondition:Theflightplancontainsaplannedstepdownandanarrivalprocedureis
selectedwhichresultsinatopofdescentpriorthestepdownwaypoint.

OPEN

AircraftcrossedTUBBYat2328.AnADSCreportwasreceived(mostprobablyaWaypointChangeEventreport).
TheEstimateforMIDAT(NEXT)containedwithintheADSCreportwas2352.Overaleglengthof110NM,thiswouldhaveresultedinan
unrealisticgroundspeedof270KTS.
ADCRwasuplinkedtotheaircraftat2332totryandcorrecttheestimateerrorforMIDAT.TheestimateforMIDATfromtheresultingADSC
reportchangedto2350,butthiswasstillunrealistic.
At2334,asubsequentDCRuplinkedtotheaircraftresultedinanADSCreportwiththecorrectestimateforMIDATof2340.
BecauseMIDATisattheFIRboundarybetweenYBBBandNZZO,NZZOalsohadADSCcontractsestablishedwiththeaircraftatthetimeofthe
occurrence.NZZOconfirmedthattheyhadreceivedthesameerroneousestimatesfromtheaircraft.

1131SN

NAT

ACTIVE

1132MM

SOPAC

OPEN

KZWYProblemreport

Requestedclimb
Receivedresponse"Unableheightsduetotraffic"
Triedtosendautoresponse"Roger"Failed
Triedtosendfreetext"Roger"failed
Followedby"ComNotAvail"messageat0605
CPDLCrecoveredatselfat0631
Subsequet response went through
IncorrectnextfixtimeinCPDLC AircraftsendsDM48positionreportwithincorrecttimeatnextfix,1322;shouldhavebeen1408.Timesentfornextfixisactuallyreported
positionreport
timeatcurrentfix.ADSreportshowsestimatefor5Sis13:22:36andCPDLCpositionreporthasatimestampof13:22:46sowesuspectthisis
anotherinstanceofthepositionreportbeingsenttoosoonafterwaypointpassage.Subsequentpositionreportat13:28hadcorrectestimate,
butthisreportseemstoincludealotofadditionaldataotherthanthereport.

Thisproblemwastheresultofatemporarylossofsatcom.

Aircraftoperatorreportsthatproblemonlyoccursifpositionreportpageisdisplayedwhenwaypointissequenced:
"Sometimes(iftheposreportpageisdisplayedduringwaypointpassage)thewaypointrefreshesbuttheestimatedtimedoes
notandyouneedtodeselectandreselectthepagetoforceanotherrefresh."
Boeinginvestigationinprogress.

Sameissueagain:8April,CPDLCpositionreportreceivedfor32133S163020Eat0640withnextfixPAPTIat0640.

1133GS

NAT

OPEN

ReceivedAFNLOGON
containedincorrectLatLong

At14:23:17,anAFNLOGONwasreceivedforthisflight.Thelocationoftheaircraft,baseduponthelat/longintheAFNLOGONwas
353106N0722436W.
Problemis,theaircrafthadalreadyleftourairspaceat14:23:17andwasphysicallylocatedinthevicinityofGTKwhichisabout12degrees
southof353106N0722436W.

Thelogsshowagapintransmissionsbetween12:45:23(whenthetransmissionwasreceivedbyARINCsstationatSalisbury
OceanCityinMaryland,and14:23:09,whenalinktestwasreceivedbyARINCsstationsatPuertoPlata(DominicanRepublic)
andProvidenciales(TurksandCaicos).Shortlyafterthat,amediaadvisorywassentindicatingestablishmentofSATCOM(and
thatonlySATCOMwasavailable).
TheAFNlogonthatfollowed(receivedonthegroundat14:23:15)wastimestamped12:51:15(i.e.duringtheperiodofNO
COMM).Itmustthereforehavebeendelayedontheairplane,waitingforthelinktobecreated.
The operator was contacted to find out if there was a problem with their satcom system
Theoperatorwascontactedtofindoutiftherewasaproblemwiththeirsatcomsystem.

1134SN

SOPAC

ACTIVE

Lossofcomms

CrewReport:
AT1047ZTOKZAKCONNEX
LOSTFORAPP10MINS

Itappearsthattheairplanehadabriefsatcomissue(durationofapprox5min).TheproblemwaspassedtoAirbusforfurther
investigation.

1135SN

SOPAC

CLOSEDAS
DUPLICATE

UnabletoestablishCPDLC/
ADSCconnectionswithGLF5

InitialfailuretoestablishCPDLCandADSCConnections(coincidentallyoutsideVHFDLcoverage?).

Closedasaduplicateof1112.

ApproachingTABAL,flightcrewinitiatedAFNlogontoYBBB.Logonreceived.
CPDLCandADSCconnectionswereinitiatedbythegroundsystem.Thesewerebothunsuccessful.
At0539,flightcrewinitiatedanotherAFNlogontoYBBB.Thistime,bothCPDLCandADSCconnectionsweresuccessfullyautomatically
establishedbythegroundsystem.
FlightcrewreportedhavingestablishedsuccessfulCPDLCandADSCconnectionswithKZAKafterdepartingPHNL,buthadbeenunsuccessful
withNFFFandinitiallyunsuccessfulwithYBBB(asabove).
OfpossiblerelevanceisTABAL(wheninitiallogoninitiated)isoutsideVHFDLcoverage,butthesubsequentlogon20minuteslater(closerto
mainlandAustralia)wasprobablywithinVHFDLcoverage.

CRA
number

Region Status

Title

1136MM

SOPAC

CPDLCDownlinksnotreceived InactiveCPDLCconnectionwithYBBBsuccessfullyestablishedat2047.
forB777
At2119,YBBBsentfreetextCPDLCuplinkREQUESTYOUSEQUENCEWAYPOINTPOXAKtoACA033;aNOTCURRENTDATAAUTHORITY
responsewasreceivedbyYBBBat2124(actuallyourrecordsindicatedtwoNCDAresponsesreceivedweretwosentbytheavionics?
PossiblyrelatedtotransitionfromVHFDLtoSATCOM).

CLOSEDAS
DUPLICATE

Description

TheprecedingATSUwasrequestedtouplinktheCPDLCENDSERVICEmessage.Thisappearedtobesuccessful.

Findings
TheARINClogexactlycorroboratesthePRdescription.AsidefromthetwoNOTCURRENTDATAAUTHORITYdownlinks
addressedtoBNECAYA(YBBB),ARINCreceivednootherdownlinksfromtheaircraft.
Noapparentreasonexistsfortheaircrafttohavesenttwoseparate(samesubnetwork,differentMSNs,13secondsapart)NOT
CURRENTDATAAUTHORITYdownlinks.Thesedownlinksarealsosuspectbecauseneitherincludedtherequiredtimestamp.
ClosedasduplicateofPR1145SN.

Fromthispointon,YBBBappearedtobetheCDAbutcouldnotreceiveCPDLCdownlinksfromtheaircraft.Theflightcrewsubsequently
confirmedthefollowingsequenceof(CPDLC)events:
2126YBBBuplinkedREQUESTPOSITIONREPORT
FlightcrewconfirmedreceiptandsentaCPDLCpositionreport
PositionreportnotreceivedbyYBBB
2129YBBBuplinkedSQUAWK[code]
Flightcrewconfirmedreceiptandsentaresponse
WILCOresponsenotreceivedbyYBBB
2155FlightcrewcontactedonVHF
ConfirmedYBBBasactivecentre
DownlinkedanotherCPDLCpositionreport
PositionreportnotreceivedbyYBBB
2157YBBBuplinkedSQUAWK[code]
Flightcrewreceiveduplinkwithin30secondsandsentresponse
WILCOresponsenotreceivedbyYBBB
Theflightcrewdidnotindicateanyindicationofsysteminoperability.

1137GS

NAT

OPEN

1138SN

SOPAC

ACTIVE

Throughoutthissequenceofevents,theADSCconnectionwiththeaircraftwasoperatingnormally.
Incorrecttimeandpositionin Twoissueshere:
ADSCReportandalsolossof 1.HadanactiveADSCandCPDLCconnectionandatsomepoint,welosttheabilitytocommunicateviaCPDLCandreceiveADSCreportsfrom
connectionforbothADSCand theaircraft.
CPDLCforawhile
2.OncetheADSCconnectionwasreestablished,boththelat/longintheOVofthereportandthetimeinthereportsweregrosslyincorrect.

UnsolicitedWILCOdownlinked WILCOresponsereceivedduringmultiplerequestsforweatherdeviations.NouplinkhadbeensenttotheaircraftbyYBBBwhichrequireda
WILCOresponse.
toYBBB(B777)

OnSATCOMtraffictraces,weseeconnexioninstabilitythewholedayofthe9thofMarch.
Duringthetimeframefrom16:41to18h31,SATCOMtriestologon,theGroundackoftheselogsonbutthennoacksendto
theGround.
Moreoverbeforeandafterthistimeframe,datalinktrafficispresent(respectively3minand8min)
ThereisalsosomeSATCOMPowersupplyinterruptfailures(Intermittent),whichmayexplaintheinstability.Butitisimpossible
tocorrelatethefailedlogonwiththesefailures.
Boeinginvestigationinprogress.
Asecondeventoccuredaweeklater.

TheaircraftenteredAGGGFIRat1412,withYBBBascontrollingauthority.CPDLCconnectionestablishednormally,andpositionreport
The
aircraft entered AGGG FIR at 1412, with YBBB as controlling authority. CPDLC connection established normally, and position report
downlinkedat1413.
NofurtherCPDLCtransactionsuntilthefollowingoccurred.
At1439,theaircraftdownlinkedaCPDLCweatherdeviationrequest(10NMLR).ThiswasshortlyfollowedbyasecondCPDLCweather
deviationrequest(10NMLR)andaWILCOresponse.ThisWILCOresponsewasnotlinkedtoanydialoguewithYBBB.
Theflightcrewwassubsequentlyqueriedregardingthetransactionsat1439.
TheyadvisedthatjustastheyhadselectedSENDforthefirstCPDLCweatherdeviationrequest,anothermessagewasreceived.Theweather
deviationrequestdidnotchangetoSENDING,sothecrewassumedthattheinboundmessagehadblockedtheirweatherdeviationrequest
downlink.
Theflightcrewacknowledgedtheinboundmessage(lateradvisedtobeaweatherdeviationrequestfromcompany)andreinitiatedthe
weatherdeviationrequesttoYBBB.ThisappearedtobecoincidentwiththereceiptoftheunsolicitedWILCOresponse.
TheflightcrewdownlinkedanotherweatherdeviationrequesttoYBBB,whichisconsistentwiththesecondrequestreceived.
Theflightcrewadvisedthattheirlogindicatedtheyhadinfactsent3weatherdeviationrequests.Isitpossibletheaircraftsomehowsentitself
theweatherdeviationrequestandinacceptingtheweatherdeviationfromcompanytheyinfactdownlinkedtheirownresponsetoYBBB?
AndthereforewhyYBBBonlyreceivedtworequests+oneWILCO?
1139SN

NAT

OPEN

NFFF (
i
CDA) d fli ht
did t i di t th
it
f
l d CPDLC di l
di
t t AGGG FIR
SITASATCOMFailureAOWand SITA'sSATCOMservice(AOEandAOW)failed,thelasttransactionpriortothefailurewasloggedat05:46andthefirstsubsequentoneat
AOE
06:42.SITA'sownbulletindocumentstheoutageashavingstartedat05:45andendedat06:43.Thecauseisgivenasan"unexpectedservice
interruptionatAussaguel".
Theservicebulletinadvisingusersoftheoutagewasnotissueduntil06:20,35minutesaftertheservicehadfailed.Moreexpeditious
notificationwouldbedesirable.
ItshouldbenotedthatwhilecentrestotallyreliantonSATCOMmightbemoreseverelyimpactedbysuchafailurethanReykjavik(wheremore
thanhalfthetrafficiscarriedviaVHF),intheabsenceofaservicebulletinitisn'tnecessarilyclearwhatisgoingon,aircraftbeingsometimes
reachable,sometimesnot.Fromlogsitwouldappearthatcontrollerswereconfusedbythesituation.

TheproblemwasduetoanAussaguelGEScomputerissue.Thechanceofsuchissueoccurringisveryremote.However,to
mitigatereoccurrencerisk,analarmhasbeensetatthestationtodetectthistypeofabnormalconditiontoallowthe
operatorstodetectsoonerandtakecorrectiveactionsmorequickly.
Thedelayednotificationwasduetoanemailcapacityissuewhichhassincebeenresolved".

CRA
number

Region Status

Title

Description

Findings

1140SN

SOPAC

CLOSEDAS
DUPLICATE

ADSContractsnotcancelled
butMAS(S)wasreceived

SendCanelAllContractsuplinkat1827:08andreceiveMAS(S)viaVHFat1827:14.NoADSDisconnectdownlinkreceived.ADSreportscontinue ClosedasduplicateofPR923.PR923wascorrectedinB777AIMSBlockPointVersion16.Whenthisproblemoccurred,the
viaSATCOMPOR1from1838:58untilaircraftlandsatSydneyat2037.
avionicswouldacknowledgeandthendiscardtheuplinkinsteadofforwardingittotheappropriateapplication.

1141GS

NAT

CLOSED

Anotherinstancewherea
receivedAFNLOGON
containedanincorrect
Lat/Long

FeedbackisthatthishasbeenseenfromotherB777aircraftaswell.
AircraftwasADSCandCPDLCconnected.

Theavionicsvendorconfirmedthatthiswascausedbyasoftwareissuethatisnowfixed.
ThisaircraftisatthefirstsoftwarelevelthathadADSC(only)enabled.
FirstAFNLOGONoccurredat1602Zwithalat/longof232842N0684318W.SuccessfulestablishmentofADSCcontractsandCPDLCconnection AllFANS1/Aaircrafthavethefix.OnlytheoneswithjustADSCarevulnerable.
soonfollowed.
Theupdateisbeingdoneprogressivelyontherestofthefleet;themajorityhavebeenmigratedalready.
BetweenmultipleADSCreportsbetween1605Zand1746Z.Thelastreportwereceivedwasat1746Zwithapositionof360724N0713908Wat
atimeof1746Z.
ADSCcontractwasnormallyterminatedat1754Z.

1142SN

SOPAC

CLOSEDAS
DUPLICATE

FailedCPDLCtransferto
Oakland

At1841Z,wereceivedanewAFNLOGONfortheaircraft.ThepositionoftheaircraftintheLOGONwas232842N0684318Wwhichwasatleast
9 degrees south of the actual location of the aircraft
Closedasaduplicateof1112.
CrewreportfailedCPDLCtransferat5S.Requireddadalinkresetthennewlogon.
WesentNDAat1217,andIseetwoFCA,FRP,FCPsequencesthenaFCA,FRPfollowedbyendserviceat1258approaching0500Sandterminate
allcontractsbothofwhichareacknowledged.

1143MM

NAT

OPEN

Next we see a logon from aircraft at 1420 and 1423 when aircraft is around 0400N both of which are rejected due no flight plan.
Incorrecttimeandpositionin AircraftwaswestboundandroutedviaAMENOJAINSDBNCANUK1KATL.AircraftwasADSCandCPDLCconnected.AllADSCandCPDLC
ADSCReport
reportswerenormalupuntiltime0749Z.

MultipleADSCpredictedroutegroupscontainedincorrecttimetogoinformationfortheindicatednextwaypoint.Thetime
togoinformationmayactuallyhavebeencorrectforthepreviouswaypointinsomereportsorforthenextplusonewaypoint
inotherreports,however.Theproblemwasreferredto767FMCengineeringatBoeing.

07:49:18AnADSCreportcameinfor301359N0665202Wwithattimeof07:49:02.TheNEXTwasfor312120N077W(JAINS)withattimeof
07:51:18.Thisistotallyincorrectasthedistancefrom301359N0665202WtoJAINSisover10degreesand,unlesswearetalkingaboutthe
SpaceShuttleoraUFO,anaircraftcannotfly10degreesin2minutes.
07:49:34AnotherADSCreportinwithanOVfor301410N0665312Wof07:49:12andaNEXTfor302743N0682639Wof09:06:52.Thistoois
incorrectsincetheaircrafthadpreviouslytoldusviavoicethatit'sestimateforJAINSwas0906.SinceJAINS,whichislocatedat312120N
077W,isnowherenear302743N0682639WthetimeintheADSCreportisdefinitelynotcorrect.
07:57:24Basicallythesameproblem.Aircraftreportsover302314N0675448Wat07:57:09andestimatesJAINSat08:01:17.Thatis4
minutestocoverabout9degrees.
1144GS

NAT

ACTIVE

LossofADSCandCPDLC
connection

AircraftwaseastboundviaZIBUTTILEDOVAPI40N060W44N050W47N040W.
23:23AFNLOGONreceived.ADSCandCPDLCconnectionsestablished.ADSCreportscomesinasexpectedbetweenthistimeand0005Z.

TheairplanestoppedsendingADSreportsafterthereportat0005zon8April.ThenexttransmissionwastheADSreportthat
shouldhavebeenissuedat0025z,butitwasactuallytransmittedat0228z.Apartfromonecompanydownlink,sentjustafter
the0005zreport,therewasnotransmissionfromtheairplaneforalmosttwoandahalfhours,andalluplinks(companyand
ATC)werereturnedas"airplanenotloggedon".

StartingaftertheADSCreportat0005Z,wereceivednofurtherADSCreports.AllattemptstoreachtheaircraftviaCPDLCwereunsuccessful.
TheoperatorwasaskedtoinvestigatewhethertheairplanehadaSATCOMproblem.IthadlostVHFbeforethatandbeenusing
AllDEMANDrequestswentunanswered.Allexpected(required)ADSCreportswereunreceived.Thislasteduntil0210Z.
SATCOM and when datalink returned it was also using SATCOM
SATCOM,andwhendatalinkreturneditwasalsousingSATCOM.
AllmessagestotransfertheaircraftfromNewYorktoGanderwentunansweredaswell
1145SN

SOPAC

ACTIVE

B777unabletosendCPDLC
InactiveCPDLCconnectionwithYBBBsuccessfullyestablishedpriorto1910.TheaircraftwasestimatingtheNFFF/YBBBFIRboundaryat1920. Allcommslookgoodupthrough19:19:10.Theairplaneappearstohavebeenonthefringeof(SITA)VHFcoverage.Atthis
time,NFFFuplinkstheENDSERVICEviaVHF.Themessagedoesnotreceiveanack,buttheairplanemusthavereceivedthe
messagesafterDataAuthority
messagebecausethereisanormaldisconnectsentoverARINCsatcom(XXE).
Transfer
At2024,YBBBuplinkedCPDLCmessageREQUESTPOSITIONREPORT.Thiswasreceivedbytheaircraft,andtheflightcrewattemptedto
downlinkaCPDLCpositionreport.
SITAcontinuestotrytouplinkthemessageviaVHFandtheninternetworksthemessagetoARINCat19:20:11.
At2028,YBBBuplinkedCPDLCmessageREQUESTPOSITIONREPORT.Thiswasreceivedbytheaircraft,andtheflightcrewattemptedto
Icanseetheuplinksnotedinthereport.YBBBinitiatedthedisconnectviaENDSERVICE,andthatprocessworkedcorrectly.
downlinkaCPDLCpositionreport.
At2030,YBBBuplinkedCPDLCmessageSQUAWK[code].Thiswasreceivedbytheaircraft,andtheflightcrewattemptedtoacceptthe
message.

UnderinvestigationatBoeing.

Shortlyaftertheseexchanges,theflightcrewnotedthatalldownlinkstheyhadattemptedtosendtoYBBBhadbeenaborted.
TheflightcrewsubsequentlyreportedthattheyhaddownlinkedaBACKONROUTECPDLCmessageat1916coincidentallyatthesametime
astheDataAuthoritytransferwasoccurringbetweenNFFFandYBBB.
IsitpossiblethattheBACKONROUTECPDLCDownlinkwascoincidentallydownlinkedastheCPDLCENDSERVICEmessagewasreceived
fromNFFF,resultinginacorruptionoftheCPDLCconnection?
Throughoutthissequenceofevents,theADSCconnectionwiththeaircraftwasoperatingnormally.

1146SN

SOPAC

ACTIVE

Unabletocommunicatewith
oneaircraftfrom2233z
0028z

Subsequenttotheseevents,theflightcrewwasinstructedtoreinitiatethelogonprocess,andfrom1935allCPDLCandADSCfunctionality
operatedsuccessfully.
ThelastADSreportforXASKYwasreceivedat2154z(3312N/11839W).At2228z,apositionreportoverFOOTSwasexpected,butnotreceived. PerARINCreview,itappearstherewasanavionicsproblemontheairplane.ProblemunderinvestigationatHoneywelland
From2233z0028z,ATCunsuccessfullyattemptedtocontactXASKYviaCPDLCandAGM.Finally,at0028z,ARINCestablishedcommunications Gulfstream.
withXASKYandapositionreportoverFIZELwasreceivedviaAGM.Thepilotstatedthathebelievedthathehadbeenautomaticallyreporting
throughCPDLCanddidnothaveanyindicationthattherewasaproblemwithhissystem.

CRA
number

Region Status

Title

Description

1147SN

SOPAC

CLOSEDAS
DUPLICATE

UnabletoestablishanADS
connection

From2104z2339z,N455QStried16timestoestablishanADSconnection.EachtimetheFN_CONwasreceivedanFN_AKwasuplinkedalong Closedasaduplicateof1112.
withtheContract,howeverbothappearedtonotreachtheaircraftdueto"UPINTERCEPTAIRCRAFTNOTLOGGEDON".

1148SN

SOPAC

ACTIVE

LossofFANSfunctions

UnderinvestigationatBoeing.NotethatthefailedtransfertoNZZOwastheresultofthetransferringagencyfailingtosendthe
AfterATClogononVHF,atpositionFICKYtheCPDLCpositionreportandsubsequentaltituderequestremainedinthe'sending'mode.After
attemptingtwomasterdatalinkresetsandchangingtheGEStoPORSantaPaula,theOMBproceduretochangethemasterdatalinkVHFradio EndService.Thisaspectwasnotanairplaneproblem.
totherightwascarriedoutandthisinitiallyreturnedalldatalinkfunctionstonormal.Followingaroutineprinterpaperchange(0835Z),allAOC
uplinksfailedtodisplayorprintfortheremainderoftheflight.

1149GS

NAT

CLOSEDAS
DUPLICATE
CLOSEDAS
DUPLICATE
CLOSEDAS
DUPLICATE

TheCPDLCtransferfromKZAKtoNZZOfailedbutsubsequentlogonwassucessfulandFANSfunctionswerenormalfortherestoftheflight.Full
report filed with manufacturer.
ClosedasduplicateofPR923.PR923wascorrectedinB777AIMSBlockPointVersion16.
NoautotransferfromSNNto OnourflightwestboundfromTLVtoEWRtherewasnoAutoTransferoftheADS/CPDLCbetweenSNNandganderon30W.
Gander
Closedasaduplicateof1112.
UnabletologontoKZAK
CPDLCnormalinRJJJbuttransferandsubsequentmanuallogonstoKZAKfailed.ATCadvisedflighttoturnADSCoffdueaircrafteqipment
fault.SubsequentlogontoYBBBsucessfulandoperationsnormalthereafter.
UnabletoreestablishCPDLC CPDLChadbeenestablishedwithaircraft,buttheconnectionwaslostat1230(approx).
ClosedasduplicateofPR923.PR923wascorrectedinB777AIMSBlockPointVersion16.
withB777
SeveralCR.1swereuplinkedbetween1236and1306,butwithnosuccess.

The aircraft should have been within VHF data link coverage at the time.
DelayeddownlinksfromB772 Anumberofdownlinkswerereceivedthathadbeendelayedinexcessof5minutesforanaircraftthatshouldhavebeenwithinVHFdatalink
coverage.

1150SN

SOPAC

1151SN

SOPAC

Findings

CPDLCconnectionreestablishedat1351.

1152SN

SOPAC

ACTIVE

1153SN

SOPAC

CLOSED

TheairplanehadnosatcomsystemandappearedtobeoperatingatthefringeofVHF.Somedownlinksweredelayedwhilethe
airplanetriedtofindagoodstation.

UnabletoestablishADS,CPDLC Between1300and1400,YBBBwasunabletoestablishCPDLCand/orADSCwiththeaircraft.Thepilotstatedthateverythingappearedtobe ARINCconfirmedtherewasaproblematSantaPaulaatthattime.

working,butnoconnectionswereshownbyATC.
withB744
TheflightplanindicatedDAT/SV,andtheaircraftshouldhavebeenwithinVHFdatalinkcoverageatthetime.

1154SN

SOPAC

ACTIVE

1155GS

SOPAC

OPEN

1156SN

SOPAC

CLOSEDAS
DUPLICATE

At 1400, it all came good and started working correctly.

UnabletoestablishADS,CPDLC UnabletoestablishCPDLC/ADSC.
withB737
CPDLCDownlinkmessage
CPDLCDMdecodedas"Badlength"byEurocatXAGDL,returnUM159with"Error10"totheaircraft
unreadablefromB763
DMwasprobablyaweatherdeviationdemand
NoadvertissementtothecontrolerHMI
The aircraft was under VHF PPT1 coverage and send correct ADS report and CPDL before and after this corrupted message.
DelayeddownlinksfromB772 SamedetailsasFITPRASA201205(CRAPRRef:1152SN)(sameaircraftaswell)

TheairplaneinvolvedbelongstoUSAF.Acontracted3rdpartyareinvistigatingontheirbehalf.
ThisproblemhasbeenduplicatedintheBoeinglabandwillbeacandidateforthenext767FMCblockpoint.

ClosedasduplicateofPR1152

Downlinktransmittedat1326(REQUESTCLIMBTOFL360)wasnotreceiveduntil1350.
Questions:
1.WasSATCOMserviceablefortheflightfortheflightatanystage?(i.e.didtheaircraftdepartwithU/SSATCOM,ordiditfailenroute?)
2.IftheSATCOMfailedenroute,whatnotificationwouldtheflightreceive?WhataboutiftheSATCOMwastheonlymediaavailableatthe
time?
1157SN

SOPAC

CLOSEDAS
DUPLICATE

5failedconnectionrequests
CPDLC

NumerousattemptstogetCPDLCconnectionasfollows:
1216:04AFNlogon
1216:22CR1
1216:37DisconnectApplicationError
1216:51CR1
1217:04DisconnectNoReason
1217:27CR1
1217:37DisconnectApplicationError
1220:46AFNlogon
1221:06CR1
NoresponsereceivedfromaircraftbutdidhaveMAS(S)
1221:37AFNlogon
1232:38CR1
NoresponsereceivedfromaircraftbutdidhaveMAS(S)
1238:55AFNlogon
1238:55CR1
1239:13CC1persistencepaysoff;>)

ClosedasduplicateofPR923.PR923wascorrectedinB777AIMSBlockPointVersion16.

1158SN

SOPAC

CLOSED

UplinksviaSATCOMinVHF
coverage

f
f
l
AircraftloggedonviaAKLRGS1224:55CPDLCCR1sentat1225:01withMAS205noresponse.
AircraftloggedonagainviaHLZRGS1227:04andCPDLCCR1sentat1227:05withMAS208(S)receivedviaPOR1followedbyCC1viaHLZRGS
at1227:19
MAS205(S)fororiginalCR1receivedviaPOR1immediatelypriortotheCC1.

ARINChadamissingconfigurationforVHFAustraliatointernetworktoAeroThai.Thisconfigurationchangewasactivatedin
May,2012.

AnalysisofuplinksshowsallMASarebeingreceivedviaSATCOMwhileaircraftisinVHFcoverageandsendingdownlinksviaVHF.WhyisCSP
uplinking via SATCOM to an aircraft in VHF coverage????

CRA
number

Region Status

Title

Description

Findings

1159GS

NAT

FANStrafficdelivered,623
trafficaborted

AircraftsuccessfullyloggedonforFANSandexchangedbothADSandCPDLCtrafficwithBIRDviavariousARINCVHFRGSs.

ThisairplanewasnotconfiguredtoallowinternetworkingofnonFANSmessages,althoughitwasconfiguredtoallow
internetworkingofFANSmessages.Thesituationhasnowbeencorrected.

CLOSED

Aircraftalsorequestedadatalinkclearance(ARINC623)butallattemptsattransmittingsaidclearancefailedwithMAS/Fcode231"No
stationto".SuchabortiveexchangeswereintermingledwiththesuccessfulFANSexchanges.

1160GS

1161SN

NOPAC

NAT

ACTIVE

CLOSEDAS
DUPLICATE

BIRD is a SITA customer for the ACARS connection, the aircraft appeared to exclusively use ARINC RGSs.
Ocean21TreatsOptional
ADARPSreroutewasrequestedfromOaklandCenter,usingaCPDLCrouterequest.
Lat/LongasSeparateWaypoint Therouteclearanceuplinkcontained:
...
MORAY
N3418.0E14600.0
OTR15
...
Thelatitudelongitudewaypointisinfactatexactlythesamelocationastheprecedingwaypoint(MORAY).

TheDARPrequestincludedtheoptionallat/longpositioninformationforwaypointMORAY.
WhenOcean21constructedtherouteclearanceuplink,itinsertedthelatitude/longitudeasaseparatefix,followingMORAY.
ThiswouldhaveresultedinthecrewseeingPARTIALCLEARANCELOADEDandaFPLNDISCONTINUITYbetweenthe
latitude/longitudeandSMOLT.Itwouldhavebeenimpossibletoloadtheairway,asairwayentriescannotgenerallybe
specifiedwithalat/long.
ATCgroundsystemsmustbeabletodealproperlywiththelat/longwhenitisincluded.Itisabasicpartoftheinteroperability
definition(theASN.1messageencoding)forFANS.

FlightreportsreceivingCPDLC AT0220z,pilotadvised,viaGanderRadio,that"whenourCPDLCChangedovertoCZQXwercvdamsgtoCTAM400".Helatersaidthathe
ClosedasduplicateofPR930.
uplinkwhennonewassent.
couldn'tfindthemessageinhislogsandwecannotfindanyrecordinours.TheflighthadreceivedaclearanceafewhourspriorforF400from
WhatthepilotsawwastheremindertoClimbtoandMaintainFL400fromtheuplinkat0027zratherthananewclearance.
KZNY.TheflightwasclearedatFL370.
Wewouldliketounderstandifthemessagewasreceivedinthecockpitatthattimeandwhowastheoriginator.Hadtheflightnotquestioned
this,hemayhaveclimbed.
CouldthisbeacaseofthemessagefromKZNYafterasignificantdelayandjustreceivesecondspriortothetransfertoCZQX?

1162SN

SOPAC

OPEN

CPDLCAnomaly

Uponreturntocockpitaftercrewrest,F/ObriefedATCCPDLCanomaly.At1530Z,receivedandcompliedwithclearancetoclimb/maintain
FL360reportlevel.Reportwasarmedandsentmessageuponleveloff.Subsequently,reportedbackoncoursefrompreviousdeviation
clearance.LogdisplayedLevelFL310.Sentsecondreportbackoncourse.LogagaindisplayedLevelFL310.SenttextJusttoverifylevelFL360
BackonCourse.UtilizedbackoncoursepromptforbothmessagesbutLogdisplayedLevelFL310vsbackoncoursemessage.

1163GS

NAT

OPEN

UpstreamCentrefailsto
relinquishconnectionat
boundary

TheflightpathtooktheaircraftfromCZQXintoBIRD,thenbackintoCZQX.Reykjavik'ssystemautomaticallytransmitteda"greeting"message AsoftwareupgradewasinstalledonAug.20thtoaddressthisissue.AwaitingconfirmationfromoriginatorthatthisPRcanbe
closed.
toprobeforconnectivityaftertheaircrafthadbeendetermined(byextrapolationfromthecoordinatedposition)tohaveenteredBIRD's
airspace.

Onveryrareoccasions,therightFMCmissesasynchronizationeventfromtheleft.Whenthishappens,theleftFMCforcesa
resynchoftherightside.OneofthesideeffectsisthattherightFMC'sATCloggetsmessedup,asdescribedinthisPR.

Theaircraftrespondedwitha"NotCDA"response,consistentwiththeupstreamcentre(Gander)havingfailedtoissueanENDSERVICEatthe
boundary.
Repeatedattemptstoestablishcontact(bymeansofmanuallyinitiatedgreetingmessages)similarlyfailed,weneverachievedCPDLCcontact
withtheflightduringthetimeitspentinourairspace(asideeffectbeingthatwewereunabletobreaktheNDAconnection,theaircraftdidso
eventually).
ThisisbelievedtostemfromadeficiencyinGander'sautomationsystemwhichwehaverepeatedlyrequestedbefixedbutthisneedstobe
confirmed.
confirmed
Theproblemhastwoaspects,bothofwhichhavesafetyimplications.Thefirst(andobvious)oneisthatwearedeniedtheabilityto
communicatewithaircraftforwhichweareresponsible.Thesecondlessobviousoneisthatanyrequestsfromthecrewwouldgotothe
wrongcontroller(inGander)withtheresultingriskthathemightissueaclearancetotheflight,notrealizingthatitisoutsidehisairspace.
1164GS

NAT

OPEN

Downstreamcentrerepeatedly AsdescribedinPR1163GS,Gander'sautomationsystemseemstobeprogrammedtohangontoaircrafttransitingfromCZQXtoBIRDifthe
flightpathwilllatertaketheaircraftbackintoCZQX(thisismerelyatheorypendingresolutionofthatPR).

AsoftwareupgradewasinstalledonAug.20thtoaddressthisissue.AwaitingconfirmationfromoriginatorthatthisPRcanbe
closed.

InordertoestablishaworkingCPDLCconnectionwithsuchaircraft,Reykjavikcontrollersmustthereforecontacttheflightsbyvoicetoinstruct
themtomanuallylogontoReykjavik,inwhoseairspacetheyareoperating.
ThisappearstoconfusethesoftwareinGander'ssystem,whenwe(asperED100)initiatetheaddressforwardingbyinstructingtheaircraftto
logontothatsysteminpreparationforreturningtoCZQXastrange"pingpong"gameensues.Althoughtheaircraftarewithinourairspace
andwearetheirCDA,Gander'sautomationimmediatelysendstheaircraftanFN_CADinstructingittologontouswithoutfollowingthe
ED100specifiedsequenceoffirstensuringthatanNDAnominationiscomplete(whichwouldofcoursefailsincetheyarenotCDA).
Theneteffectofthisstrangedesignisthattheaircraftkeepsloggingontothetwosystemsalternately(ataratedictatedonlybethespeed
withwhichthenetworkcandelivertherelevantmessages).Theratewouldofcoursebeevenhigherwereitnotforthefactthatwewaittosee
thatournominationofGanderasNDAsucceedsbeforeproceedingtotheFN_CADstage.
SinceoursystemisforcedtokeepestablishingaCPDLCconnectionwiththeseaircraft,despitetheirbeinginourairspace,theconnectionis
effectivelyunusable.

CRA
number

Region Status

Title

Description

Findings

1165DN

NAT

ReportofLargeDataand
ClearanceNotDisplayedby
A/CResultinginFailureof
ClimbClearance.

ThefollowingisatranscriptfromtheShanwickControllerwhendealingwithalackofresponsetoanissuedclearanceresultinginthea/cnot
complyingwithaclimbinstruction.Thea/creported"LargeDataBlock"indicationandnoclearancedisplayed.SAATSlogsindicatesuccessful
deliveryoftheuplinkandreturnROGER.

Asoftwarebughasbeenidentifiedandisacandidateforcorrectioninthenextsoftwareupdate.

OPEN

"At1400Itookoverthesectorandshortlyafterreceivedanonconformancereportforanaircraftashehadcrossed20Watalowerlevelthan
expected.Hisclearedprofileshowed'290CX20W310'butonhisautomatic(FANS)reportat20WhewasstillmaintainingF290.Itookacopy
andprobedthefollowingprofile'290CX15W310',thisprofileshowednoconflictssoIleftitPC'dandrequestedademandcontractfromthe
aircraft.ThedemandreportstillshowedtheaircraftatF290soIsentaprioritymessageviaHFinstructingtheaircraftto'CLIMBNOWF310.
REPORTREACHING';thiswasbackedupwithaphonecalltoBallygirreentodeliverthemessagetotheflightassoonaspossible.Theaircraft
readbacktheinstruction.Icheckedthehistoryandattime1320theaircraftrequestedclimbtoF350viacpdlc.Wewereunablehisrequested
levelbutcouldclimbtoalowerlevelso,asperprocedure,sentthemessage'UNABLE/DUETOTRAFFIC/[STANDBYFORHIGHERLEVEL].The
aircraftROGER'dthismessageat1323sothecontrollersenttheclearance'CLIMBTOREACH[F310]BY[50N/20W]/REPORTLEVEL[F310]/
[......UNABLEYOURREQUESTEDLEVEL......]at1325.At1326wereceivedtheWILCOtotheclearance.Iaskedtheaircraftwhytheyhadfailedto
complywiththeclearanceissuedviacpdlcandtheyadvisedthattheyhadreceivednoclearance.Itoldthemthatourhistorysaidotherwise
andthatIwouldneedtotakereportingactiontoestablishwhathadgonewrong.Theaircraftadvisedthat'FORINFOWEHAVEALSOCHECKED
SYSTEMLOGANDFOUNDINSTRUCTIONSBUTTHISWASNEVERRECEIVEDANDNEVERACCEPTED.ONLYTHINGSHORTLYAFTERREQRECD2ND
MSGHEADEDASLARGEDATAWHICHWEACCEPTEDHOWEVERNOCTCWASGIVENTOTHATMSGANDNOLVLCHANGEWASINCLUDEDAND
WEWEREEXPECTINGTOSEETHELARGEDATAAFTERWHICHNEVERFOLLOWED.'At1411theaircraftreportedlevelatF310andshortlyafter
passedintoShannon'sareaofresponsibility".
1166GS

NAT

CLOSED

1167GS

NOPAC

CLOSEDAS
DUPLICATE

1168GS

NOPAC

CLOSEDAS
DUPLICATE

1169GS

NOPAC

1170GS

SOPAC

CLOSEDAS
DUPLICATE
OPEN

1171SN

SOPAC

ACTIVE

AircraftnotloggedontoDSP OverthepastcoupleofmonthswehavebeenreviewingcaseswherewebelieveanaircraftisloggedontoGanderyetwearenotableto
receivepositioninformation(ADS)orsendandreceiveCPDLCmessages.Thishappensrandomlyandinsomecases,thingsjuststartedworking
multipleoccurences
again.
UnabletoEstablishCPDLCwith CRASAJPR4337001
RJJJ
ThecrewreportedestablishingCPDLCwithKZAK,butmessageswerenotacknowledged.Then,onreachingNATSS,theyattemptedtologonto
RJJJ,butthisfailed.
UnabletoConnecttoPAZNor CRASAJPR4417001
RJJJ
ThecrewreportedloggingonnormallytoPAZA,butgettingnoautotransfertoPAZN.
TheythenattemptedmanytimestologontoPAZNandRJJJ,buthadnosuccess.
UnabletoLogontoEdmonton CRASAJPR4670001
ThecrewreportedbeingunabletologontoCZEG(Edmonton)Center.
PartialLoadofTailoredArrival TailoredArrivalrequestedandreceivedbyCPDLC.TAdisplayednormallyonMFDandalsoprintednormallybutwhenloadedintotheFMCby
LOADFMCprompt,thewaypointsbetweenSXCandtherunwayweremissing.TAspeedandaltituderestrictionspriortoandatSXCloaded
normally,indicatingtheflightplanwaspartiallyoverwrittenbytheloadeddata.

CorruptedNextFixinCPDLC
PositionReport

Theloadwasattemptedatotaloffourtimeswiththesameresultsotheuplinkwasrejected.
CPDLCPositionReportreceivedhasNextFixdecodedasS10W1@@

SeveraldifferenteventswereincludedunderthisonePRandwereanalyzedbytheCRA.TheCRAfoundanumberofdifferent
causessuchasapparentfailuresoftheairbornesatcomsystems.
Closedasaduplicateof1121.

Closedasaduplicateof1121.

Closedasaduplicateof1121.
Boeinginvestigationinprogress.

Boeinginvestigationinprogress;possibleduplicateofPR1094,thoughtherearesomedifferences.

ExpectedpositionfromFPLis10S171W
1172MM

SOPAC

OPEN

No.LOAD.promptforroute
uplink

AircraftwasbetweenABARBand31S160E.
AnamendedroutewasissuedbyCPDLCtotheaircrafttorouteitnorthof30S163E(cornerofYBBB/NFFF/NZZOFIRs).Theaircraftwasstillin
An
amended route was issued by CPDLC to the aircraft to route it north of 30S163E (corner of YBBB/NFFF/NZZO FIRs) The aircraft was still in
VHFcommunicationatthetime:
CLEAREDTO[26S170E]VIA[31S160E2935S16300E]

1173GS

NAT

OPEN

1174GS

NOPAC

ACTIVE

1175SN

NAT

CLOSED

Noresponsewasreceivedfromtheaircraftforseveralminutes.Whenqueried,theflightcrewadvisedthattheyhadreceivedtheamended
routeandwereenteringitintotheFMS.Whenaskediftheycouldloadtheclearance,theresponsewasno,andwhenqueriedtheyadvised
that there was No LOAD prompt
ADSReportTimeAheadofReal ThefollowingwasreportedbyShanwickcontroller:
Time
"Attime1043theaircraftreported20Wcorrectlygivinga30Westimateof1130.Attime1135(5minutesafterhis30Westimate)Ireceiveda
FANSreportfromtheflightstatingthecoordinate5657N02020Wattime1144.Notonlywasthistimeinthefuturebutthecoordinateputhim
backto20Wwhenheshouldhavebeenthrough30WtoGanderairspace.Thecoordinategivenwasplausibleandthelevelwascorrectwhen
comparedtohisclearance.IcalledGandertorequestthe30WpositionreportanddetailedtothemtheFANSreportIhadreceived.Ialso
requestedADSdemandcontractreportswhichindicatedthathewasthrough30WasSAATShadcalculated.Subsequently,Ireceivedthe30W
positionreportadvisingtheflighthadcrossed30Wat1134".

PerformanceIssuewithone
operator'sB77Lfleetin
Anchorage
CPDLCConnectionNot
Completed#1

Theaircraftposition,positionsinthefiledflightplan,andpositionsintherouteclearanceuplinkwereconsistentwitheach
other.Noerror/rejectiondownlinkinresponsetotherouteclearanceuplinkwaspresentintheDSPmessagelog.777avionics
in a laboratory setting successfully loaded the same route clearance uplink The LOAD FMC prompt may have been present but
inalaboratorysettingsuccessfullyloadedthesamerouteclearanceuplink.TheLOADFMCpromptmayhavebeenpresentbut
inhibitedbecauseamodifiedroute(MOD)waspending,orbecauseofaknownsoftwareproblemthatcausesanoldroute
clearanceuplinktobeprocessedbytheFMCandthatuplinkcontainedanelement(e.g.,acrossingconstraint)whichneededto
beintheroutebutwasn't.TheCRAandBoeingwillmonitorFITPRsforrecurrencesofthisissue.

It'sclearfromthemessagelogsuppliedthattheproblemwasoneofanold(almostanhourold)messagebeingdelivered.
TherewerenoADSdownlinksbetween1026zand1135z,andafter1028z,everyuplinkattempted(7ADSandoneCPDLC)
resultedinanMASfailure.
ThetimestampinADSreportsisonlythenumberofsecondspastthemostrecenthour.Thehourisadded(inthiscase
erroneously)bytheANSP'sgroundsystem.Ifareportissignificantlydelayed(pastthetopofthehour),itcanappearanhour
newerthanitis.ThesameissueappliedtothenextADSdownlink(at1136z).

ExaminationoftheShanwicklogsconfirmedthedatalinktrafficworkedokbetween0914and1027.From1027to1131alluplinktrafficfailed
i.e.MASfailure.At1135and1136twoADSdownlinkswerereceivedwithpresentpositiontimesof1143and1144respectively.From1138
dowlinkswerereceivedwiththecorrecttime.
SATperformanceofonoperator'sB77LfleetinAnchorageFIRhasbeenobservedtobesignificantlylowerthanperformanceofsamefleetin TheCRAarewaitingforasetofspecificreportstolookat.Theplanistolookatsomeofthelongdelayedones,toseewhatelse
OaklandandNewYorkFIRs.
washappeningonthelink.AlotoftheapparentSATCOMdelaymay,infact,bedelaysinretryingVHF.
On12Jultwoa/cfromthesameoperatorexhibitedthesame/similarissueswithCPDLCconnectivityinGanderandShanwickairspace.

AsoftwarebugintheGandergatewaywasidentifiedandhasbeencorrected.

InGanderairspaceoneaircraftwassentaCR1.MASdeliveryindicatesuplinkwasdelivered,butnoCC1wasreceived.
Whenthea/ctransittedtoShanwick,itwasissuedwithCR1butreceivedaDM64dowlinkstatingCZQXasCDA.

CRA
number

Region Status

Title

Description

Findings

1176SN

NAT

CPDLCConnectionNot
Completed#2

On12Jultwoa/cfromthesameoperatorexhibitedthesame/similarissueswithCPDLCconnectivityinGanderandShanwickairspace.

ClosedasaduplicateofPR1175SN.

CLOSEDAS
DUPLICATE

InGanderairspaceoneaircraftwassentaCR1.MASdeliveryindicatesuplinkwasdelivered,butnoCC1wasreceived.
Whenthea/ctransittedtoShanwick,itwasissuedwithCR1butreceivedaDM64dowlinkstatingCZQXasCDA.

1177GS

1178MM

NOPAC

SOPAC

OPEN

ACTIVE

UnabletoDARPwithstep
climbaltitudesloadedinFMC
Invalidnext+1positionand
altitudeoverlongperiod

UnabletoDARP.WhenrequestingaDARPusingthe"Route2"requestfunctionwekeptgettinga"downlinkerror"message.

Boeinginvestigationinprogress.

WedidhaveourexpectedstepclimbaltitudesloadedintotheFMCpriortomakingthe"Route2"DARPrequest.
Next+1positionandaltitudeshowsasINVALIDinalldownlinkedADSCreports.ThisissimilartothatseeninPR1084SNinNovember2011.

Boeinginvestigationinprogress.

However,thefiledrouteisA464PAPTIBASIV5BwhereBASIV5BisaSTARintoAuckland.ThePAPTIfixgivesnormalposition,altitude,andETA
asfixnextanditwouldbethefirstfixintheSTARthatisshowingasINVALID.Possiblecorrelation?

1179MM

NAT

1180GS

NAT

CLOSEDAS
DUPLICATE
ACTIVE

CPDLCdownlinkscontain
invalidcharacters
FixJOBOCflaggedasnon
oceanicentrypointbycertain
FMC's

NewYorkisreceivingmanyCPDLCrequestswhichcontaininvalidcharactersinthemessage.TheMOPSelementthatcontainsthecharactersis ClosedasaduplicateofPR1155GS
inDM67.
AssignedtoGulfstreamandUSAFforinvestigation.
TwoaircraftwerecomingoutofNYDomesticRADARgoingintoNYOceanic.TheOceanicentryfixwasJOBOCandbothhadroutingafter
JOBOCof41N060W42N050W43N040Wthenpointseast.
BothaircraftadvisedtheNYDomesticRADARcontrollerthatthefixJOBOCwas"notanoceanicentrypoint"intheirFMCandthattheirFMC
wasrejectingtherouting.
TheserouteswerenotsentbyCPDLCsotheymusthavebeenloadedintotheFMContheground.Seemsliketheirdatabasesdidnotrecognize
JOBOC.

1181SN

NAT

CLOSEDAS
DUPLICATE

CPDLCuplinksrejecteddueto WearereceivingrejectionmessagesinresponsetoCPDLCMOPS80clearances.Theformatofthemessagesappeartobecorrect.Please
explainthereasonfortheerrors.IftheyareduetoformatthenIwouldneedtoknowthatsothatwecanmakecorrectionstooursoftware.
'applicationerror'

ClosedasaduplicateofPR964IllegalAirwayNameinDARPTrialUplink.Thisproblemistheresultofasoftwarebuginthe
FAA'sOcean21system.

1182SN

NAT

ACTIVE

UnexpectedADSReport

Boeinginvestigationinprogress.

1183SN

SOPAC

CLOSEDAS
DUPLICATE

CPDLCDownlinksnotreceived InactiveCPDLCconnectionwithYBBBsuccessfullyestablishedat1800.
afterCPDLCtransfer
TheaircraftcrossedtheFIRboundaryat1806.
y

ThefollowingwasreportedbyShanwickATC:
AnADSalertmessagewasproducedbySAATSforanaircraft.
Itindicatedanaltitudedeviation.
Theflighthadbeenclearedonarandomrouteatfl350.
Thealertmessageindicatedfl368(withnoverticalrate).
Acopyplanwasproducedtoprotecttheairspace.
Theflightwasthenaskedifithadclimbed.
ADSdemandcontractsindicatedfl350,andthepilotreportednotleavingfl350duringhisflight.

ClosedasaduplicateofPR1145SN.

At1809,YBBBuplinkedREQUESTPOSITIONREPORT
FlightcrewconfirmedreceiptandsentaCPDLCpositionreportat1809
PositionreportnotreceivedbyYBBB.
At1813,YBBBuplinkedREQUESTPOSITIONREPORT
FlightcrewconfirmedreceiptandsentaCPDLCpositionreportat1813
PositionreportnotreceivedbyYBBB.
At1818,theflightcrewsentafreetextdownlinkwhichreadsomethinglikeCANYOULETUSKNOWIFYOUGETTHISTEXT.Thiswasnot
receivedbyYBBB(hencewhyIdon'tknowtheexactwording....):)
At1821,YBBBuplinkedMONITORBRISBANECENTRE8867
Flightcrewconfirmedreceiptandsentaresponse
WILCOresponsenotreceivedbyYBBB
At1825,theflightcrewdisconnectedtheirCPDLCconnectionandinitiatedanotherlogonwithYBBB.AnactiveCPDLCconnectionwas
established,andalltransactionsfromthispointonweresuccessful.
Theflightcrewdidnotindicateanyindicationofsysteminoperability.
Throughoutthissequenceofevents,theADSCconnectionwasoperatingnormally.

10

CRA
number

Region Status

Title

Description

Findings

1184SN

NAT

YOSSIwaypointdidnotload
intotheFMCasitwasnotin
theFMCdatabase

OnourmostrecenttailoredarrivalintoMIAYOSSIwaypointdidnotloadintotheFMCasitwasnotintheFMCdatabase.Ourinternal
investigationhasconfirmedthatthewaypointwasremovedfromthenavdatabase.ThiswasdonebytheNDBproviderasYOSSIwaypointwas
removedbytheATCcenterandreplacedbySTAPLwiththesamecoordinates.Thiseventdoeshoweverraisethequestionforusonhowthese
waypointsarecontrolledbytheappropriateauthority.TheTAsystemshouldmonitorthewaypointstatusandonlyuse'existing'waypoints.It
doesnothelptheTAtrialsifthewaypointsdonolongerexistespeciallysincethecrewsareinstructedtorejecttheclearanceifthereisaroute
discontinuity(i.e.inthecaseofawaypointnotcontainedintheFMCNDB).Inadditionthecrewsshallnotedittheclearance."

Thereportingoperatorreceivedthefollowingemail3weeksafterthereportedevent:

OPEN

Subject:Florida8/9TailoredArrival
TheMIATailoredArrivalhasbeensuspendedduetothewaypointYOSSIbeingrecentlydeleted.NewYorkARTCCwasunaware
ofthisdeletionandhadbeenuplinkingTAclearancescontainingadiscontinuitytoaircraft.Theclearanceswererejectedper
operationaltrialpolicy:"AclearancethatincludesadiscontinuityisNOTacceptableandpilotsmustrejecttheTA".
TheMIATAisstillinoperationaltrialstatus,waitingforimplementation.WearecoordinatingaServiceLevelAgreementwith
TheOfficeofAdvancedConcepts&TechnologyDevelopmentandareworkingthedetailsoftheprogramtransfer.TheAir
TrafficandFlightStandardimplementationnoticesandassociatedchangestoFAAO7110.65,AeronauticalInformationManual
(AIM),andAeronauticalInformationPublication(AIP)areinthecoordinationprocess.

1185SN

NAT

CLOSED

B772appearstohavespotty
SATCOM,fallsbacktoHF

ThisaircraftinitiallycommunicatedwithBIRDviaVHFinSpitzbergen(Longyearbyen),switchingbetweenARINC(LYR)andSITA(LYR1).Itthen
Theairplaneinvolvedhadatemporaryproblemwithitssatcomsystem.Theproblemhasbeenresolved.
switchedtoARINC'sSATCOMservice(viaGESXXE).bythetimeofthefirstSATCOMreportanADSpositionreportwasoverduebyabouthalfan
hour,thiswasrequestedfromtheflight.
WhilethemissingADSreportwasneverreceived,theflightdidsenddownaCPDLCpositionreportandthenextADSreportviaHF.Afterthis
theflightalternatedbetweenSATCOMandHFwheretheperformencewassopoorthatthecontrollersometimesthoughthatcontacthad
beenlost.ArguablyeveryonewouldhavebeenbetteroffwithouttheHF"backup".

1186SN

SOPAC

CLOSEDAS
DUPLICATE

ThereasonforthisPRisthatwewouldliketoknowwhytheaircrafthadproblemscommunicatingviaSATCOMandraiseawarenessofthe
problemsassociatedwithHFwhenmessagedeliverytimesapproach(asinthiscase)20minutesinanenvironmentwhere,afterfiveminutes,
you are required to chase down missing position reports
B772CPDLCEstimateforNEXT CPDLCEstimateforNEXTsameastimeoverPREVIOUS.
ClosedasaduplicateofPR1132MM
sameastimeoverPREVIOUS
PositionReportcontainedthefollowinginformation:
CurrentPosition:2006S16259.4E
TimeatCurrentPosition:1500
LastSequencedWaypoint:BODEG
TimeoverLastSequencedWaypoint:1500
NextWaypoint:IKODA
ETAforNextWaypoint:1500
i.e.theestimateforNEXT(IKODA)wasthesameasthesequencedwaypoint(BODEG)of1500.

1187SN

NAT

CLOSED

FlightReportsReceivingCLX
Twice

Themessagewasdeliveredtotheairplanetwicebythenetwork.Thiscanhappenwhentheairplanereceivesanuplink,butthe
ATCReport:
y p
g
p
q
yq y g y
networkdoesn't"hear"theackfromtheairplane.Inthiscase,theuplinkwasattemptedonceoverLHR4,thentwiceover
p
,
p
p
,
Attime1134ClearanceDeliveryoperatoradvisedthataflightwasuponfrequencyqueryingwhyhehadreceived2clearancesviathedatalink.
The2clearanceswerethesameandoncheckingthehistorytherewasonly1CLXbut2CLA'sindicating2acceptancesoftheclearancebutthey stationMAN3,andthenoncemoreoverLHR4at11:30:35.TheACARSAckwasreceivedoverMAN3at11:30:37.Allparties
werethesame.
behaved"correctly",whichcansometimesresultinduplicatemessagedelivery.
SystemLogReview:
ThesystemcommslogsindicatetheclearancewasonlysentoncebySAATSviaOCL(ORCA)andthattwodownlinkCLA(acceptclearance)
messageswerereceived.Wehaveencounteredsimilarbeforewhentheaircrewhavehittheacceptbuttonmorethanonce.Thisdoesnot
disproveorotherwisethereportthattheaircrewstatedtheyreceivedtheclearancetwice.OnthisbasisthisPRisraisedwiththeNATDLMAto
attempttoestablishifmorethanoneclearancewasuplinked.

1188SN

SOPAC

ACTIVE

UM166+UM77combination
receivedbyA388

ACPDLCreroutewasuplinkedbyNFFFtoanaircraftattherequestofYBBB.

Airbusinvestigationinprogress.

Theuplink,sentat1655,containedthefollowingmessageelements:
UM166DUETOTRAFFIC
UM77AT20S166EPROCEEDDIRECTTO30S156E
Shortlyafteruplinkingthisclearance,aWILCOdownlinkresponsewasreceived,indicatingtheyhadacceptedtheclearance.
However,theflightcrewbegantrackingdirecttoposition30S156E,bypassing20S166Eascleared.
WhenlaterdescribingthereceiptoftheCPDLCclearance,theflightcrewindicatedthattheyhadinterpretedtheclearanceasbeingdirectto
30S156E.ThedescriptionprovidedverballybytheflightcrewappearedtoindicatethatnoLOADprompthadbeenpresentedinassociation
withtheuplinkedclearance,creatingtheneedtoinputtheclearancemanually.
DoesthisuplinkmessageelementcombinationreceivedbytheA380requiremanualinteractiontoloadbytheflightcrew?
1189SN

SOPAC

ACTIVE

UnnotifiedCSPoutage

NooutagereportwasreceivedfromARINCviathenormalemailreportingchannel.OutagewasdetectedatNZZOoperationalcontroller
positionswhichinitiatedfollowupactionwithARINC.

OnSeptember14,ARINCexperiencedapoweroutageduringaplannedUPSmaintenance.Ourglobalnetworkprocessor
recoveredquicklyandaircraftcommunicationwasreestablishedwithinashortperiodoftime.Duetothenatureofthepower
outageadditionalcheckswerealsomadeontheapplicationserversinthesecondarysystembeforeallapplicationswere
recovered.Weregretthatthisrecoveryimpactedyouandyourservices.

I'veinitiatedfollowupwithARINCtodetermine1.ActualOutageDuration2.Cause3.Reasonfornonotification.

AwaitingconfirmationfromoriginatorthatthisPRcanbeclosed.

CSPoutage(ARINC)between14/051514/1000thatwasapparentlyduetoapoweroutageintheARINCnetwork.

11

CRA
number

Region Status

Title

Description

Findings

1190SN

SOPAC

airplaneunabletologonto
YBBB

AnaircraftwasunabletologontoYBBB.CoordinationwithKZAKindicatedthattheaircrafthadnotsuccessfullyloggedontothemeither.

Closedasaduplicateof1112.

CLOSEDAS
DUPLICATE

Anecdotalevidenceindicatesthattherewereproblemswiththisairframeseveraldaysearlier(11/91720)

1191SN

NOPAC

ACTIVE

1192SN

SOPAC

ACTIVE

FANSPROBLEMREPORTOFNO FMCMESSAGE"ATCCOMTERMINATED",UnabletologontoKZAKorRJJJ.
SITAareinvestigatingwiththeoperator.Thiswasarecentlydeliverednewairplaneandmaynothavehaditssatcomsystem
properlyconfigured.
LOGON
OffTrackDeviationinCPDLC CPDLCPositionReportfromaC17onenteringAGGGFIR(activecentreYBBB)containedappendedtextDEVIATING128NMRIGHTOFROUTE. AssignedtoUSAFforinvestigation.
PositionReportfromC17
Theaircraftwasnotconductingaweatherdeviation,andwereunabletoexplaintheoriginoftheappendedtextintheCPDLCPositionReport.
AsubsequentCPDLCPositionReportwithNZZO(somewherecloserto2100)reportedlycontainednosuchanomaly.

1193SN

SOPAC

CLOSEDAS
DUPLICATE

Failedtransfer

TRANSFERFAILED.NEXT
CENTERYBBBBUTNOADSC
CONTRACTESTABLISHED.
MANUALLOGONOK.

ClosedasaduplicateofPR1195SN.

1194SN

SOPAC

ACTIVE

KLAXTailoredArrivalTrial

InearlySeptember,TailoredArrivalrequestsmadebyCPDLCbeganbeingdenied.CommunicationwithOaklandCenterindicatedthatSOCAL
TRACONandconsequentlyL.A.CenterarenolongersupportingT.As.Therewasnoconsultation,ornotificationbywayofaNOTAMtousers.

AssignedtotheFAAforinvestigation.

1195SN

SOPAC

ACTIVE

NoAddressforwardingfrom
WAAF

Forseveraldays,latelogons(i.e.astheaircraftapproachestheYBBBFIRboundary)havebeenreceivedforaircraftsouthboundfromWAAF.
Normallytheselogonsarereceived~30minutespriortotheFIRboundaryasaresultofWAAFAddressForwardingtheaircrafttoYBBB.

CRAinvestigationinprogress.

InitialinvestigationbyCRAinresponsetoanairlinereportindicatesthatnoFN_CADmessagewassentbyWAAF.Thismatcheswhatweare
seeingoperationallyitisexpectedthatthelatelogonsareflightcrewsmanuallyloggingontoYBBB.
TherewasanATCgroundsystemdataupgradeinWAAFlastweekthiscouldbethecauseoftheproblem.

12