IFR traffic near midair collision with VFR traffic.

Attributes
ACN	115973
Time
Date	198907
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : ocn
State Reference	CA
Altitude	msl bound lower : 5000 msl bound upper : 5000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : ont tower : dfw
Operator	general aviation : personal
Make Model Name	Small Aircraft
Flight Phase	cruise other cruise other
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	cruise other
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : commercial
Experience	flight time last 90 days : 25 flight time total : 1150 flight time type : 350
ASRS Report	115973
Person 2
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Events
Anomaly	conflict : nmac
Independent Detector	other flight crewa
Resolutory Action	flight crew : took evasive action
Consequence	other
Miss Distance	horizontal : 300 vertical : 0
Supplementary
Primary Problem	Ambiguous

Narrative:

I was tower en route from vny to riverside, ca. I had just heard another pilot report a near miss, 5 to 8 seconds later, found an small aircraft 300' in front of me, my altitude. Small aircraft dived hard, I banked steep right and climbed. Controller gave me a left turn as I was taking hard evasive action to the right. I refused the left turn once I was clear of the small aircraft. I was brisk with the controller when, in retrospect, I do not feel the situation was his fault. The problem is mixed VFR/IFR traffic in smoke/haze where the real visibility is 1/2-1 mi. I am frankly fed up with hearing 'traffic X O'clock, altitude unk.' mode C must be mandatory in the heavy ontario/los angeles corridor and WX called IFR when it is really below 3 mi. I was still 'rattled' enough to miss a runway 9 landing at riverside, and had to circle to 27 to land. This situation would have been prevented if VFR traffic was not released into IFR conditions.

Original NASA ASRS Text

Title: IFR TRAFFIC NMAC WITH VFR TRAFFIC.

Narrative: I WAS TWR ENRTE FROM VNY TO RIVERSIDE, CA. I HAD JUST HEARD ANOTHER PLT REPORT A NEAR MISS, 5 TO 8 SECONDS LATER, FOUND AN SMA 300' IN FRONT OF ME, MY ALT. SMA DIVED HARD, I BANKED STEEP RIGHT AND CLIMBED. CTLR GAVE ME A LEFT TURN AS I WAS TAKING HARD EVASIVE ACTION TO THE RIGHT. I REFUSED THE LEFT TURN ONCE I WAS CLEAR OF THE SMA. I WAS BRISK WITH THE CTLR WHEN, IN RETROSPECT, I DO NOT FEEL THE SITUATION WAS HIS FAULT. THE PROBLEM IS MIXED VFR/IFR TFC IN SMOKE/HAZE WHERE THE REAL VISIBILITY IS 1/2-1 MI. I AM FRANKLY FED UP WITH HEARING 'TFC X O'CLOCK, ALT UNK.' MODE C MUST BE MANDATORY IN THE HEAVY ONTARIO/LOS ANGELES CORRIDOR AND WX CALLED IFR WHEN IT IS REALLY BELOW 3 MI. I WAS STILL 'RATTLED' ENOUGH TO MISS A RWY 9 LNDG AT RIVERSIDE, AND HAD TO CIRCLE TO 27 TO LAND. THIS SITUATION WOULD HAVE BEEN PREVENTED IF VFR TFC WAS NOT RELEASED INTO IFR CONDITIONS.

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