> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-6.8/voyage-management-system/step-by-step-guides/vessels/find-vessel-voyages-and-port-calls.md).
# Find Vessel Voyages and Port Calls
In the "Voyages & Port Calls" section of the vessel drawer you will find the most import information about a vessel and its voyages.
### Vessel Details
The "Vessel Details" section shows data about the vessel such as DWT summer/tropical and immersion. Click **Expand**
to show contact information for the vessel.
### Voyages
This is a list of voyages on the opened vessel, sorted by newest first. If there is an ongoing voyage (end date in the future) in the list, it is indicated with a blue marker on the left side. When clicking the reference number of the voyage, the voyage drawer will then open. If the voyage does not have a reference number, a text value displaying 'Missing' will show instead. This is also clickable and will ope n the selected voyage.
Clicking on the voyages will list all port calls of the voyage below. Clicking on port calls in the list opens them in a panel where you can make changes.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dataloy.com/release-6.8/voyage-management-system/step-by-step-guides/vessels/find-vessel-voyages-and-port-calls.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.