Narrative:

Loss of separation occurred while turning from base to final for runway 25R at lvk in VFR daylight conditions with unlimited visibility. My aircraft was cleared to land; number 4 behind a cherokee on downwind for runway 25R. At about the same time I also heard aircraft Y report 6 miles out on the ILS for runway 25R. The cherokee ahead flew an extended downwind and a wide square turn to base and to final. I had to extend my downwind to allow proper spacing. I made my turns in essentially the same locations as the cherokee. As I lifted the wing to turn from base to final; the conflicting aircraft appeared at 45 degrees off the nose closing with no change in aspect. I steepened my turn to final and ended up flying parallel to aircraft Y at the same altitude with Y about 200 to 300 ft off my left wing. I called the tower to report the conflicting traffic and they instructed me to follow aircraft Y. The tower clearly had no idea of my aircraft position relative to aircraft Y. I told the tower 'that won't work' and they instructed us to do a 360. A right 360 was performed and proper spacing and separation was regained. Note that the right 360 caused a taws warning. Corrective action: ensure that local controllers are watching both 'local' traffic and the ILS traffic during VFR conditions. For new controllers; do not allow ILS approaches to runway 25R while there are multiple VFR aircraft in the pattern. If not already done; install a radar repeater to allow lvk tower to see traffic; which is beyond visual range.

Google
 

Original NASA ASRS Text

Title: Pilot of high wing aircraft in VFR traffic pattern at LVK reports NMAC with low wing aircraft on ILS approach to Runway 25R. The conflict was discovered as wing was raised for turn to final; Tower issued 360 to high wing aircraft.

Narrative: Loss of separation occurred while turning from base to final for Runway 25R at LVK in VFR daylight conditions with unlimited visibility. My aircraft was cleared to land; number 4 behind a Cherokee on downwind for Runway 25R. At about the same time I also heard Aircraft Y report 6 miles out on the ILS for Runway 25R. The Cherokee ahead flew an extended downwind and a wide square turn to base and to final. I had to extend my downwind to allow proper spacing. I made my turns in essentially the same locations as the Cherokee. As I lifted the wing to turn from base to final; the conflicting aircraft appeared at 45 degrees off the nose closing with no change in aspect. I steepened my turn to final and ended up flying parallel to Aircraft Y at the same altitude with Y about 200 to 300 FT off my left wing. I called the tower to report the conflicting traffic and they instructed me to follow Aircraft Y. The Tower clearly had no idea of my aircraft position relative to Aircraft Y. I told the Tower 'that won't work' and they instructed us to do a 360. A right 360 was performed and proper spacing and separation was regained. Note that the right 360 caused a TAWS warning. Corrective Action: Ensure that local controllers are watching both 'local' traffic and the ILS traffic during VFR conditions. For new controllers; do not allow ILS approaches to Runway 25R while there are multiple VFR aircraft in the pattern. If not already done; install a radar repeater to allow LVK Tower to see traffic; which is beyond visual range.

Data retrieved from NASA's ASRS site as of April 2012 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.