Narrative:

I had been on flight data for 14 minutes and slid to the local east position to relieve the controller so they could slide to another position for a certification check ride. I was briefed that aircraft X (parachute jump aircraft) was aware of the training flight (aircraft Y) and that aircraft X would give a 1 minute call prior to releasing the parachute jumpers. I had 4 IFR aircraft under my control being vectored for various approaches into ngp. Aircraft Y was passed as being on our local channel 18 and rdr service terminated. When aircraft X announced 1 minute; I made the blanket broadcast over the frequencies for the military training aircraft to remain clear of ras for parachute operations. Crp does not normally keep channel 18 keyed up and I do not recall whether or not I had it keyed at the time of my general broadcast. Shortly after; aircraft X asked who the texans were that flew underneath his jumpers. I told him to stand by; verified that the flight was in the vicinity of ras; transmitted on ch 18 to the aircraft Y flight to work west of ras for jump operations and the flight lead acknowledged. No further issues during that jump. Aircraft X launched 1 more time while I was on the position without incident.there are a number of things that could be implemented to preclude this from happening again.1) keep all formation flights on ch 17 with the other training flights working the alert 632 area.2) have the jump school deliver a daily flight schedule to crp in order to disseminate to the controllers so that they are aware of the scheduled parachute operations prior to assuming the position. Once jump aircraft is airborne; ensure controller has ch 18 keyed and broadcasts all transmissions on that frequency until jump operations are complete.3) do not terminate radar services of the aircraft working the central (formation flight) area.

Related reports:

Google
 

Original NASA ASRS Text

Title: CRP Tower Controller reported a conflict between a parachute operation and a flight of training aircraft that flew underneath the skydivers. Reporter responded to a pilot inquiry and resolved the situation.

Narrative: I had been on flight data for 14 minutes and slid to the Local East position to relieve the controller so they could slide to another position for a certification check ride. I was briefed that Aircraft X (parachute jump aircraft) was aware of the training flight (Aircraft Y) and that Aircraft X would give a 1 minute call prior to releasing the parachute jumpers. I had 4 IFR aircraft under my control being vectored for various approaches into NGP. Aircraft Y was passed as being on our local channel 18 and RDR service terminated. When Aircraft X announced 1 minute; I made the blanket broadcast over the frequencies for the military training aircraft to remain clear of RAS for parachute operations. CRP does not normally keep channel 18 keyed up and I do not recall whether or not I had it keyed at the time of my general broadcast. Shortly after; Aircraft X asked who the Texans were that flew underneath his jumpers. I told him to stand by; verified that the flight was in the vicinity of RAS; transmitted on CH 18 to the Aircraft Y flight to work west of RAS for jump operations and the flight lead acknowledged. No further issues during that jump. Aircraft X launched 1 more time while I was on the position without incident.There are a number of things that could be implemented to preclude this from happening again.1) Keep all formation flights on CH 17 with the other training flights working the alert 632 area.2) Have the jump school deliver a daily flight schedule to CRP in order to disseminate to the controllers so that they are aware of the scheduled parachute operations prior to assuming the position. Once jump aircraft is airborne; ensure controller has CH 18 keyed and broadcasts all transmissions on that frequency until jump operations are complete.3) Do not terminate radar services of the aircraft working the central (formation flight) area.

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.