Narrative:

I was on an IFR flight plan at 10;000 ft on an airway in IMC conditions. I was talking to la center. The center controller called me as traffic to a tbm who was coming the opposite direction on the airway at a high rate of speed and descending rapidly. The tbm pilot responded that he was in IMC conditions and couldn't see me. Then the controller called out the tbm to me as traffic at my 12 o'clock and I also responded that I was in IMC conditions and couldn't see the tbm. The controller responded 'roger' and then went and read a long clearance to another aircraft without advising either the tbm or myself of the impending conflict nor requesting either one of us to take evasive action; deviate; climb; descend; stop descent; etc.I looked at my ads-B display and saw the tbm approaching me and it appeared that a collision would occur if I did not take evasive action. The controller was busy reading the long clearance; so after the tbm got to within 800 ft of me and my ads-B traffic alert went off; I rapidly turned 45 degrees left of course and it appeared I missed the tbm by less than 700 ft in IMC conditions. I advised the controller when he was done with the other plane's clearance of what had happened; and he had nothing to say. I have experienced this before; on IFR flight plans and in IMC conditions; where the controller seems to believe they have satisfied their duty of traffic separation by calling out traffic to aircraft in IMC; who can't possibly see and avoid anyone. Suggest playing the tapes and retraining.

Related reports:

Google
 

Original NASA ASRS Text

Title: PA-28 Pilot on an IFR flight plan reported being issued opposite direction traffic in IMC; but the Controller took no action to separate the traffic.

Narrative: I was on an IFR flight plan at 10;000 ft on an airway in IMC conditions. I was talking to LA Center. The Center Controller called me as traffic to a TBM who was coming the opposite direction on the airway at a high rate of speed and descending rapidly. The TBM pilot responded that he was in IMC conditions and couldn't see me. Then the controller called out the TBM to me as traffic at my 12 o'clock and I also responded that I was in IMC conditions and couldn't see the TBM. The controller responded 'roger' and then went and read a long clearance to another aircraft without advising either the TBM or myself of the impending conflict nor requesting either one of us to take evasive action; deviate; climb; descend; stop descent; etc.I looked at my ADS-B display and saw the TBM approaching me and it appeared that a collision would occur if I did not take evasive action. The controller was busy reading the long clearance; so after the TBM got to within 800 ft of me and my ADS-B traffic alert went off; I rapidly turned 45 degrees left of course and it appeared I missed the TBM by less than 700 ft in IMC conditions. I advised the controller when he was done with the other plane's clearance of what had happened; and he had nothing to say. I have experienced this before; on IFR flight plans and in IMC conditions; where the controller seems to believe they have satisfied their duty of traffic separation by calling out traffic to aircraft in IMC; who can't possibly see and avoid anyone. Suggest playing the tapes and retraining.

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.