All aircraft in MSFS have unique names. All they need to do is make sure the selected filter respects that unique aircraft name, so only missions available for aircraft with that exact name will show.
That still doesn’t tell you where it is on the world map it is situated.
I prefer to pick the most financially rewarding mission and then find the nearest say, pc24.
The filter functions in this manner already.
You appear to be assuming that what you see in the EFB before you [Accept Mission] is telling you what plane it is for or somehow limiting you. It does not, it’s irrelevant, just because the EFB shows a Diamond or a Cessna or whatever (as per your screenshot) before aircraft selection does not mean you cannot then select any compatible plane to do that mission.
Why does it show a Cessna when I have the filter set to show only the Vision Jet?
Once a different aircraft appears on the mission, it automatically creates issues for those of us using cockpit setups. SPAD.neXt, GlassOut, and other addons get confused by the wrong aircraft being loaded or displayed.
Sometimes, after I accept the mission, it changes back to the Vision Jet, but not always. Even when it does change to the Vision Jet after accepting, I still have to readjust most of my addons because they already loaded or reacted based on the wrong aircraft.
The aircraft filter should respect the selected aircraft from the beginning, so only missions for that specific aircraft appear.
The filter shows missions that are compatible for the given aircraft, that’s it. If you want the EFB to show the aircraft in the filter, that would also require that the filter only allow for one aircraft at a time.
This is another example as I’ve pointed out above of users simply misunderstanding the purpose of the filter - it is not a bug, it is (from your perspective) a missing feature.
At that point you’ve only filtered a list of missions, not actually selected a mission or transferred and selected an aircraft.
It’s a multiselect filter, you can choose several different aircraft models, and/or combinations of aircraft and specialisations, and the filter names are groupings, some represent all variants (cargo, passenger etc). This means there is no clear logical path through that filter to one selected aircraft, but the actual issue is third party add-ons being able to adapt to the aircraft changing.
The only one I use frequently is little navmap and that syncs the correct information from the API as soon as the flight loads it’s actually doing it the second it changes in the aircraft selector, career or free flight. I can’t speak to SPAD or the others, but if they are collecting information for configuration at the world map and not being able to adapt it’s too early - it will never be valid until the aircraft has actually been selected.
Someone more familiar with SPAD might know.
EDIT
Right - testing what I can see here with little navmap (which reads the Simulator Aircraft).
Career - when I click on a mission bubble, there is an aircraft in the EFB before selection, and little navmap picks it up in the ‘simulator aircraft’ data. I think they are associated with mission generation.
What this doesn’t do though is stop me selecting any possible aircraft, including the twin pioneer (that I had in the filter), so it’s noise/nuisance data that shouldn’t really be displayed to the user BUT it’s not stopping me from selecting the aircraft I intend to use.
When I do change it the ‘Simulator Aircraft’ is changed and little navmap shows the updated selection straight away. As I said, I don’t know how SPAD or the others sense the selected aircraft but aside from the EFB abberation mentioned, the filter is working correctly, and simvar that tells us what aircraft is selected is also changing as expected.