37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 822037 |
Time | |
Date | 200902 |
Place | |
Locale Reference | PHL.TRACON |
State Reference | PA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Radar 4 Air Traffic Control Time Certified In Pos 1 (yrs) 3 |
Events | |
Anomaly | Other Radar Equipment Limitaion |
Narrative:
February 2009 the phl ASR9 was out for maintenance and we were using the ASR11. I was working and running arrivals to runway 35 with the use of the crda (ghost targets). The SOP for this sector states that the runway 35 arrival shall be on the corresponding ghost target or within 1 mile in trail of the ghost target; when the aircraft is within 2 miles of the runway intersection. When the ASR11 is in use; the ghost target for runway 27R drops off before reaching the runway. This lack of radar coverage to the ground in an ASR11 operation makes this procedure unsafe.
Original NASA ASRS Text
Title: PHL Approach Controller voiced concern regarding ASR-11 tracking limitations during Runway 35 CRDA operations.
Narrative: February 2009 the PHL ASR9 was out for maintenance and we were using the ASR11. I was working and running arrivals to Runway 35 with the use of the CRDA (ghost targets). The SOP for this sector states that the Runway 35 arrival shall be on the corresponding ghost target or within 1 mile in trail of the ghost target; when the aircraft is within 2 miles of the runway intersection. When the ASR11 is in use; the ghost target for Runway 27R drops off before reaching the runway. This lack of radar coverage to the ground in an ASR11 Operation makes this procedure unsafe.
Data retrieved from NASA's ASRS site as of April 2012 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.