Why is the predicted ETA missing for some containers?

Why is the predicted ETA missing for some containers?

We understand the frustration that can arise when you're expecting a predicted ETA for your container from Portcast, but don't receive one. In this section, we'll outline some of the common reasons why you might not see a predicted ETA for the specific container:

• Early Container Stage: If the container is still in the early stages of its journey and the carrier hasn't finalized the entire route, including the assignment of the final vessel, Portcast might not be able to generate a prediction. This situation is particularly prevalent with carriers like MSC. Without information about the final vessel, predictive ETA cannot be provided by Portcast.
• Unpublished Final Vessel Schedule: In cases where the carrier hasn't published the schedule for the final vessel, Portcast won't have the necessary data to predict the ETA accurately.
• Lack of Long-Term Schedule: Certain carriers, including MSC, might not provide a long-term schedule, and the target port/POD (Port of Discharge) information might be missing from the schedule/rotation. This absence of critical data would lead to Portcast being unable to offer predictions.
• ATA/ATD Data from AIS: If Portcast has received Arrival Time (ATA) or Departure Time (ATD) data based on AIS (Automatic Identification System) information, regardless of what data the carrier might provide, Portcast will not generate predictions.
• Missing Vessel Metadata: In situations where Portcast lacks essential vessel metadata such as IMO number or vessel name, predictions might not be available. This can occur due to recent changes in vessel details or if a small vessel, not typically a container ship, is repurposed as a container ship. These issues will be addressed on a case-by-case basis, so please notify us if you encounter any instances of missing vessels.
• Data Mismatch and Inaccuracies: Discrepancies between the data published by the carrier and the actual vessel location can lead to prediction failures. Carriers might occasionally use incorrect port codes. While Portcast maintains mappings for previously observed discrepancies, new issues may arise if carriers use unrecognized port codes.

If you're experiencing a missing predicted ETA, we recommend checking if any of the aforementioned factors apply to your situation. Understanding these common issues will provide insight into why a predicted ETA might not be available for your container at a given time.