Narrative:

Sector 17 began handing off aircraft Y at 27000 feet. I noticed an enhanced limited data block within sector 28 low beneath sector 17; aircraft X. I brought up the full data block and noticed it may hinder the ability of the arriving flight to descend; so I requested sector 17 to shortcut aircraft Y to zzzzz intersection before accepting the handoff to allow sector 17 to safely climb aircraft X. I descended aircraft Y to 24000 feet as I am allowed to do by SOP. Aircraft X was handed off to sector 17 climbing to 23000 feet. Sector 17 gave a climb to this aircraft X to an altitude above my airspace. Aircraft X came within 2.5 miles of my airspace at 26000 feet and was finally through my airspace approximately 10 miles in. No one called me with a point out for aircraft X climbing through my airspace.it's me once again with yet another airspace violation from the central area at ZJX. I just sent one in on that area from [three days prior] and elaborated on how this area has become inherently unsafe. I am going to fill out an atsap for every single one that affects the sector that I am working from this point forward. I understand us controllers are human and make mistakes. We all get in a bind from time to time and need an 'out' from fellow controllers. I have no issue on that. The issue is with many controllers completely disobeying our basic ways to move traffic safely and efficiently through the NAS. The basic ways are point outs; apreq's; etc. I'm actually very unhappy with how this has progressed in the time I have been hired by the FAA and at ZJX. I look forward to hearing from you and what steps are going to be taken for people to be accountable for not doing their job correctly and safely.

Related reports:

Google
 

Original NASA ASRS Text

Title: An aircraft was climbed through a Controller's sector without a handoff or point out.

Narrative: Sector 17 began handing off Aircraft Y at 27000 feet. I noticed an enhanced limited data block within sector 28 Low beneath sector 17; Aircraft X. I brought up the full data block and noticed it may hinder the ability of the arriving flight to descend; so I requested sector 17 to shortcut Aircraft Y to ZZZZZ intersection before accepting the handoff to allow sector 17 to safely climb Aircraft X. I descended Aircraft Y to 24000 feet as I am allowed to do by SOP. Aircraft X was handed off to sector 17 climbing to 23000 feet. Sector 17 gave a climb to this Aircraft X to an altitude above my airspace. Aircraft X came within 2.5 miles of my airspace at 26000 feet and was finally through my airspace approximately 10 miles in. No one called me with a point out for Aircraft X climbing through my airspace.It's me once again with yet another airspace violation from the Central Area at ZJX. I just sent one in on that area from [three days prior] and elaborated on how this Area has become inherently unsafe. I am going to fill out an ATSAP for every single one that affects the sector that I am working from this point forward. I understand us controllers are human and make mistakes. We all get in a bind from time to time and need an 'out' from fellow controllers. I have no issue on that. The issue is with many controllers completely disobeying our basic ways to move traffic safely and efficiently through the NAS. The basic ways are Point outs; APREQ's; etc. I'm actually very unhappy with how this has progressed in the time I have been hired by the FAA and at ZJX. I look forward to hearing from you and what steps are going to be taken for people to be accountable for not doing their job correctly and safely.

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.