37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 212025 |
Time | |
Date | 199206 |
Day | Wed |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : aus |
State Reference | TX |
Altitude | msl bound lower : 4500 msl bound upper : 4500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : aus |
Operator | general aviation : personal |
Make Model Name | Small Transport, Low Wing, 2 Recip Eng |
Flight Phase | cruise other |
Flight Plan | None |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : private |
Experience | flight time last 90 days : 17 flight time total : 446 flight time type : 286 |
ASRS Report | 212025 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | non adherence : far other anomaly other |
Independent Detector | aircraft equipment other aircraft equipment : unspecified other flight crewa |
Resolutory Action | flight crew : exited penetrated airspace |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I was flying VFR at 4500 ft from tyr direct aus. The base of the scattered clouds was 6500 ft. I had not received a briefing before leaving. Lost tyler VOR signal 65 mi out. Turned to austin VOR 114.6 and proceeded on a 210 heading. It is normal to have a 20 min lapse in signal between tyler and austin. The clouds were starting to build and the cloud base was getting lower. It was changing from scattered to broken. Austin approach was receiving reports of a cell building 15 mi to the east and was asking for aircraft radar reports. I found it on my radar. It was showing up just on the centerline and to the right of my path on radar. Visually it was directly in front of me. Listened to ATIS again, verified my notes. Tried 118 on navigation, no such frequency. Turned to 117.1. The needle showed me too far to the south to be coming from austin. Tried to get a bearing from georgetown NDB, needle would not settle. Maybe I was south, turned toward VOR signal. There was a city, austin, at 12.6 DME. Checked traffic and turned left maintaining 4500 to 4600 ft altitude. Switched to approach. I needed to know if I was causing a problem and report if call for. I flew toward a lake directly away from VOR. Tuned to lee county (giddings) NDB. Needle verified the lake was north of bastrop. Circled over bastrop. Reported my position to austin approach, received squawk code and proceeded with instructions into austin. Some of the factors contributing to situation; I had not received a briefing before leaving. Time lapse between VOR signals had been too long, but I knew I was on the proper published frequency and I would pick up ATIS at 30 mi out. I had become involved with the changing WX and the evaluation of it on the radar. I had never encountered a navigation frequency change at an airport. I did not think a frequency change at a large airport would be possible in a short enough time not to be published. I did not understand the ATIS information 'VORTAC is 117.1 and channel 118.' I thought it had to be for special IFR approach or military information. A few more words in the information would have been a lot clrer; such as 'VORTAC frequency has been changed to 117.1 and channel 118.' I know now that large airports VOR frequencys can be changed without publication and how to understand them over ATIS.
Original NASA ASRS Text
Title: PVT PLT OF SMT ACFT INADVERTENTLY PENETRATED AN ARSA.
Narrative: I WAS FLYING VFR AT 4500 FT FROM TYR DIRECT AUS. THE BASE OF THE SCATTERED CLOUDS WAS 6500 FT. I HAD NOT RECEIVED A BRIEFING BEFORE LEAVING. LOST TYLER VOR SIGNAL 65 MI OUT. TURNED TO AUSTIN VOR 114.6 AND PROCEEDED ON A 210 HDG. IT IS NORMAL TO HAVE A 20 MIN LAPSE IN SIGNAL BTWN TYLER AND AUSTIN. THE CLOUDS WERE STARTING TO BUILD AND THE CLOUD BASE WAS GETTING LOWER. IT WAS CHANGING FROM SCATTERED TO BROKEN. AUSTIN APCH WAS RECEIVING RPTS OF A CELL BUILDING 15 MI TO THE E AND WAS ASKING FOR ACFT RADAR RPTS. I FOUND IT ON MY RADAR. IT WAS SHOWING UP JUST ON THE CTRLINE AND TO THE R OF MY PATH ON RADAR. VISUALLY IT WAS DIRECTLY IN FRONT OF ME. LISTENED TO ATIS AGAIN, VERIFIED MY NOTES. TRIED 118 ON NAV, NO SUCH FREQ. TURNED TO 117.1. THE NEEDLE SHOWED ME TOO FAR TO THE S TO BE COMING FROM AUSTIN. TRIED TO GET A BEARING FROM GEORGETOWN NDB, NEEDLE WOULD NOT SETTLE. MAYBE I WAS S, TURNED TOWARD VOR SIGNAL. THERE WAS A CITY, AUSTIN, AT 12.6 DME. CHKED TFC AND TURNED L MAINTAINING 4500 TO 4600 FT ALT. SWITCHED TO APCH. I NEEDED TO KNOW IF I WAS CAUSING A PROBLEM AND RPT IF CALL FOR. I FLEW TOWARD A LAKE DIRECTLY AWAY FROM VOR. TUNED TO LEE COUNTY (GIDDINGS) NDB. NEEDLE VERIFIED THE LAKE WAS N OF BASTROP. CIRCLED OVER BASTROP. RPTED MY POS TO AUSTIN APCH, RECEIVED SQUAWK CODE AND PROCEEDED WITH INSTRUCTIONS INTO AUSTIN. SOME OF THE FACTORS CONTRIBUTING TO SITUATION; I HAD NOT RECEIVED A BRIEFING BEFORE LEAVING. TIME LAPSE BTWN VOR SIGNALS HAD BEEN TOO LONG, BUT I KNEW I WAS ON THE PROPER PUBLISHED FREQ AND I WOULD PICK UP ATIS AT 30 MI OUT. I HAD BECOME INVOLVED WITH THE CHANGING WX AND THE EVALUATION OF IT ON THE RADAR. I HAD NEVER ENCOUNTERED A NAV FREQ CHANGE AT AN ARPT. I DID NOT THINK A FREQ CHANGE AT A LARGE ARPT WOULD BE POSSIBLE IN A SHORT ENOUGH TIME NOT TO BE PUBLISHED. I DID NOT UNDERSTAND THE ATIS INFO 'VORTAC IS 117.1 AND CHANNEL 118.' I THOUGHT IT HAD TO BE FOR SPECIAL IFR APCH OR MIL INFO. A FEW MORE WORDS IN THE INFO WOULD HAVE BEEN A LOT CLRER; SUCH AS 'VORTAC FREQ HAS BEEN CHANGED TO 117.1 AND CHANNEL 118.' I KNOW NOW THAT LARGE ARPTS VOR FREQS CAN BE CHANGED WITHOUT PUBLICATION AND HOW TO UNDERSTAND THEM OVER ATIS.
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.