BE33 pilot had an near midair collision in ndt class east airspace.

Attributes
ACN	494910
Time
Date	200012
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : cma.vor
State Reference	CA
Altitude	msl single value : 4000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Bonanza 33
Operating Under FAR Part	Part 91
Navigation In Use	other vortac
Flight Phase	descent : approach
Route In Use	approach : visual arrival : on vectors
Flight Plan	IFR
Aircraft 2
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Route In Use	enroute : direct
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : commercial pilot : instrument pilot : multi engine
Experience	flight time last 90 days : 34 flight time total : 3918 flight time type : 2960
ASRS Report	494910
Person 2
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : private
Events
Anomaly	conflict : nmac non adherence : published procedure non adherence : far other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 100 vertical : 50
Supplementary
Problem Areas	Flight Crew Human Performance FAA Airspace Structure
Primary Problem	Flight Crew Human Performance

Narrative:

On dec/xa/00, I filed an IFR flight plan from cno to cma, assigned altitude 6000 ft (socal approach), then I was xferred to point mugu approach. Point mugu assigned a 4000 ft altitude. While stabilized at 4000 ft, point mugu advised to maintain 4000 ft and contact cma tower upon reaching cecee intersection. Tracking inbound on the 247 degree radial to cma, I had not reached cecee intersection, when an aircraft heading northeast just missed my tail. I reported this to the controller, and he said the only traffic he saw was about 2 mi northeast of my location. He also stated that at that altitude they don't see traffic. When I returned from the flight, I called and talked to the point mugu supervisor. He told me he was going to look into the tapes and radar information. This was reported to him on dec/xa/00. The day was VFR. I still like to file IFR because of the extra safety margin on an IFR flight plan. I believe the controller was negligent and failed to advise me of the approaching traffic at 4000 ft MSL, assigned altitude, established on the 247 degree radial tracking inbound to cma. This is an instrument approved procedure published for the cma airport. How can he say to me that, at that altitude, he can't see traffic?

Original NASA ASRS Text

Title: BE33 PLT HAD AN NMAC IN NDT CLASS E AIRSPACE.

Narrative: ON DEC/XA/00, I FILED AN IFR FLT PLAN FROM CNO TO CMA, ASSIGNED ALT 6000 FT (SOCAL APCH), THEN I WAS XFERRED TO POINT MUGU APCH. POINT MUGU ASSIGNED A 4000 FT ALT. WHILE STABILIZED AT 4000 FT, POINT MUGU ADVISED TO MAINTAIN 4000 FT AND CONTACT CMA TWR UPON REACHING CECEE INTXN. TRACKING INBOUND ON THE 247 DEG RADIAL TO CMA, I HAD NOT REACHED CECEE INTXN, WHEN AN ACFT HDG NE JUST MISSED MY TAIL. I RPTED THIS TO THE CTLR, AND HE SAID THE ONLY TFC HE SAW WAS ABOUT 2 MI NE OF MY LOCATION. HE ALSO STATED THAT AT THAT ALT THEY DON'T SEE TFC. WHEN I RETURNED FROM THE FLT, I CALLED AND TALKED TO THE POINT MUGU SUPVR. HE TOLD ME HE WAS GOING TO LOOK INTO THE TAPES AND RADAR INFO. THIS WAS RPTED TO HIM ON DEC/XA/00. THE DAY WAS VFR. I STILL LIKE TO FILE IFR BECAUSE OF THE EXTRA SAFETY MARGIN ON AN IFR FLT PLAN. I BELIEVE THE CTLR WAS NEGLIGENT AND FAILED TO ADVISE ME OF THE APCHING TFC AT 4000 FT MSL, ASSIGNED ALT, ESTABLISHED ON THE 247 DEG RADIAL TRACKING INBOUND TO CMA. THIS IS AN INST APPROVED PROC PUBLISHED FOR THE CMA ARPT. HOW CAN HE SAY TO ME THAT, AT THAT ALT, HE CAN'T SEE TFC?

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.