Phl local controller reported a loss of separation when a helicopter passed under an aircraft transp...

Narrative:

Aircraft Z; was orbiting [nearby] for a practice parachute jump. There was not a tfr in effect for this operation. The schedule I had showed that the jump would happen from 5;500. Aircraft Y; was on final to 27R. Aircraft X had called me 10 south of the airport for class bravo transition; north of the 27R final approach course and the [area of orbit]. When aircraft X was about 3 miles south of aircraft Y; I issued traffic. Aircraft X replied that he was looking. I asked aircraft X if he could turn 15 degrees right; as this would point him at aircraft Y's tail. He replied that he could. I issued the instruction; and then updated the traffic call to aircraft X. Aircraft X reported the traffic in sight and that he could maintain visual separation. I told aircraft X to maintain visual separation from and pass behind aircraft Y. All of these calls where within about one minute. The 15 degree turn/passing behind aircraft Y; put aircraft X as close to going over top of the [orbit area] as he could have been without trying. During this time; I noticed that aircraft Z was still at 4;500. As aircraft X was passing the [orbit area]; another controller said that he could see the jumpers coming down. Aircraft Z was still at 4;500; and I was given no notice that jumpers where away; or that they would be jumping from any altitude other than 5;500. The only plan effected to separate traffic from the jump zone; was to have all phl arrivals land 27R; and to have aircraft Z remain north of I-95 (which runs between the [orbit area] and the 27R final). Aircraft Z notified the approach controller one pass prior to jumpers way. The approach controller did not notify the tower. While I was expecting to receive notification; the approach controller thought that the TRACON supervisor would notify the tower supervisor. This did not happen. There were not any pre-planned notification procedures.

Original NASA ASRS Text

Title: PHL Local Controller reported a loss of separation when a helicopter passed under an aircraft transporting skydivers. The Controller had not been advised that the jumpers had exited the aircraft. Reporter noted a lack of communication between TRACON and Tower supervisors.

Narrative: Aircraft Z; was orbiting [nearby] for a practice parachute jump. There was not a TFR in effect for this operation. The schedule I had showed that the jump would happen from 5;500. Aircraft Y; was on final to 27R. Aircraft X had called me 10 south of the airport for Class Bravo transition; north of the 27R final approach course and the [area of orbit]. When Aircraft X was about 3 miles south of Aircraft Y; I issued traffic. Aircraft X replied that he was looking. I asked Aircraft X if he could turn 15 degrees right; as this would point him at Aircraft Y's tail. He replied that he could. I issued the instruction; and then updated the traffic call to Aircraft X. Aircraft X reported the traffic in sight and that he could maintain visual separation. I told Aircraft X to maintain visual separation from and pass behind Aircraft Y. All of these calls where within about one minute. The 15 degree turn/passing behind Aircraft Y; put Aircraft X as close to going over top of the [orbit area] as he could have been without trying. During this time; I noticed that Aircraft Z was still at 4;500. As Aircraft X was passing the [orbit area]; another controller said that he could see the jumpers coming down. Aircraft Z was still at 4;500; and I was given no notice that jumpers where away; or that they would be jumping from any altitude other than 5;500. The only plan effected to separate traffic from the jump zone; was to have all PHL arrivals land 27R; and to have Aircraft Z remain north of I-95 (which runs between the [orbit area] and the 27R final). Aircraft Z notified the approach controller one pass prior to jumpers way. The approach controller did not notify the tower. While I was expecting to receive notification; the approach controller thought that the TRACON supervisor would notify the tower supervisor. This did not happen. There were not any pre-planned notification procedures.

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	1317220
Time
Date	201512
Local Time Of Day	1201-1800
Place
Locale Reference	PHL.Tower
State Reference	PA
Environment
Light	Daylight
Aircraft 1
Make Model Name	Helicopter
Operating Under FAR Part	Part 135
Flight Phase	Cruise
Flight Plan	VFR
Aircraft 2
Make Model Name	Small Transport Low Wing 2 Recip Eng
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 4.5
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Phl local controller reported a loss of separation when a helicopter passed under an aircraft transporting skydivers. The controller had not been advised that the jumpers had exited the aircraft. Reporter noted a lack of communication between TRACON and tower supervisors.