Air carrier on oceanic route is 'lost' due to no handoff to next facility.

Attributes
ACN	199327
Time
Date	199201
Day	Sat
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : zny
State Reference	NY
Altitude	msl bound lower : 33000 msl bound upper : 37000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zny
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 3 Turbojet Eng
Flight Phase	cruise other
Route In Use	enroute airway : r759
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time total : 14000
ASRS Report	199327
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : commercial pilot : instrument
Events
Anomaly	non adherence : far other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Inter Facility Coordination Failure other
Situations
ATC Facility	procedure or policy : unspecified

Narrative:

Cleared bwi-sju AR8 bacus R759 elmuc inham route 6 sju. Approaching bacus, ZDC advised 'radar contact lost, report bacus this frequency.' we reported bacus at FL330 with a tallo estimate and requested FL370. We were given 'cross tallo at FL370, depart FL330 passing south of 30N, report tallo to ny.' we crossed tallo at FL370 on time and attempted to call ny on 88.46/113.96. Could read, could not transmit. Relayed report through communication flight on VHF and heard ny ask 'confirm flight number' and 'we have no record of the flight.' in a few mins we were able to talk to ny on HF and they said again they had no record of our flight and implied/asked if we had flown all the way to tallo with no radio contact. We insisted that we did a cellcall check prior to iad departure (routing IAP, bwi, sju) and had reported bacus to ZDC and complied with washington restriction to report tallo to ny. There was no restriction to call ny prior to tallo. Anyway, it appears that washington did not pass us off to ny. This event was discussed with company dispatch department and debriefed. We are still not sure if we failed to do something we were supposed to or if the handoff was screwed up.

Original NASA ASRS Text

Title: ACR ON OCEANIC RTE IS 'LOST' DUE TO NO HDOF TO NEXT FACILITY.

Narrative: CLRED BWI-SJU AR8 BACUS R759 ELMUC INHAM RTE 6 SJU. APCHING BACUS, ZDC ADVISED 'RADAR CONTACT LOST, RPT BACUS THIS FREQ.' WE RPTED BACUS AT FL330 WITH A TALLO ESTIMATE AND REQUESTED FL370. WE WERE GIVEN 'CROSS TALLO AT FL370, DEPART FL330 PASSING S OF 30N, RPT TALLO TO NY.' WE CROSSED TALLO AT FL370 ON TIME AND ATTEMPTED TO CALL NY ON 88.46/113.96. COULD READ, COULD NOT XMIT. RELAYED RPT THROUGH COM FLT ON VHF AND HEARD NY ASK 'CONFIRM FLT NUMBER' AND 'WE HAVE NO RECORD OF THE FLT.' IN A FEW MINS WE WERE ABLE TO TALK TO NY ON HF AND THEY SAID AGAIN THEY HAD NO RECORD OF OUR FLT AND IMPLIED/ASKED IF WE HAD FLOWN ALL THE WAY TO TALLO WITH NO RADIO CONTACT. WE INSISTED THAT WE DID A CELLCALL CHK PRIOR TO IAD DEP (RTING IAP, BWI, SJU) AND HAD RPTED BACUS TO ZDC AND COMPLIED WITH WASHINGTON RESTRICTION TO RPT TALLO TO NY. THERE WAS NO RESTRICTION TO CALL NY PRIOR TO TALLO. ANYWAY, IT APPEARS THAT WASHINGTON DID NOT PASS US OFF TO NY. THIS EVENT WAS DISCUSSED WITH COMPANY DISPATCH DEPT AND DEBRIEFED. WE ARE STILL NOT SURE IF WE FAILED TO DO SOMETHING WE WERE SUPPOSED TO OR IF THE HDOF WAS SCREWED UP.

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.