37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1095436 |
Time | |
Date | 201306 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | PHL.Airport |
State Reference | PA |
Aircraft 1 | |
Make Model Name | BAe 125 Series 800 |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Sail Plane |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
A hawker had departed phl off of runway 35 enroute to rdg. I received the aircraft climbing to 4;000 from the departure controller; on runway heading. I cleared the aircraft direct ptw; on course. Through out most of the day there had been heavy glider activity in the area of ckz airport; about 15 miles east-northeast of ptw. A short time before I made initial contact with the hawker; I observed a glider target about 5 east of ptw at about 4;500. I made a note to myself that the glider was well outside of the normal area of glider activity. I then became busy with other traffic I was working. A short time later I looked back at the hawker; which was now approaching ptw. I noticed the glider target over ptw VOR at 4;000; barely moving. The glider was no more than a mile from the hawker; and the hawker was headed directly for it. The conflict alert activated simultaneously. Realizing that I didn't have time to make a full traffic call to the hawker; I stated the following: 'hawker; traffic alert; turn left heading 270 immediately.' the hawker read back the turn and advised that they were in a TCAS climb. I then issued traffic information. The hawker reported traffic in sight and stated that it was a glider. I descended the hawker back to 4;000 and put him back on course. The aircraft was handed off to rdg without further complication. In the future I will attempt to increase my working and scan speeds on days where there is heavy VFR and glider activity; so as to catch these situations sooner. I would also hope that some of these glider pilots would realize that soaring over a VOR at an IFR altitude (4;000) is not a good idea and would attempt to remain at VFR altitudes away from busy routes; intersections; and navaids. I have noticed this problem on other days along V3 near mazie intersection. Sometimes it seems that there are a half-dozen VFR gliders operating between 4;000 and 5;000 right on V3. This can be dangerous; as we feed traffic to N90 northeast bound at 4;000 on V3.
Original NASA ASRS Text
Title: PHL Controller described a IFR/VFR glider conflict event near CKZ Airport; the reporter noting the glider activity at this location and on V3 is frequently problematic.
Narrative: A Hawker had departed PHL off of Runway 35 enroute to RDG. I received the aircraft climbing to 4;000 from the Departure Controller; on runway heading. I cleared the aircraft direct PTW; on course. Through out most of the day there had been heavy glider activity in the area of CKZ Airport; about 15 miles east-northeast of PTW. A short time before I made initial contact with the Hawker; I observed a glider target about 5 east of PTW at about 4;500. I made a note to myself that the glider was well outside of the normal area of glider activity. I then became busy with other traffic I was working. A short time later I looked back at the Hawker; which was now approaching PTW. I noticed the glider target over PTW VOR at 4;000; barely moving. The glider was no more than a mile from the Hawker; and the Hawker was headed directly for it. The Conflict Alert activated simultaneously. Realizing that I didn't have time to make a full traffic call to the Hawker; I stated the following: 'Hawker; traffic alert; turn left heading 270 immediately.' The Hawker read back the turn and advised that they were in a TCAS climb. I then issued traffic information. The Hawker reported traffic in sight and stated that it was a glider. I descended the Hawker back to 4;000 and put him back on course. The aircraft was handed off to RDG without further complication. In the future I will attempt to increase my working and scan speeds on days where there is heavy VFR and glider activity; so as to catch these situations sooner. I would also hope that some of these glider pilots would realize that soaring over a VOR at an IFR altitude (4;000) is not a good idea and would attempt to remain at VFR altitudes away from busy routes; intersections; and NAVAIDS. I have noticed this problem on other days along V3 near MAZIE Intersection. Sometimes it seems that there are a half-dozen VFR gliders operating between 4;000 and 5;000 right on V3. This can be dangerous; as we feed traffic to N90 northeast bound at 4;000 on V3.
Data retrieved from NASA's ASRS site as of July 2013 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.