37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 386510 |
Time | |
Date | 199711 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : ocn |
State Reference | CA |
Altitude | msl bound lower : 4500 msl bound upper : 4500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : lax |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise other |
Flight Plan | None |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : commercial pilot : cfi |
Experience | flight time last 90 days : 250 flight time total : 750 flight time type : 600 |
ASRS Report | 386510 |
Person 2 | |
Affiliation | government : faa |
Function | controller : departure |
Qualification | controller : radar |
Events | |
Anomaly | aircraft equipment problem : less severe other anomaly other other spatial deviation |
Independent Detector | other controllera other flight crewa |
Resolutory Action | none taken : unable |
Consequence | Other |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | other |
Narrative:
While en route from see to ral, I heard pilot report to socal that both his GPS units were inoperative. At first I thought nothing of this. Shortly after this, socal told me they were receiving 'carrier only' from my communication radio. At this time, I noticed my portable GPS off line. I began to troubleshoot my radios. I regained radio contact with socal with my #2 communication. At one point, I believed both communication radios had failed or had an intercom problem and brought out the hand held communication radio. As it worked out, socal seemed frustrated with me and said squawk VFR radar service terminated once I was outside of the class B airspace. When I contacted them again I got a new code previous to entering the march AFB class C. They seemed very busy and I was scolded by a female controller for using too much air time when I tried to explain my problem. I did make a PIREP. I got no further advisories and no handoff to the tower. I contacted the tower before reaching the 5 mi radius. GPS was working now. The reason I'm writing this report is twofold. 1) I'm sure I'm not in violation of the 'radio contact' requirement for the airspace I flew through. Socal may see things differently. 2) while troubleshooting my communication radios, I somehow thought the GPS problem was related. Nonsense. When looked at by the avionics shop they found the #1 communication had a true breakdown and no other defects in any other system. For a short time in the air, I believed both communications were out. I was probably trying so many combinations that I must have forgotten to select communication #2 on the audio panel. (I was alone.) question: I talked to FSS and there was no NOTAM for GPS outage.
Original NASA ASRS Text
Title: PLT OF C172A HAS RADIO PROB WHILE DEPARTING CLASS B AIRSPACE. ON ENTERING CLASS C AIRSPACE THE RADIO PROB BECOMES EVIDENT AGAIN. GPS ALSO IS SKEWED.
Narrative: WHILE ENRTE FROM SEE TO RAL, I HEARD PLT RPT TO SOCAL THAT BOTH HIS GPS UNITS WERE INOP. AT FIRST I THOUGHT NOTHING OF THIS. SHORTLY AFTER THIS, SOCAL TOLD ME THEY WERE RECEIVING 'CARRIER ONLY' FROM MY COM RADIO. AT THIS TIME, I NOTICED MY PORTABLE GPS OFF LINE. I BEGAN TO TROUBLESHOOT MY RADIOS. I REGAINED RADIO CONTACT WITH SOCAL WITH MY #2 COM. AT ONE POINT, I BELIEVED BOTH COM RADIOS HAD FAILED OR HAD AN INTERCOM PROB AND BROUGHT OUT THE HAND HELD COM RADIO. AS IT WORKED OUT, SOCAL SEEMED FRUSTRATED WITH ME AND SAID SQUAWK VFR RADAR SVC TERMINATED ONCE I WAS OUTSIDE OF THE CLASS B AIRSPACE. WHEN I CONTACTED THEM AGAIN I GOT A NEW CODE PREVIOUS TO ENTERING THE MARCH AFB CLASS C. THEY SEEMED VERY BUSY AND I WAS SCOLDED BY A FEMALE CTLR FOR USING TOO MUCH AIR TIME WHEN I TRIED TO EXPLAIN MY PROB. I DID MAKE A PIREP. I GOT NO FURTHER ADVISORIES AND NO HDOF TO THE TWR. I CONTACTED THE TWR BEFORE REACHING THE 5 MI RADIUS. GPS WAS WORKING NOW. THE REASON I'M WRITING THIS RPT IS TWOFOLD. 1) I'M SURE I'M NOT IN VIOLATION OF THE 'RADIO CONTACT' REQUIREMENT FOR THE AIRSPACE I FLEW THROUGH. SOCAL MAY SEE THINGS DIFFERENTLY. 2) WHILE TROUBLESHOOTING MY COM RADIOS, I SOMEHOW THOUGHT THE GPS PROB WAS RELATED. NONSENSE. WHEN LOOKED AT BY THE AVIONICS SHOP THEY FOUND THE #1 COM HAD A TRUE BREAKDOWN AND NO OTHER DEFECTS IN ANY OTHER SYS. FOR A SHORT TIME IN THE AIR, I BELIEVED BOTH COMS WERE OUT. I WAS PROBABLY TRYING SO MANY COMBINATIONS THAT I MUST HAVE FORGOTTEN TO SELECT COM #2 ON THE AUDIO PANEL. (I WAS ALONE.) QUESTION: I TALKED TO FSS AND THERE WAS NO NOTAM FOR GPS OUTAGE.
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.