For sure a Faculty table with fields pertinent to the member. For track, I presume it is odd or even years only, so there's no need to worry about storing what year they'd attend. It would require unnecessary upkeep. That could be a yes/no field like EvenYear. I'd consider comparing the result of using the Mod function against the year in question and if it evaluates to 0 it is an even year so your query returns Yes members, otherwise it's an odd year so you return No members. If a member swaps, you update each to Yes/No accordingly.
tblRobeRental at minimum would need Member_FK (containing auto number or other type of unique member ID from tblFaculty). DateOut and DateIn could serve to track robes not returned (DateIn field would be Null).
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.