What do you mean?
Controllers are standalone classes that act as...well...conducting data between your entities / view models and the views.
You can always create a new instance of your model in another controller....but not sure about what you really want to do.

Or maybe you mean you don't want to hit the database twice doing exactly the same thing?
Just move the query out to a "repository class" and cache the method returning the data?

But as for actually using one controller action from another controller, you should not be able to do that (if you can, your controller have responsibilities it should not have)