Narrative:

I was descending from 3500 ft MSL en route from 3DA (flushing, mi) to Y47 (new hudson, mi) when I saw a large twin engine, commuter type aircraft, high or shoulder wing, at about my 12:30 position on a near collision course. I banked sharply to the right, turned on my landing light and waggled my wings. He made no move, continued on as though he did not see me. His course estimated at 060 degrees magnetic compass and mine, before turning, was 170 degrees. He might have been going to the pontiac VOR (psi), he was headed that way. I was near V-133, just by coincidence. A solution to this problem would have been for me to have been in contact with detroit approach for VFR advisories. Another comment would be to be especially watchful when descending (or climbing) through 'hard altitudes' such as 3000 and 4000 and 5000 as the airliners and other IFR traffic will be at those altitudes, and in the area within 50 NM of detroit, and pontiac, we do have a lot of IFR traffic. I wonder if he was talking to detroit approach? I had my transponder on, and my mode C was (and is) operational as checked by flint departure approximately 10 or 15 mins before this incident. There was no violation of any FARS that I know of. I was VFR, he was in VFR conditions and I am reporting this only to point out a near miss and how it may have helped if I had been talking to detroit approach. They control the area where this incident occurred.

Related reports:

Google
 

Original NASA ASRS Text

Title: CLOSE PROX GA-SMA COMMUTER-MDT NEAR PSI VOR.

Narrative: I WAS DSNDING FROM 3500 FT MSL ENRTE FROM 3DA (FLUSHING, MI) TO Y47 (NEW HUDSON, MI) WHEN I SAW A LARGE TWIN ENG, COMMUTER TYPE ACFT, HIGH OR SHOULDER WING, AT ABOUT MY 12:30 POS ON A NEAR COLLISION COURSE. I BANKED SHARPLY TO THE R, TURNED ON MY LNDG LIGHT AND WAGGLED MY WINGS. HE MADE NO MOVE, CONTINUED ON AS THOUGH HE DID NOT SEE ME. HIS COURSE ESTIMATED AT 060 DEGS MAGNETIC COMPASS AND MINE, BEFORE TURNING, WAS 170 DEGS. HE MIGHT HAVE BEEN GOING TO THE PONTIAC VOR (PSI), HE WAS HEADED THAT WAY. I WAS NEAR V-133, JUST BY COINCIDENCE. A SOLUTION TO THIS PROBLEM WOULD HAVE BEEN FOR ME TO HAVE BEEN IN CONTACT WITH DETROIT APCH FOR VFR ADVISORIES. ANOTHER COMMENT WOULD BE TO BE ESPECIALLY WATCHFUL WHEN DSNDING (OR CLBING) THROUGH 'HARD ALTS' SUCH AS 3000 AND 4000 AND 5000 AS THE AIRLINERS AND OTHER IFR TFC WILL BE AT THOSE ALTS, AND IN THE AREA WITHIN 50 NM OF DETROIT, AND PONTIAC, WE DO HAVE A LOT OF IFR TFC. I WONDER IF HE WAS TALKING TO DETROIT APCH? I HAD MY TRANSPONDER ON, AND MY MODE C WAS (AND IS) OPERATIONAL AS CHKED BY FLINT DEP APPROX 10 OR 15 MINS BEFORE THIS INCIDENT. THERE WAS NO VIOLATION OF ANY FARS THAT I KNOW OF. I WAS VFR, HE WAS IN VFR CONDITIONS AND I AM RPTING THIS ONLY TO POINT OUT A NEAR MISS AND HOW IT MAY HAVE HELPED IF I HAD BEEN TALKING TO DETROIT APCH. THEY CTL THE AREA WHERE THIS INCIDENT OCCURRED.

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.