Narrative:

The tower supervisor coordinated with S56 a specific plan to handle a parachute operation that was in progress east of slc. The tracon was supposed to let us know when the jumpers were 2 to 3 minutes from jumping. At that point the tracon was going to hold all VFR aircraft out that would cause a problem for the jumpers until we called them and reported that the jumpers were on the ground. The first time the jump aircraft called jumpers away the tracon had already gave us a VFR aircraft after the fact; but we were able to call off the jump until that VFR aircraft landed. The next time the jump aircraft reported jumpers away the jumpers did jump this time. The jump aircraft exited the bravo airspace and told the tracon controller that the jumpers were down and clear; but we were informed that the pilot was not in communication with the jumpers so there was know way for him to know they were all on the ground. We had already coordinated that we would tell the tracon when they could start sending VFR back into the airspace; but that didn't happen. The tracon just took the jump report from the pilot and resumed normal ops. The tracon controller started to let the VFR aircraft(s) back into bravo again; thinking the jumpers were down; but the tower could still see one parachute still in the air. We tried to get the tracon to hold the VFR aircraft(s) out; but we ended up having to move the VFR's out of the way on our own until we observed all the jumpers were down. The jump pilot obviously assumed the jumpers were down; but that wasn't the case.we have these parachute jumps every year and they never go as planned. They are always planned at very busy times and very close to the airport. I don't think it is a safe operation and I think it should not be allowed to do any more.

Google
 

Original NASA ASRS Text

Title: SLC Controller reports of miscommunication between TRACON and Tower reference jumpers being on the ground and allowing aircraft in close proximity.

Narrative: The tower supervisor coordinated with S56 a specific plan to handle a parachute operation that was in progress east of SLC. The Tracon was supposed to let us know when the Jumpers were 2 to 3 minutes from jumping. At that point the Tracon was going to hold all VFR aircraft out that would cause a problem for the jumpers until we called them and reported that the jumpers were on the ground. The first time the jump aircraft called jumpers away the Tracon had already gave us a VFR aircraft after the fact; but we were able to call off the jump until that VFR aircraft landed. The next time the Jump aircraft reported jumpers away the jumpers did jump this time. The jump aircraft exited the Bravo airspace and told the Tracon controller that the jumpers were down and clear; but we were informed that the pilot was not in communication with the jumpers so there was know way for him to know they were all on the ground. We had already coordinated that we would tell the Tracon when they could start sending VFR back into the airspace; but that didn't happen. The Tracon just took the jump report from the pilot and resumed normal ops. The Tracon controller started to let the VFR aircraft(s) back into Bravo again; thinking the jumpers were down; but the tower could still see one parachute still in the air. We tried to get the Tracon to hold the VFR aircraft(s) out; but we ended up having to move the VFR's out of the way on our own until we observed all the jumpers were down. The jump pilot obviously assumed the jumpers were down; but that wasn't the case.We have these parachute jumps every year and they never go as planned. They are always planned at very busy times and very close to the airport. I don't think it is a safe operation and I think it should not be allowed to do any more.

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.