37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 330749 |
Time | |
Date | 199603 |
Day | Sun |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : lzu |
State Reference | GA |
Altitude | msl bound lower : 3000 msl bound upper : 4000 |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : atl |
Make Model Name | Baron 58/58TC |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise other |
Route In Use | arrival other enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Experience | controller non radar : 1 controller radar : 13 |
ASRS Report | 330749 |
Person 2 | |
Function | oversight : pic |
Qualification | pilot : instrument pilot : private |
Events | |
Anomaly | other anomaly other |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance |
Consequence | Other |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | other |
Narrative:
I was vectoring the above BE58 for ILS runway 25 approach at lzu. He was on a 020 degree heading at 3000 ft MSL. At approximately the 144 degree radial at 10 NM from lzu airport, I completely lost radar and beacon targets. Atl's new ASR-9 was supposed to keep this from being a problem but it continues to occur. I moved to a radar scope slaved off mge's ASR 8 radar but couldn't locate the BE58. To alleviate the problem, I instructed the pilot to climb to 4000 ft. I wasn't able to identify him until he was about to cross the localizer 1000 ft above approach altitude. The radar coverage where I first lost contact with him is supposedly normal. Farther north, it is notoriously bad at 3000 ft and sometimes even at 4000 ft. We anticipate this airport to be rather busy during the upcoming olympics. We will have to work much harder with more traffic just to provide service to lzu airport. Initially, FAA management promised us a new radar for this area to be in by this present time but now tell us we will have to wait until after the olympics.
Original NASA ASRS Text
Title: CTLR CLAIMS ATL ASR-9 RADAR COVERAGE NEAR LZU, GA, IS POOR. RPTR STATES THAT RADAR COVERAGE IS NOT ADEQUATE FOR THEIR AREA OF ATC RESPONSIBILITY 30 NE OF ATL NEAR LZU BELOW 4000 FT.
Narrative: I WAS VECTORING THE ABOVE BE58 FOR ILS RWY 25 APCH AT LZU. HE WAS ON A 020 DEG HDG AT 3000 FT MSL. AT APPROX THE 144 DEG RADIAL AT 10 NM FROM LZU ARPT, I COMPLETELY LOST RADAR AND BEACON TARGETS. ATL'S NEW ASR-9 WAS SUPPOSED TO KEEP THIS FROM BEING A PROB BUT IT CONTINUES TO OCCUR. I MOVED TO A RADAR SCOPE SLAVED OFF MGE'S ASR 8 RADAR BUT COULDN'T LOCATE THE BE58. TO ALLEVIATE THE PROB, I INSTRUCTED THE PLT TO CLB TO 4000 FT. I WASN'T ABLE TO IDENT HIM UNTIL HE WAS ABOUT TO CROSS THE LOC 1000 FT ABOVE APCH ALT. THE RADAR COVERAGE WHERE I FIRST LOST CONTACT WITH HIM IS SUPPOSEDLY NORMAL. FARTHER N, IT IS NOTORIOUSLY BAD AT 3000 FT AND SOMETIMES EVEN AT 4000 FT. WE ANTICIPATE THIS ARPT TO BE RATHER BUSY DURING THE UPCOMING OLYMPICS. WE WILL HAVE TO WORK MUCH HARDER WITH MORE TFC JUST TO PROVIDE SVC TO LZU ARPT. INITIALLY, FAA MGMNT PROMISED US A NEW RADAR FOR THIS AREA TO BE IN BY THIS PRESENT TIME BUT NOW TELL US WE WILL HAVE TO WAIT UNTIL AFTER THE OLYMPICS.
Data retrieved from NASA's ASRS site as of July 2007 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.