C310 pilot reported an near midair collision at 9;000 ft while on an IFR flight.

Narrative:

We were in cruise at 9000 feet on an IFR flight plan. We were talking to gray approach at the time. I recently had ads-B installed in my aircraft and I got a traffic target on my garmin 530W. It looked like it could be a conflict. I called gray approach and asked if they had target at my 12 o'clock. Took a little [time] to respond. My wife and I were both looking for the target. It got within 200 ft of our altitude and was pretty much head on. I was debating turning but I wanted to get a visual if I could to make a better decision. I was going 200 mph or so and the target was going like 240 knots according to my ipad so not much time to figure it out. I had my 530w traffic page set at 6 miles for this exact reason to catch them sooner. We got a visual on the target probably 1.5 miles out. They went under our right wing. We were south bound they were north bound. When they passed ads-B was alerting 300 ft separation but it had gotten to 200 ft.I complained to gray approach told them that was way closer than I liked. I am on an IFR flight plan for a reason; to get some more eyeballs looking out for me. The controller kinda blew it off and almost immediately handed me off to houston center. Even though I did not have to make an altitude change; I was aware of the situation and ready to do so because of ads-B traffic. Maybe the controllers were preoccupied or they were shorthanded or busy handing us off. Regardless; way too close for me and my family.

Original NASA ASRS Text

Title: C310 pilot reported an NMAC at 9;000 FT while on an IFR flight.

Narrative: We were in cruise at 9000 feet on an IFR flight plan. We were talking to Gray approach at the time. I recently had ADS-B installed in my aircraft and I got a traffic target on my Garmin 530W. It looked like it could be a conflict. I called Gray approach and asked if they had target at my 12 o'clock. Took a little [time] to respond. My wife and I were both looking for the target. It got within 200 ft of our altitude and was pretty much head on. I was debating turning but I wanted to get a visual if I could to make a better decision. I was going 200 mph or so and the target was going like 240 knots according to my iPad so not much time to figure it out. I had my 530w traffic page set at 6 miles for this exact reason to catch them sooner. We got a visual on the target probably 1.5 miles out. They went under our right wing. We were south bound they were north bound. When they passed ADS-B was alerting 300 ft separation but it had gotten to 200 ft.I complained to Gray approach told them that was way closer than I liked. I am on an IFR flight plan for a reason; to get some more eyeballs looking out for me. The controller kinda blew it off and almost immediately handed me off to Houston Center. Even though I did not have to make an altitude change; I was aware of the situation and ready to do so because of ADS-B traffic. Maybe the controllers were preoccupied or they were shorthanded or busy handing us off. Regardless; way too close for me and my family.

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.

Attributes
ACN	1330589
Time
Date	201602
Local Time Of Day	0601-1200
Place
Locale Reference	GRK.TRACON
State Reference	TX
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Cessna 310/T310C
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft Low Wing 2 Eng Retractable Gear
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Person 1
Function	Single Pilot Captain Pilot Flying
Qualification	Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 30 Flight Crew Total 430 Flight Crew Type 50
Events
Anomaly	ATC Issue All Types Conflict NMAC
Miss Distance	Horizontal 1500 Vertical 300