37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 141728 |
Time | |
Date | 199004 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : rdu airport : w52 |
State Reference | NC |
Altitude | msl bound lower : 3000 msl bound upper : 4500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : rdu |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, Low Wing, 1 Eng, Fixed Gear |
Flight Phase | cruise other descent other |
Flight Plan | VFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : private |
Experience | flight time last 90 days : 20 flight time total : 90 flight time type : 7 |
ASRS Report | 141728 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : published procedure non adherence : clearance |
Independent Detector | other controllera |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Aircraft was on a VFR flight to W52 at 4500'. Contacted rdu approach about 20 mi southeast. Approach gave transponder code, which was inserted. Rdu approach did not have radar contact, which I thought unusual. Continued on course as directed. Transited southern fringe of rdu arsa. Controller notified me of radar contact 10 mi southwest rdu. At that time stated possible transponder failure. Next statement was to begin VFR descent to 3000', and I had traffic 3 O'clock, 2 mi, same destination. I reported W52 in sight. I was, at this time, not in the arsa. I began a descent to pattern altitude 3-5 mi ese W52. Changed frequency to raleigh radio to cancel flight plan. Then changed frequency to W52 unicom 123.00. At this time the small aircraft traffic informed me that rdu approach had not terminated radar service. Recontacted rdu approach. They had lost contact (radio) for 3-5 mins which at that point radar service was terminated. Problem, in my opinion, began with transponder failure and/or failure of pilot/ATC to diagnose transponder failure, leading to distrs in later states. Problem changing frequency west/O requesting frequency change or receiving clearance to do so. Unclr instructions re: arsa termination by controller.
Original NASA ASRS Text
Title: GA SMA FREQ CHANGE PREMATURE. ACFT WAS STILL IN ARSA WHEN PLT CHANGED TO UNICOM FREQ.
Narrative: ACFT WAS ON A VFR FLT TO W52 AT 4500'. CONTACTED RDU APCH ABOUT 20 MI SE. APCH GAVE XPONDER CODE, WHICH WAS INSERTED. RDU APCH DID NOT HAVE RADAR CONTACT, WHICH I THOUGHT UNUSUAL. CONTINUED ON COURSE AS DIRECTED. TRANSITED SOUTHERN FRINGE OF RDU ARSA. CTLR NOTIFIED ME OF RADAR CONTACT 10 MI SW RDU. AT THAT TIME STATED POSSIBLE XPONDER FAILURE. NEXT STATEMENT WAS TO BEGIN VFR DSNT TO 3000', AND I HAD TFC 3 O'CLOCK, 2 MI, SAME DEST. I RPTED W52 IN SIGHT. I WAS, AT THIS TIME, NOT IN THE ARSA. I BEGAN A DSNT TO PATTERN ALT 3-5 MI ESE W52. CHANGED FREQ TO RALEIGH RADIO TO CANCEL FLT PLAN. THEN CHANGED FREQ TO W52 UNICOM 123.00. AT THIS TIME THE SMA TFC INFORMED ME THAT RDU APCH HAD NOT TERMINATED RADAR SVC. RECONTACTED RDU APCH. THEY HAD LOST CONTACT (RADIO) FOR 3-5 MINS WHICH AT THAT POINT RADAR SVC WAS TERMINATED. PROB, IN MY OPINION, BEGAN WITH XPONDER FAILURE AND/OR FAILURE OF PLT/ATC TO DIAGNOSE XPONDER FAILURE, LEADING TO DISTRS IN LATER STATES. PROB CHANGING FREQ W/O REQUESTING FREQ CHANGE OR RECEIVING CLRNC TO DO SO. UNCLR INSTRUCTIONS RE: ARSA TERMINATION BY CTLR.
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.