Center controller reported an aircraft was late in reporting position and could not be contacted. Th...

Narrative:

I received a coordination message from [an adjacent center] for aircraft X at FL290. Later I received an air to ground message that the aircraft was 'leaving' FL270 for FL200. The aircraft was still in [the adjacent center's] airspace and I was not in communication with the flight; but I was expecting a re-coordination from the sector or that it was a possible typo. This message comes into our error queue and when the aircraft is outside our airspace we don't process those messages. Aircraft X crosses into [our] flight information region (fir) and fails to make his position report within the allotted 10 minutes. I sent a request to [oceanic] to contact the aircraft as he was HF equipped only to make a position report. While I was waiting for [oceanic] to come back with a report; [the adjacent center] advised that they were not in contact with the flight and didn't have a position report either. When [oceanic] managed to contact the aircraft he reported that he was in fact at FL200; that he was down to one engine and couldn't maintain any higher altitude. I verified that he was [requesting priority handling] and got the requisite information and passed it to the supervisor. The aircraft had elected to continue on to his original destination. He was still over an hour away from the airport when I was relieved of duty.

Original NASA ASRS Text

Title: Center Controller reported an aircraft was late in reporting position and could not be contacted. The aircraft was eventually contacted and confirmed to be at a lower altitude due to an engine failure.

Narrative: I received a coordination message from [an adjacent center] for Aircraft X at FL290. Later I received an air to ground message that the aircraft was 'leaving' FL270 for FL200. The aircraft was still in [the adjacent center's] airspace and I was not in communication with the flight; but I was expecting a re-coordination from the sector or that it was a possible typo. This message comes into our error queue and when the aircraft is outside our airspace we don't process those messages. Aircraft X crosses into [our] Flight Information Region (FIR) and fails to make his position report within the allotted 10 minutes. I sent a request to [oceanic] to contact the aircraft as he was HF equipped only to make a position report. While I was waiting for [oceanic] to come back with a report; [the adjacent center] advised that they were not in contact with the flight and didn't have a position report either. When [oceanic] managed to contact the aircraft he reported that he was in fact at FL200; that he was down to one engine and couldn't maintain any higher altitude. I verified that he was [requesting priority handling] and got the requisite information and passed it to the Supervisor. The aircraft had elected to continue on to his original destination. He was still over an hour away from the airport when I was relieved of duty.

Data retrieved from NASA's ASRS site 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.

Attributes
ACN	1483013
Time
Date	201709
Local Time Of Day	0001-0600
Place
Locale Reference	ZZZ.ARTCC
State Reference	US
Aircraft 1
Make Model Name	Super King Air 350
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 6
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Critical Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance

Center controller reported an aircraft was late in reporting position and could not be contacted. The aircraft was eventually contacted and confirmed to be at a lower altitude due to an engine failure.