ZSU ARTCC controllers report about an aircraft that was not at the correct altitude when handed off ...

Narrative:

I was training a new flm on D2. There was training on the r-side as well. By the time we got the position; aircraft X was at FL340 and coordinated at FL360. The briefing we received included this information. Apparently the radar guys knew about this because the strip was flat on the bay. We kept working; and minutes later ZNY called us asking at what altitude was the traffic coordinated. By that time the strip was not in the bay because the traffic had progressed the fix already. The developmental did not remember the altitude and did not see the traffic progressing the fix either; so he told ZNY FL340 because he saw the limited data block at FL340 north of the fix. At that time; was when I knew that something was wrong and asked the flm for the strips to verify the altitude coordinated. We confirmed FL360 coordinated and that the radar guy did not assigned the altitude. There are always a lot of altitudes changes; every time we take a d-side position; even though the coordination was not made by us; and the radar guy has the information; every new d-side should confirm with the radar guy that he/she know about the altitudes changes. This could help the radar guy as a reminder as well; just in case he/she has been busy and forgetting something.

Original NASA ASRS Text

Title: ZSU ARTCC controllers report about an aircraft that was not at the correct altitude when handed off from originating Center to Oceanic Center causing confusion at Oceanic Center.

Narrative: I was training a new FLM on D2. There was training on the R-side as well. By the time we got the position; Aircraft X was at FL340 and coordinated at FL360. The briefing we received included this information. Apparently the Radar guys knew about this because the strip was flat on the bay. We kept working; and minutes later ZNY called us asking at what altitude was the traffic coordinated. By that time the strip was not in the bay because the traffic had progressed the fix already. The developmental did not remember the altitude and did not see the traffic progressing the fix either; so he told ZNY FL340 because he saw the limited data block at FL340 north of the fix. At that time; was when I knew that something was wrong and asked the FLM for the strips to verify the altitude coordinated. We confirmed FL360 coordinated and that the Radar guy did not assigned the altitude. There are always a lot of altitudes changes; every time we take a D-side position; even though the coordination was not made by us; and the Radar guy has the information; every new D-side should confirm with the Radar guy that he/she know about the altitudes changes. This could help the Radar guy as a reminder as well; just in case he/she has been busy and forgetting something.

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	1166808
Time
Date	201404
Local Time Of Day	1201-1800
Place
Locale Reference	ZSU.ARTCC
State Reference	PR
Environment
Light	Daylight
Aircraft 1
Make Model Name	Medium Large Transport
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Handoff / Assist Instructor Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 13
Person 2
Function	Enroute Instructor
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 7
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy

ZSU ARTCC controllers report about an aircraft that was not at the correct altitude when handed off from originating center to oceanic center causing confusion at oceanic center.