Narrative:

Northbound from myf to wvi I experienced a near collision with an air carrier sbound. It was near V-107, and I was on flight following and talking to ZLA. The controller called the traffic at 2 O'clock. As I looked in that direction I saw that we were less than 3 seconds from an abeam position, I estimate the closing speed at more than 500 KTS. Without interviewing the controller I can't say much, except that see and avoid does not work reliably at that high a closing speed. Obviously, it would have been better if the controller had notified me when we were at least 15 seconds apart instead of 3. I just don't know what the controller's situation was, but I do believe a different controller took over the frequency right after I told him I was going to have to file an ASRS report.

Google
 

Original NASA ASRS Text

Title: WHILE ON ATC FLT FOLLOWING, THE PLT OF A LIGHT ACFT EXPERIENCED AN NMAC WITH OPPOSITE DIRECTION ACR TFC. PLT RPTED THAT THE ARTCC CTLR PROVIDED TFC INFO, BUT THAT THE ADVISORY WAS TOO LATE FOR THE PLT TO RESPOND.

Narrative: NBOUND FROM MYF TO WVI I EXPERIENCED A NEAR COLLISION WITH AN ACR SBOUND. IT WAS NEAR V-107, AND I WAS ON FLT FOLLOWING AND TALKING TO ZLA. THE CTLR CALLED THE TFC AT 2 O'CLOCK. AS I LOOKED IN THAT DIRECTION I SAW THAT WE WERE LESS THAN 3 SECONDS FROM AN ABEAM POS, I ESTIMATE THE CLOSING SPD AT MORE THAN 500 KTS. WITHOUT INTERVIEWING THE CTLR I CAN'T SAY MUCH, EXCEPT THAT SEE AND AVOID DOES NOT WORK RELIABLY AT THAT HIGH A CLOSING SPD. OBVIOUSLY, IT WOULD HAVE BEEN BETTER IF THE CTLR HAD NOTIFIED ME WHEN WE WERE AT LEAST 15 SECONDS APART INSTEAD OF 3. I JUST DON'T KNOW WHAT THE CTLR'S SIT WAS, BUT I DO BELIEVE A DIFFERENT CTLR TOOK OVER THE FREQ RIGHT AFTER I TOLD HIM I WAS GOING TO HAVE TO FILE AN ASRS RPT.

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.