Narrative:

VFR flight in C-182, level at 7500 ft MSL, inbound to rzs on course 115 degrees, 11 DME, 150 KTS ground speed. I was receiving flight following from vandenburg approach on 118.0. Sun had set (at 7500 ft) approximately 15 mins prior. All navigation, strobe, and beacon lights were on. WX was clear and 30 mi visibility, a haze layer below started at approximately 6000 ft MSL and reduced visibility to 8-10 mi. No warning from vandenburg. Suddenly, a commuter twin engine airliner appeared at approximately 11 O'clock, plus 200 ft vertically, and approximately 225 ft in front of me. (He was descending into santa barbara.) the airliner continued to descend in front of me. I turned right and descended. When I felt there was no longer a collision danger, I was on course 150 degrees and had descended to 7300 ft. The airliner never maneuvered. After the airliner was well in front of me and below, I climbed and resumed course for san marcus pass. The airliner continued to descend over the ridge into sba. As I was returning to course, vandenburg handed me off to santa barbara (125.4). Before I left the frequency, I queried the controller as to whether or not he had seen the airliner that had nearly hit me. He said no, but mentioned there are known radar differences in the lake cachuma area. I continued with santa barbara approach, and then home. After landing I verified that all of my lighting system were operational. The next day, I reported to the local FSS an near midair collision. While it is my responsibility to see and avoid other traffic, I always thought that participating in flight following would protect me from IFR traffic (or protect IFR traffic from me, which is the same thing). Obviously, I was wrong. As the airliner in question was not talking to vandenberg approach, I wonder if there is not an ATC coordination problem in this area. I should have been handed off to sba, or the airliner should have been talking to vandenberg. Every aircraft has a blind spot for visibility. In a cessna 182, you cannot scan for traffic above and behind you. See and avoid is a cooperative concept. It may be that sba saw me on radar and chose not to call traffic to the airliner due to altimeter setting differences. This is further support for point #2, thereby insuring common altimeter settings. Known radar deficiencies sound like a problem that should be fixed. The van controller (and others) mentioned reflections off the lake as a problem. This is easily (technically, not budgetarily) remedied by installing another radar facility in the valley near the lake and performing some error checking on the track files. (I am an aeronautical and electrical engineer with radar experience.) this would easily remedy multipath effects. The crew of the airliner either didn't see me or somehow misjudged my proximity. I suspect the former, as no evasive action was ever taken by the airliner. This might have been caused by cockpit distrs. Only the crew of that aircraft knows. Crews operating on IFR flight plans in VMC, I feel, must take the time to scan in front of them, and should be made aware when operating in areas of known radar performance dificiencies.

Google
 

Original NASA ASRS Text

Title: SMA HAS NMAC WITH COMMUTER ACFT.

