Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 3.5
Communication Breakdown; Confusion; Distraction; Situational Awareness
ATC Issue All Types; Airspace Violation All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Separated Traffic
Human Factors; Procedure
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.
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.