ZAU controller reported receiving a point out that was not coordinated according to procedures. Cont...

Narrative:

Aircraft X departed ZZZ for jfk. Weather stretching from east of departure airport to the east/northeast forced the aircraft north a bit. The data block appeared; with I32 initiating a point out to us. The flight plan said kzzz.weldo.djb; and there was an interim altitude 130 in the data block. My trainee accepted the automated point out. I explained how that was most likely an error; as I was confident ZID would climb the aircraft. Before the aircraft reached weldo; the interim 130 was amended to FL230. There was no coordination from ZID as the aircraft climbed through our airspace. There were no fourth line data as the aircraft turned left; further into our airspace. [It read] 'ph' [present heading] in the fourth line as the aircraft took a course towards fwa. We made a point out to olk [sector] making sure they were aware of the aircraft; then [it read] '080' in the heading section of the 4th line; while the aircraft was still climbing through our airspace.the unsafe automated point out procedure needs to be suspended until adequate training is developed and accomplished. We should have called ZID and worked the aircraft. The aircraft never entered the sector's airspace that was misapplying the unsafe automated point out procedure.

Original NASA ASRS Text

Title: ZAU Controller reported receiving a point out that was not coordinated according to procedures. Controller reported the automated point out procedure currently practiced is unsafe.

Narrative: Aircraft X departed ZZZ for JFK. Weather stretching from east of departure airport to the east/northeast forced the aircraft north a bit. The data block appeared; with I32 initiating a point out to us. The flight plan said KZZZ.WELDO.DJB; and there was an interim altitude 130 in the data block. My trainee accepted the automated point out. I explained how that was most likely an error; as I was confident ZID would climb the aircraft. Before the aircraft reached WELDO; the interim 130 was amended to FL230. There was no coordination from ZID as the aircraft climbed through our airspace. There were no fourth line data as the aircraft turned left; further into our airspace. [It read] 'PH' [present heading] in the fourth line as the aircraft took a course towards FWA. We made a point out to OLK [sector] making sure they were aware of the aircraft; then [it read] '080' in the heading section of the 4th line; while the aircraft was still climbing through our airspace.The unsafe automated point out procedure needs to be suspended until adequate training is developed and accomplished. We should have called ZID and worked the aircraft. The aircraft never entered the sector's airspace that was misapplying the unsafe automated point out procedure.

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	1544491
Time
Date	201805
Local Time Of Day	1201-1800
Place
Locale Reference	ZAU.ARTCC
State Reference	IL
Aircraft 1
Make Model Name	Regional Jet 900 (CRJ900)
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

ZAU controller reported receiving a point out that was not coordinated according to procedures. Controller reported the automated point out procedure currently practiced is unsafe.