Narrative:

ZNY-34 flashed me a data block on aircraft X that showed no aircraft type; or any flight plan information; just a target descending to FL250. I was busy with multiple sectors; and numerous aircraft. I did not have a d-side to handle any coordination for me. I assumed ZNY had an utm [unsuccessful transmission message] on this aircraft; as it is uncommon to have an aircraft flash without flight plan information; without any utm; etc. I called the controller at ZNY-34 and advised I had no flight plan information on the data block aircraft X; and asked if he had a utm or any fails. He said no. I questioned this; as I was surprised and he said; 'no; so do you want to write it?' I said standby; as the aircraft was still several minutes from my sector. I went back to a few other aircraft; then I got back on the line with ZNY-34 and said; 'go ahead; I'll write it;' and he said; 'you know what; I don't like your attitude I'm gonna spin him.' at this point the ZNY controller entered my airspace with aircraft X without coordination; turned him around in a 360 turn; then entered my airspace again after descending the aircraft to FL200; violating my airspace a second time. He refused to answer any landlines; and my supervisor tried calling his area several times and their supervisor would not answer the phone. The controller at ZNY-34's unwillingness to communicate; and provide manual coordination led to the aircraft getting delayed; and him violating my airspace twice.I recommend ZNY controllers be responsible for ensuring flight plan information passes to ZBW in a timely manner.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZBW controller describes scenario where he doesn't have complete track data or a flight plan on an aircraft. He requests information from the Controller working the aircraft who refuses to pass the information to him and violates the airspace twice with the aircraft.

Narrative: ZNY-34 flashed me a data block on Aircraft X that showed no aircraft type; or any flight plan information; just a target descending to FL250. I was busy with multiple sectors; and numerous aircraft. I did not have a D-side to handle any coordination for me. I assumed ZNY had an UTM [Unsuccessful Transmission Message] on this aircraft; as it is uncommon to have an aircraft flash without flight plan information; without any UTM; etc. I called the Controller at ZNY-34 and advised I had no flight plan information on the data block Aircraft X; and asked if he had a UTM or any fails. He said no. I questioned this; as I was surprised and he said; 'No; so do you want to write it?' I said standby; as the aircraft was still several minutes from my sector. I went back to a few other aircraft; then I got back on the line with ZNY-34 and said; 'Go ahead; I'll write it;' and he said; 'You know what; I don't like your attitude I'm gonna spin him.' At this point the ZNY Controller entered my airspace with Aircraft X without coordination; turned him around in a 360 turn; then entered my airspace again after descending the aircraft to FL200; violating my airspace a second time. He refused to answer any landlines; and my Supervisor tried calling his area several times and their Supervisor would not answer the phone. The Controller at ZNY-34's unwillingness to communicate; and provide manual coordination led to the aircraft getting delayed; and him violating my airspace twice.I recommend ZNY controllers be responsible for ensuring flight plan information passes to ZBW in a timely manner.

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.