Controller and pilot report of event where controller was thinking the aircraft was going to go to o...

Attributes
ACN	1170585
Time
Date	201405
Local Time Of Day	0001-0600
Place
Locale Reference	SCT.TRACON
State Reference	CA
Environment
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Other Instrument Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Transport Low Wing 2 Recip Eng
Flight Phase	Descent
Route In Use	Other Instrument Approach
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 7.5
Person 2
Function	Pilot Not Flying
Qualification	Flight Crew Commercial Flight Crew Instrument Flight Crew Flight Instructor
Experience	Flight Crew Last 90 Days 55 Flight Crew Total 1258.1 Flight Crew Type 54.7
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

Marginal VFR to IFR. Most aircraft landing at airports were on instrument approach. Two aircraft involved; aircraft X was cleared for VOR approach into okb (runway 6 / 24) and aircraft Y (awaiting IFR clearance for VOR approach into crq) was holding VFR over ocn VOR directly over aircraft X; I was waiting for proper separation before making aircraft Y IFR. Aircraft X started commencing approach into okb and was descending southeast bound out of 2;500 ft; I told aircraft Y that once they made it back around over the VOR I would have an IFR clearance for him into crq (I would of had divergence at that point). Aircraft Y was now south bound towards the VOR and once over the VOR I made him IFR and cleared him for the approach. I continued with scan because there were other aircraft on my frequency. When my scan got back to aircraft X he was out of position north of okb runway and turning right east to west towards the approach end of runway 24 and back into aircraft Y who was south bound towards crq. When I saw this I thought maybe aircraft X had lost control of his aircraft due to his position and his descent; then he over flew runway 24 and contacted me when he was upwind. Aircraft Y was at 1;600 ft and aircraft X was at 600 ft; so no separation was lost. I issued 'brasher warning' to aircraft X for possible pilot deviation. Basically the pilot was supposed to initiate a missed approach on runway 6 at okb; but decided to make his approach to runway 24 instead.recommendation would be to inform all pilots that when making an approach to a specific runway regardless if they are on a VOR approach; that pilot needs to follow the far and ensure they continue missed approach on the runway the commence their approach on.

Original NASA ASRS Text

Title: Controller and pilot report of event where Controller was thinking the aircraft was going to go to one runway while the pilot thought they were going to the other.

Narrative: Marginal VFR to IFR. Most aircraft landing at airports were on instrument approach. Two aircraft involved; Aircraft X was cleared for VOR approach into OKB (RWY 6 / 24) and Aircraft Y (awaiting IFR clearance for VOR approach into CRQ) was holding VFR over OCN VOR directly over Aircraft X; I was waiting for proper separation before making Aircraft Y IFR. Aircraft X started commencing approach into OKB and was descending southeast bound out of 2;500 FT; I told Aircraft Y that once they made it back around over the VOR I would have an IFR clearance for him into CRQ (I would of had divergence at that point). Aircraft Y was now south bound towards the VOR and once over the VOR I made him IFR and cleared him for the approach. I continued with scan because there were other aircraft on my frequency. When my scan got back to Aircraft X he was out of position north of OKB runway and turning right east to west towards the approach end of Runway 24 and back into Aircraft Y who was south bound towards CRQ. When I saw this I thought maybe Aircraft X had lost control of his aircraft due to his position and his descent; then he over flew Runway 24 and contacted me when he was upwind. Aircraft Y was at 1;600 FT and Aircraft X was at 600 FT; so no separation was lost. I issued 'Brasher Warning' to Aircraft X for possible pilot deviation. Basically the pilot was supposed to initiate a missed approach on Runway 6 at OKB; but decided to make his approach to Runway 24 instead.Recommendation would be to inform all pilots that when making an approach to a specific runway regardless if they are on a VOR approach; that pilot needs to follow the FAR and ensure they continue missed approach on the runway the commence their approach on.

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

Controller and pilot report of event where controller was thinking the aircraft was going to go to one runway while the pilot thought they were going to the other.