MDT TRACON Controller reported numerous conflicts occur between VFR aircraft not in communication with ATC and IFR aircraft on their final approach course. This is reportedly an ongoing issue and the reporter suggested the MDT airspace should be redesigned as a Class C.

Narrative

This issue is not about individual events; but about an unsafe condition that exists 100% of the time because it relates to airspace classification and adjacent airports. Please do not dismiss this report due to its length; and please understand that the workforce has all but stopped submitting reports on this issue because it's been so long since the issues were brought up.MDT is a level 7 Combined Tower with Radar/TRACON. The airport and surrounding airspace is Class Delta with an overlying TRSA. Although MDT is not as busy as some major airports in the US; there are several times during the day where commercial/corporate traffic is considerable; typically alternating between waves of IFR arrivals and departures. The traffic levels and passenger enplanements are well above the threshold for Class Charlie airspace; but the airport retains an outdated and inherently unsafe combination of Class Delta and TRSA airspace. The primary reason for this report aims to address the unsafe condition which exists at MDT created by the lack of Class Charlie airspace. MDT Class Delta airspace extends from the surface to 2;800 ft. with typical lateral dimensions. In addition; it is combined with the nearby CXY airport Class Delta airspace; which in itself creates a more complicated airspace structure in the area.It is not uncommon for VFR traffic in the vicinity of MDT to overfly the airport and surrounding areas at altitudes as low as 3;000 ft. some even to the very lowest they can to remain above the MDT Class Delta. This is particularly unsafe as MDT departures are vectored out of MDT with an initial climb to 3;000 ft. and these VFR aircraft are under no obligation to participate in the ATC system while in the overlying TRSA airspace. Not only that; but these same VFR targets will often unknowingly be on the MDT final approach path which can often extend to 15 miles at altitudes that are in direct conflict with arrival aircraft. This is again particularly unsafe as two way radio communication is not required of these aircraft which often leaves the Controllers and Pilots of MDT arrivals guessing at what these targets will do.There have been repeated TCAS RAs issued to aircraft that are departing from or arriving to MDT; even if the Controllers working at the time can identify the potential conflicts. The proximity of the IFR departures and arrivals to these non-participating VFR targets is unacceptable and risk prone; especially at an airport where the commercial/corporate traffic is predictably elevated at certain times of the day. In the best case scenario; IFR aircraft (including commercial traffic) is being held on the ground (or vectored off on approach) to avoid conflicts with traffic since ATC cannot be certain of its movement. In the worst cases; traffic in being put into a situation where evasive action is required to avoid NMAC proximity. The implications for traffic without a TCAS system is obvious; and serious. Other unacceptable results of this outdated airspace are unstable approaches; missed approaches; increased workload during critical phases of flight; and Traffic management initiatives being disrupted. If these disruptions were caused by UAS systems; this issue would have national attention and the most serious of responses; yet it's being caused by a clearly and easily preventable issue and no changes have been made. Class Charlie airspace would allow Controllers to predict and control the path and altitude of any aircraft that is transitioning this airspace; and prevent these uncontrolled airplanes from stopping departures; arrivals; and causing much larger aircraft from making abrupt evasive maneuvers. Pilots of the non-participating aircraft are also at risk; whether they are aware of their location or not. It may be deceptive to GA pilots and similar users who are looking at the sectional chart and seeing only Class Delta airspace when in reality MDT is far busier and has far more passenger enplanements than a large amount of already established Class Charlie airports in the NAS. This is particularly relevant on days where VMC prevails and a large increase in VFR flights occurs.So many airports that are far slower than MDT with far less commercial traffic have Class Charlie airspace; yet MDT does not. This issue has been reported; mandatory when the situation requires it; and voluntarily several times. Even if these events do not occur daily; we are trying to convey how easily a very dangerous situation could develop. We are always learning from the past in aviation; and in this case; the problem we are facing is not new; and has caused serious sometimes fatal incidents in other locations in the NAS. Once again; the recommendation is that Class C airspace be implemented at MDT. Steps have been taken in the past to make these changes; including a staff study; an Ad-Hoc airspace committee comprised of members of the public; and at every turn the parties have agreed that Class C airspace is needed asap. This issue exists every day; 100% of the time. Controller actions are preventing bigger issues from happening; but we are one mistake or one delayed controller/pilot response away from big issues.I do not wish to bog down the reporting system; but at the same time; it seems that not submitting anything is also not the correct action to take.