PA-46 Malibu Meridian
Air Traffic Control Fully Certified
Communication Breakdown; Situational Awareness
Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Air Traffic Control Issued New Clearance
Human Factors
I was working Local Control 1 with Runways 2R/2L active. A Cirrus was inbound with Approach Control at 4;000 MSL from the northwest transitioning north of the field to enter a right downwind for Runway 2R. A Meridian was inbound with Approach Control from the northeast at 4;000 MSL approaching the right downwind for Runway 2R. It appeared that the Meridian was being sequenced in front of the Cirrus. A VFR Beech Baron called me six miles southeast of the field inbound. Initially I told the Baron to reduce his speed so that I could sequence him behind the Meridian; but noticed that the Meridian was being vectored a bit further east of the airport. Therefore I told the Baron to keep his speed up and that he was number one for Runway 2R and cleared to land. After clearing the Baron; I noticed the Meridian take a turn to the north; I assumed Approach Control was spinning him for some unknown reason. A helicopter called and requested a west departure from the helipad; and I issued him a take off clearance.  That's when I looked back at the RACD and noticed the Meridian had not made a complete 360 degree right turn but instead was continuing on a northerly heading. The Meridian called me at this moment stating he was entering a left base for Runway 20R. The Meridian was pointed directly at the Cirrus inbound from the northwest about to turn a 4 mile right downwind for Runway 2R. I immediately issued a Traffic Alert to the Meridian regarding the Cirrus at his 11 o'clock; one and a half miles. I believe the Meridian was only 300 to 700 FT below the Cirrus; thereby having lost standard separation. The two aircraft targets appeared to merge as the Meridian passed under the Cirrus.  Realizing the pilot of the Meridian was headed to the wrong runway; my Ground Controller called Approach to obtain control of the Meridian for me and the request was approved. I provided suggested headings to the Meridian to route him back over the north end of the field to enter a left downwind for Runway 2L. About 2 minutes later; the pilot of the Meridian lined up on final for Runway 20R. I told him to break off his final for 20R and enter a left downwind for Runway 2L. The pilot replied he was lining up on final for Runway 20L. I immediately instructed the pilot to climb and maintain 2;500 MSL and turn right heading 270 so as to guide him to the left downwind for Runway 2L. Finally; the pilot of the Meridian entered the left downwind for 2L and landed. After asking Approach Control to review the tapes; the pilot was cleared for; and read back; the Visual Approach for Runway 2R.  Sometime between then time Approach switched the Meridian to Tower frequency and the time he checked on with me; an excessive amount of time to switch frequencies in my opinion; the pilot must have forgotten he was headed for Runway 2R and turned left downwind to base for Runway 20R. I can provide no recommendations because this was clearly a pilot deviation that resulted in less than standard separation. Perhaps if the Approach Controller had ensured that the Meridian had leveled at 3;000 FT as assigned before switching the aircraft to Tower frequency; then when he made the erroneous northerly turn he would have at least been 1;000 FT below the Cirrus when the targets merged and separation may not have been lost.
Tower Controller described a loss of separation event when traffic inbound to the pattern entered an opposite direction downwind.