ZLC controller reports of a change to an altitude in the scratch pad area of a data tag that was cha...

Narrative:

Aircraft X was flashed to R30 from boi approach nearly 20 minutes from the boundary with 120 in the altitude section of the flight plan. About 13 minutes later; the handoff was retracted then reattempted with 100 now in the data block. No call was attempted to coordinate this change of altitude by boi approach. I saved the controller from a deviation by affecting communication. The boi approach airspace test is a failure. It must be ended now. It is a daily occurrence to have amended altitudes not coordinated because of the 'flash as soon as they're on radar; sometimes before' mentality that has been adopted by boi approach. In addition to the 'flash first; do no coordination later' mantra that is repeated endlessly within the building that houses boi approach; there is no respect for the 7110.65 in transferring communications as soon as possible after a handoff. This sort of disregard of rules and safety are incessant when it comes to boi approach and something must be done about this test that is showing a blatant disregard for safety.I submitted a previous reports about an aircraft climbing to the wrong altitude and may have mixed up the times it happened.

Original NASA ASRS Text

Title: ZLC Controller reports of a change to an altitude in the scratch pad area of a data tag that was changed but never coordinated. Controller reports that the BOI Approach airspace is a failure due to things not being coordinated and BOI Approach not having respect for the 7100.65.

Narrative: Aircraft X was flashed to R30 from BOI Approach nearly 20 minutes from the boundary with 120 in the altitude section of the flight plan. About 13 minutes later; the handoff was retracted then reattempted with 100 now in the data block. No call was attempted to coordinate this change of altitude by BOI Approach. I saved the controller from a deviation by affecting communication. The BOI Approach airspace test is a failure. It must be ended now. It is a daily occurrence to have amended altitudes not coordinated because of the 'flash as soon as they're on radar; sometimes before' mentality that has been adopted by BOI Approach. In addition to the 'flash first; do no coordination later' mantra that is repeated endlessly within the building that houses BOI Approach; there is no respect for the 7110.65 in transferring communications as soon as possible after a handoff. This sort of disregard of rules and safety are incessant when it comes to BOI Approach and something must be done about this test that is showing a blatant disregard for safety.I submitted a previous reports about an aircraft climbing to the wrong altitude and may have mixed up the times it happened.

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	1262678
Time
Date	201505
Local Time Of Day	1201-1800
Place
Locale Reference	ZLC.ARTCC
State Reference	UT
Environment
Light	Daylight
Aircraft 1
Make Model Name	M-20 Series Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 3.5
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy

ZLC controller reports of a change to an altitude in the scratch pad area of a data tag that was changed but never coordinated. Controller reports that the boi approach airspace is a failure due to things not being coordinated and boi approach not having respect for the 7100.65.