Small Transport; Low Wing; 2 Turbojet Eng
Air Traffic Control Developmental
Communication Breakdown; Distraction
ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance
Human Factors; Aircraft; Procedure
Paragliding activity in the vicinity of the city of Aspen puts paragliders in close proximity to aircraft landing Runway 33 at ASE airport.  Runway 33 is rarely a landing runway; however; due to a tailwind to Runway 15; traffic landed Runway 33.  Due to terrain; landing 33 is only possible via right traffic.  Right traffic to 33 puts aircraft near paragliders.  Per LOA between paragliders and ASE Tower; aircraft must be advised of paraglider activity.  Paraglider activity was broadcasted on the ATIS; Aircraft X reported receipt of the current ATIS which had paraglider activity on it.  I observed a paraglider in the projected course of Aircraft X when the aircraft had just turned base.  The paraglider appeared to be slightly more than a half mile ahead of Aircraft X.  I advised Aircraft X again that there were paragliders near Aspen Mountain and to use caution.  Aircraft X acknowledged receipt of my advisory; appeared to climb slightly; then continued to the runway and landed.  When the paragliding company reported operations terminated for the day (as per LOA) they told me they felt the jet was 'too close for comfort.'  I agreed and explained everything in this statement. I recommend that paragliders not operate in the traffic pattern at Aspen. They are small and not easily identified visually by controllers.  It's too dangerous for them to be in the pattern.
ASE Developmental Controller reports of an incident where paragliding activities are done and a jet that departs ASE gets too close to the glider.