My suggestions:

1) Create groups (either AD security or SharePoint) for A, B, and C

2) Create all calendar  items in a single  list, and use item level
security to secure access to individual items as needed

3) Instead of having multiple  calendars, use a single one and let
the security trimming (or possible audience targeting to the groups
depending on your specific  requirements) determine what is displayed to
the users.

I suppose I need to add a bit of clarity to what I have already done,
in order to possibly get some input on things, in order to finish
this project and get it off my plate.
The first of which is:
The Staff (invididuals inserted into the calendar  at specific  times),
is drawn from a 3rd party program called fundraiser. It's taken into
a csv and imported into sql  05. Specific information is pulled from
the tables/cells into sharepoint and inserted intot he calendar.

AD is also set up and used allowing the individuals to login to the
sharepoint. They are part of groups, although we have not yet
grouped them in AD or sharepoint as of yet.

When the user logs in, the client wants them to have a default view
of the calendar with very specific rights to other views, or not.

I have a single  calendar set up and have created the views which show
specific users, and catagories of of users, with a link to the
individual to edit the information beyond just whats shown in the
calendar such as time in - out, specialty.

Some users are supposed to be granted rights to see all the views,
and some users are supposed to have access to only one or two views,
and thats all they want them to be able to see on their individual
list of views.

All the data  is updated  in the fundraiser, so editing backwards is
not a part of this release.

The users/staff are entered into the calendar as events.

Perhaps this additional information will help get more input.

many Thanks in advance for any feedback, assistance, input, ideas,
etc...