Narrative:

For this event; there were two separate jump aircraft. Aircraft X with 9 jumpers and aircraft Y with 1 jumper. Poc tower did not receive any calls or advisories from TRACON for either jump. The poc local controller kept aircraft out of the path of both jumps. The way that we knew the first jump occurred was from the information provided by the pilot earlier in the week. I was given a briefing item with the proposed jump times. I noticed the time; and thought it was odd that we had not received any notification from TRACON. Local control looked out the window and observed the jumpers had already left the aircraft. Local control attempted to call TRACON on the direct line; 'jumpers away' but got no answer.for the second jump; TRACON had vectored aircraft Z inbound on a VFR practice VOR approach and switched the aircraft to local control. The pilot of the second jump aircraft called the tower controller on the frequency and advised local control that the jumper was away. Local control had to break aircraft Z off the approach and give the pilot instructions to keep them out of the path of the jump. Had aircraft Z continued the VOR approach as cleared; they would have flown through the path of the second jump while they were descending to the landing zone.coordination between sct and poc should have been conducted per 7110.65 9-7-1. When I realized aircraft Z was inbound on the VOR approach I should have advised TRACON that I could not accept the aircraft at this time due to parachute activities.I as the front line manager should have advised sct operations manager that the first coordination was not accomplished. That may have led the TRACON controller to coordinate the second jump and not to have vectored aircraft Z inbound while parachute operations were in effect.

Related reports:

Google
 

Original NASA ASRS Text

Title: TRACON Controller working parachute jump aircraft did not coordinate the Jumpers leaving the aircraft with the Tower. Reportedly; the jumper's area is in confliction with the VOR Approach. The Tower Controller had to break the aircraft off their approach to resolve a conflict.

Narrative: For this event; there were two separate Jump Aircraft. Aircraft X with 9 jumpers and Aircraft Y with 1 jumper. POC tower did not receive any calls or advisories from TRACON for either jump. The POC Local Controller kept aircraft out of the path of both jumps. The way that we knew the first jump occurred was from the information provided by the pilot earlier in the week. I was given a briefing item with the proposed jump times. I noticed the time; and thought it was odd that we had not received any notification from TRACON. Local Control looked out the window and observed the jumpers had already left the aircraft. Local Control attempted to call TRACON on the direct line; 'jumpers away' but got no answer.For the second jump; TRACON had vectored Aircraft Z inbound on a VFR Practice VOR approach and switched the aircraft to Local Control. The pilot of the second jump aircraft called the tower controller on the frequency and advised Local Control that the jumper was away. Local Control had to break Aircraft Z off the approach and give the pilot instructions to keep them out of the path of the jump. Had Aircraft Z continued the VOR approach as cleared; they would have flown through the path of the second jump while they were descending to the landing zone.Coordination between SCT and POC should have been conducted per 7110.65 9-7-1. When I realized Aircraft Z was inbound on the VOR approach I should have advised TRACON that I could not accept the aircraft at this time due to Parachute activities.I as the Front Line Manager should have advised SCT Operations Manager that the first coordination was not accomplished. That may have led the TRACON controller to coordinate the second jump and not to have vectored Aircraft Z inbound while Parachute operations were in effect.

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.