Narrative: VFR FLT IN C-182, LEVEL AT 7500 FT MSL, INBOUND TO RZS ON COURSE 115 DEGS, 11 DME, 150 KTS GND SPD. I WAS RECEIVING FLT FOLLOWING FROM VANDENBURG APCH ON 118.0. SUN HAD SET (AT 7500 FT) APPROX 15 MINS PRIOR. ALL NAV, STROBE, AND BEACON LIGHTS WERE ON. WX WAS CLR AND 30 MI VISIBILITY, A HAZE LAYER BELOW STARTED AT APPROX 6000 FT MSL AND REDUCED VISIBILITY TO 8-10 MI. NO WARNING FROM VANDENBURG. SUDDENLY, A COMMUTER TWIN ENG AIRLINER APPEARED AT APPROX 11 O'CLOCK, PLUS 200 FT VERTICALLY, AND APPROX 225 FT IN FRONT OF ME. (HE WAS DSNDING INTO SANTA BARBARA.) THE AIRLINER CONTINUED TO DSND IN FRONT OF ME. I TURNED R AND DSNDED. WHEN I FELT THERE WAS NO LONGER A COLLISION DANGER, I WAS ON COURSE 150 DEGS AND HAD DSNDED TO 7300 FT. THE AIRLINER NEVER MANEUVERED. AFTER THE AIRLINER WAS WELL IN FRONT OF ME AND BELOW, I CLBED AND RESUMED COURSE FOR SAN MARCUS PASS. THE AIRLINER CONTINUED TO DSND OVER THE RIDGE INTO SBA. AS I WAS RETURNING TO COURSE, VANDENBURG HANDED ME OFF TO SANTA BARBARA (125.4). BEFORE I LEFT THE FREQ, I QUERIED THE CTLR AS TO WHETHER OR NOT HE HAD SEEN THE AIRLINER THAT HAD NEARLY HIT ME. HE SAID NO, BUT MENTIONED THERE ARE KNOWN RADAR DIFFERENCES IN THE LAKE CACHUMA AREA. I CONTINUED WITH SANTA BARBARA APCH, AND THEN HOME. AFTER LNDG I VERIFIED THAT ALL OF MY LIGHTING SYS WERE OPERATIONAL. THE NEXT DAY, I RPTED TO THE LCL FSS AN NMAC. WHILE IT IS MY RESPONSIBILITY TO SEE AND AVOID OTHER TFC, I ALWAYS THOUGHT THAT PARTICIPATING IN FLT FOLLOWING WOULD PROTECT ME FROM IFR TFC (OR PROTECT IFR TFC FROM ME, WHICH IS THE SAME THING). OBVIOUSLY, I WAS WRONG. AS THE AIRLINER IN QUESTION WAS NOT TALKING TO VANDENBERG APCH, I WONDER IF THERE IS NOT AN ATC COORD PROB IN THIS AREA. I SHOULD HAVE BEEN HANDED OFF TO SBA, OR THE AIRLINER SHOULD HAVE BEEN TALKING TO VANDENBERG. EVERY ACFT HAS A BLIND SPOT FOR VISIBILITY. IN A CESSNA 182, YOU CANNOT SCAN FOR TFC ABOVE AND BEHIND YOU. SEE AND AVOID IS A COOPERATIVE CONCEPT. IT MAY BE THAT SBA SAW ME ON RADAR AND CHOSE NOT TO CALL TFC TO THE AIRLINER DUE TO ALTIMETER SETTING DIFFERENCES. THIS IS FURTHER SUPPORT FOR POINT #2, THEREBY INSURING COMMON ALTIMETER SETTINGS. KNOWN RADAR DEFICIENCIES SOUND LIKE A PROB THAT SHOULD BE FIXED. THE VAN CTLR (AND OTHERS) MENTIONED REFLECTIONS OFF THE LAKE AS A PROB. THIS IS EASILY (TECHNICALLY, NOT BUDGETARILY) REMEDIED BY INSTALLING ANOTHER RADAR FACILITY IN THE VALLEY NEAR THE LAKE AND PERFORMING SOME ERROR CHKING ON THE TRACK FILES. (I AM AN AERONAUTICAL AND ELECTRICAL ENGINEER WITH RADAR EXPERIENCE.) THIS WOULD EASILY REMEDY MULTIPATH EFFECTS. THE CREW OF THE AIRLINER EITHER DIDN'T SEE ME OR SOMEHOW MISJUDGED MY PROX. I SUSPECT THE FORMER, AS NO EVASIVE ACTION WAS EVER TAKEN BY THE AIRLINER. THIS MIGHT HAVE BEEN CAUSED BY COCKPIT DISTRS. ONLY THE CREW OF THAT ACFT KNOWS. CREWS OPERATING ON IFR FLT PLANS IN VMC, I FEEL, MUST TAKE THE TIME TO SCAN IN FRONT OF THEM, AND SHOULD BE MADE AWARE WHEN OPERATING IN AREAS OF KNOWN RADAR PERFORMANCE DIFICIENCIES.

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.