Narrative:

Experienced an event on sector 16 that perfectly illustrates the east specialty's variety of attitudes toward positive coordination of altitude. I experienced a sequence of events that was very frustrating based on long history and experience with the east.first; north of the ZZZ area; I noticed aircraft X handing off to me from within sector 70s airspace with FL270 hard displaying in the data block. After some time; it appears they decided to verbally coordinate this with my d-side; so I took the handoff and moved on.then; east of ZZZ1; aircraft Y began flashing to me with FL280 showing in the data block while he was still descending from the 30's. No coordination was made; I'm sick of getting in to pissing matches with the east over this; so I just took the handoff and inserted a temp 290 altitude until he checked in and I issued FL280 (he came over only descending to FL290).then the 3rd issue occurred very shortly thereafter; and was the one that finally caused me to file this report. North of ZZZ2 VOR; aircraft Z began handing off to me with FL280 in the data block while he was at FL300. He was 'over' sector 15's airspace at the time; so I assumed that FL280 was the altitude he was descending to. He checked in level at FL290; not descending to FL280 as I had assumed.I reported the situations to my [supervisor].this is a constant; continual problem with the east. It has been going on for literally years and years; as they have their own concept about how air traffic operates. They lack professionalism to the core and do not appear able to comprehend the english language as organized and published in the 7110.65 and 7110.149. They do not modify their behavior based on concrete evidence and clearly published rules; and no one cares enough or are able to motivate them to change their behavior. There is no accountability. It will cause an issue some day because they will just assume another controller knew what they would do. They'll [expletive] about someone else applying a valid procedure; showing they know full-well what the procedure is; and then turn around and fail to execute the same because they feel like their piss poor interpretation of the rules is somehow valid (and I assert they do this knowingly and willfully).I assert that the number of reports of this matter is far below the actual frequency of occurrence; for a variety of reasons. I've tried to report in the past on this issue and nothing happens. I see instances fairly regularly when I work traffic and just don't feel motivated to file anymore. Then; you have to assume that someone receiving poor data block coordination cares enough to report it in the first place; and I know for a fact most of the controllers don't actually care enough to file. They'll [expletive]; sure; it's always fun to dog pile on the east; but to actually try and do something about it happens rarely.lastly; and the icing on the cake for this situation; and just proof of the east's general unprofessionalism; northeast of ZZZ2 VOR; aircraft a at FL300 apparently flashes to me; well outside my airspace (40-50 miles; beyond my range). I receive a phone call from 15; first asking for me by name; then telling me that aircraft a is descending to FL260. I didn't know who the aircraft was; I thought possibly he was coming from a high sector above me; so I'm scrambling to pull him up. He tells me he just wanted to make sure there wasn't any 'confusion.' I had typed the cid (computer identification) to try and pull the aircraft up; unknowingly taking the handoff. It wasn't until after I expanded out that I saw the aircraft being reference and I saw I had taken the handoff.I know that I catch crap at this facility from people that see me as just trying to follow the book and be correct about working traffic. I get that I'm the safety rep; and my reputation is that of following the book; apparently to a fault. I let a lot of [expletive] pass; if only because continually [expletive] basically changes nothing at this facility. But the automated coordination of altitude data in data blocks is not something I can stay quiet on. But nothing changes; and I expect fully that I will be pissing in to the wind with this report as well. When I leave this facility; at least I can say I tried to get things fixed.I'm just sick of it; and the lack of change at this facility is a major motivation toward my desire to leave permanently.I reported this to my qc manager directly as well.actually identify on an individual basis the controllers in the east who continually; willfully; and without consequence or accountability clearly violate written procedure that has been clarified and explained to them numerous times and ignored time and time again. Nothing will change though. I'm done.

Related reports:

Google
 

Original NASA ASRS Text

Title: ARTCC Controller reported individuals in certain areas of the sector do not follow procedures correctly. This behavior has reportedly led to confusion and airspace violations.

Narrative: Experienced an event on Sector 16 that perfectly illustrates the East Specialty's variety of attitudes toward positive coordination of altitude. I experienced a sequence of events that was very frustrating based on long history and experience with the East.First; north of the ZZZ area; I noticed Aircraft X handing off to me from within Sector 70s airspace with FL270 hard displaying in the data block. After some time; it appears they decided to verbally coordinate this with my D-Side; so I took the handoff and moved on.Then; east of ZZZ1; Aircraft Y began flashing to me with FL280 showing in the data block while he was still descending from the 30's. No coordination was made; I'm sick of getting in to pissing matches with the East over this; so I just took the handoff and inserted a temp 290 altitude until he checked in and I issued FL280 (he came over only descending to FL290).Then the 3rd issue occurred very shortly thereafter; and was the one that finally caused me to file this report. North of ZZZ2 VOR; Aircraft Z began handing off to me with FL280 in the data block while he was at FL300. He was 'over' sector 15's airspace at the time; so I assumed that FL280 was the altitude he was descending to. He checked in level at FL290; not descending to FL280 as I had assumed.I reported the situations to my [supervisor].This is a constant; continual problem with the East. It has been going on for literally years and years; as they have their own concept about how air traffic operates. They lack professionalism to the core and do not appear able to comprehend the English language as organized and published in the 7110.65 and 7110.149. They do not modify their behavior based on concrete evidence and clearly published rules; and no one cares enough or are able to motivate them to change their behavior. There is no accountability. It will cause an issue some day because they will just assume another controller knew what they would do. They'll [expletive] about someone else applying a valid procedure; showing they know full-well what the procedure is; and then turn around and fail to execute the same because they feel like their piss poor interpretation of the rules is somehow valid (and I assert they do this knowingly and willfully).I assert that the number of reports of this matter is far below the actual frequency of occurrence; for a variety of reasons. I've tried to report in the past on this issue and nothing happens. I see instances fairly regularly when I work traffic and just don't feel motivated to file anymore. Then; you have to assume that someone receiving poor data block coordination cares enough to report it in the first place; and I know for a fact most of the controllers don't actually care enough to file. They'll [expletive]; sure; it's always fun to dog pile on the east; but to actually try and do something about it happens rarely.Lastly; and the icing on the cake for this situation; and just proof of the East's general unprofessionalism; NE of ZZZ2 VOR; Aircraft A at FL300 apparently flashes to me; well outside my airspace (40-50 miles; beyond my range). I receive a phone call from 15; first asking for me by name; then telling me that Aircraft A is descending to FL260. I didn't know who the aircraft was; I thought possibly he was coming from a high sector above me; so I'm scrambling to pull him up. He tells me he just wanted to make sure there wasn't any 'confusion.' I had typed the CID (Computer Identification) to try and pull the aircraft up; unknowingly taking the handoff. It wasn't until after I expanded out that I saw the aircraft being reference and I saw I had taken the handoff.I know that I catch crap at this facility from people that see me as just trying to follow the book and be correct about working traffic. I get that I'm the Safety Rep; and my reputation is that of following the book; apparently to a fault. I let a lot of [expletive] pass; if only because continually [expletive] basically changes nothing at this facility. But the automated coordination of altitude data in data blocks is not something I can stay quiet on. But nothing changes; and I expect fully that I will be pissing in to the wind with This report as well. When I leave this facility; at least I can say I tried to get things fixed.I'm just sick of it; and the lack of change at this facility is a major motivation toward my desire to leave permanently.I reported this to my QC manager directly as well.Actually identify on an individual basis the controllers in the East who continually; willfully; and without consequence or accountability clearly violate written procedure that has been clarified and explained to them numerous times and ignored time and time again. Nothing will change though. I'm done.

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.