Near midair collision between a beech jet 400A and an MU2 at 1800 ft AGL 5 NM east of ptk, mi.

Attributes
ACN	551755
Time
Date	200206
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : ptk.airport
State Reference	MI
Altitude	msl bound lower : 2500 msl bound upper : 3000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	MU-300 Diamond 1/1A
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Flight Plan	None
Aircraft 2
Controlling Facilities	tracon : d21.tracon
Make Model Name	MU-2 Undifferentiated or Other Model
Person 1
Affiliation	other
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : commercial
Experience	flight time last 90 days : 40 flight time total : 1600 flight time type : 6
ASRS Report	551755
Person 2
Affiliation	other
Function	flight crew : first officer
Events
Anomaly	conflict : airborne critical non adherence : far non adherence : required legal separation other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : took evasive action
Miss Distance	horizontal : 500 vertical : 500
Supplementary
Problem Areas	Aircraft Airspace Structure Environmental Factor Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Departed 7d2 on a sales demonstration flight. En route to flint, mi (fnt). Realized that we may be getting too close to pontiac's airspace (ptk) so called up the airspace information on the garmin GNS 530 map to see if we had violated the class D. Garmin showed that we were right on the edge of the class D ring, so I turned about 90 degrees to the right to direct our plane away from the airspace. I failed to see the traffic off our right, until he was under us about 500 ft. I think he may have descended to avoid us but am not sure. Events contributing to possible airspace violation and close proximity to airborne traffic include -- 1) GPS map not set up to show airspace rings at scale selected. I am very familiar with the garmin GNS 530 but did not realize this feature had been de-selected. 2) abrupt change of direction to depart the class D airspace, or prevent the actual incursion put us in the path of other airborne traffic. I may have scanned the area more thoroughly if not concerned with a potential airspace violation. 3) MU2 close by.

Original NASA ASRS Text

Title: NMAC BTWN A BEECH JET 400A AND AN MU2 AT 1800 FT AGL 5 NM E OF PTK, MI.

Narrative: DEPARTED 7D2 ON A SALES DEMO FLT. ENRTE TO FLINT, MI (FNT). REALIZED THAT WE MAY BE GETTING TOO CLOSE TO PONTIAC'S AIRSPACE (PTK) SO CALLED UP THE AIRSPACE INFO ON THE GARMIN GNS 530 MAP TO SEE IF WE HAD VIOLATED THE CLASS D. GARMIN SHOWED THAT WE WERE RIGHT ON THE EDGE OF THE CLASS D RING, SO I TURNED ABOUT 90 DEGS TO THE R TO DIRECT OUR PLANE AWAY FROM THE AIRSPACE. I FAILED TO SEE THE TFC OFF OUR R, UNTIL HE WAS UNDER US ABOUT 500 FT. I THINK HE MAY HAVE DESCENDED TO AVOID US BUT AM NOT SURE. EVENTS CONTRIBUTING TO POSSIBLE AIRSPACE VIOLATION AND CLOSE PROX TO AIRBORNE TFC INCLUDE -- 1) GPS MAP NOT SET UP TO SHOW AIRSPACE RINGS AT SCALE SELECTED. I AM VERY FAMILIAR WITH THE GARMIN GNS 530 BUT DID NOT REALIZE THIS FEATURE HAD BEEN DE-SELECTED. 2) ABRUPT CHANGE OF DIRECTION TO DEPART THE CLASS D AIRSPACE, OR PREVENT THE ACTUAL INCURSION PUT US IN THE PATH OF OTHER AIRBORNE TFC. I MAY HAVE SCANNED THE AREA MORE THOROUGHLY IF NOT CONCERNED WITH A POTENTIAL AIRSPACE VIOLATION. 3) MU2 CLOSE BY.

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.