Small Aircraft
Flight Crew Private
Flight Crew Last 90 Days 21; Flight Crew Total 370; Flight Crew Type 306
Communication Breakdown; Situational Awareness
ATC Issue All Types; Conflict Airborne Conflict
Flight Crew Took Evasive Action
Aircraft; Human Factors
While on a direct VFR flight from ZZZ to CAK I had a near miss with Aircraft Y approximately 14 miles west of CAK. I had established contact with CLE Approach; 20 miles out and received confirmation of radar contact and received a squawk code. At approximately 14 miles out (from the class C airspace) I sighted the other aircraft approaching from the southeast at near my altitude. It was less than 1/4 mile when I spotted it and immediately reduced power and began a fast descent to gain separation. I saw no reaction from the other aircraft. After I made initial contact with CLE Approach a squawk code was given to an aircraft flying from ZZZ1 to 3G3. I suspect this was that aircraft. I understand some transition will happen with the TRACON moving to CLE but in the [X] years I have operated out of CAK I have never have had traffic within the visual range that I haven't been warned about while in radar contact. It was a busy time on the radio but this should not have been missed. On a second note not related to this event but in the same control space. My partner in the same plane was contacting CLE Approach to enter the Class C space at CAK and was given a squawk code with the #8 in it. After telling ATC unable due to the #8 ATC then gave a second code with the #9 in it. After the second unable to comply the third code was finally compatible with the system.
Pilot reported an airborne conflict while on approach to CAK without being notified by ATC.