Trudy: Manzanillo access and terminal schedules require separate recovery checks

Intelligence question & baseline

Has Trudy moved from forecast exposure to a documented constraint on Manzanillo container movements, and what must users verify before resumption?

Approved review e117089e-c980-4d9c-bcee-6d7e3f7cfac9, decided 13 October 2026 22:31 UTC: forecast exposure based on NHC Advisory 1; no closure established in that snapshot. Current source fingerprint reflects a green GDACS humanitarian classification.

Finding beyond the lead source

Dated COPOMA notices add reported access restrictions and non-uniform terminal schedules beyond the forecast-only baseline. Recovery is a multi-gate coordination problem; no current port-wide reopening or realised congestion is verified. [access, ssa, contecon, maersk]^[4][5][6][7]

Decision affected & alternative explanation

Port agents, carrier operations teams and container cargo/appointment planners. · Confirm both fresh harbour movement permission and the relevant terminal/gate service before committing to a recovery slot; do not infer network-wide delay or reopening. [access, ssa, contecon]

Alternative explanation · The notices may be precautionary, partly superseded or not fully executed; a westward track and forecast weakening may reduce later exposure. Old homepage indicators do not resolve that alternative. [nhc-disc, dashboard]

Revise the judgment when · A dated superseding harbour order plus terminal execution/appointment confirmation would establish recovery; named missed calls, queue times or cargo-release records would quantify disruption. No such results were retrieved.

What we learned

The new finding is that recovery has several distinct gates: permission for vessel movements, terminal handling and landside appointments. COPOMA's SSA notice makes resumption dependent on authority approval, while its Contecon notice retains some appointments and makes later availability conditional. Treating either a weather improvement or a published reopening target as restoration of the whole container chain could therefore misalign a ship call with cargo availability. The 13 October approved review established only forecast exposure, with no closure evidenced then. [access, ssa, contecon, maersk, baseline] NHC's EP212026 series also resolves the earlier Twenty-One-E/Trudy naming uncertainty. [baseline, name-series]

Maritime implication

For port agents, carriers and cargo planners, obtain a fresh harbour-authority movement decision and a terminal-specific appointment/cargo-release confirmation before relying on a recovery slot. Keep the published local times as stated: no timezone conversion or realised completion is established here. These are planning checks, not a navigation clearance, evidence of missed sailings or a measured backlog. [access, ssa, contecon, maersk]

A dated warning, not a humanitarian all-clear

Analytical inference · The current GDACS source and the NHC warning answer different questions. The former classifies humanitarian impact; the latter identifies a dated coastal wind hazard. Forecast weakening cannot certify safe approaches. [source, nhc19a, nhc-disc]^[1][2][3]

Recovery has separate sea and landside gates

Analytical inference · The COPOMA notices distinguish harbour access, SSA handling/gate cut-offs and Contecon appointments. Some activity was retained while other functions were scheduled to stop; a port-wide binary status loses that operational distinction. [access, ssa, contecon]^[4][5][6]

Analytical inference · The Maersk notice gives a Monday gate target, whereas Contecon's Monday appointments are conditional. These are different scopes, not conflicting proof of one port reopening time. [maersk, contecon]^[7][6]

Analytical inference · An additional trade summary gives an earlier TEC import cut-off than COPOMA. This unresolved scope/time discrepancy reinforces the need for terminal-specific original instructions, not selection of the more convenient summary. [ssa, cutoff-discrepancy]^[5][11]

Verify recovery before converting it into a service promise

Analytical inference · Cargo planners need an effective movement order and confirmation from the terminal serving their shipment. Old dashboard values and scheduled restart dates cannot establish an available connection or a realised delay. [access, ssa, contecon, maersk, dashboard]^{[4][5][6][7][10]}

Business conclusions for maritime intelligence

Analytical inference · For container users, the evidenced dependency is coordination across access and cargo-service permissions. A weather improvement alone does not establish that a booked call and a landside release can be synchronised. [access, ssa, contecon]^[4][5][6]

Confidence & evidence limits

MODERATE · NHC's indexed official advisory supports the dated warning; COPOMA provides accessible operational notices and the port authority's directory identifies it as the port community. However, the authority/terminal notices are relayed through one publisher, not independently verified signed originals. Current reopening, actual execution and cargo-delay measurements remain unconfirmed. [nhc19a, access, ssa, contecon, directory]

Evidence & analytical reasoning

Reported · NHC Advisory 19A, valid 18 October 0600 UTC, retains the Manzanillo–Cabo Corrientes hurricane warning; expected later weakening is a forecast. [nhc19a]^[2]

Reported · COPOMA relays a 16 October vessel-access restriction and different terminal/cargo schedules; their stated times are not proof of current execution. [access, ssa, contecon, maersk]^[4][5][6][7]

Analytical inference · Vessel movement permission and landside cargo availability must be checked separately; one published resumption time cannot establish port-wide recovery. [access, ssa, contecon, maersk]^[4][5][6][7]

Analytical inference · GDACS's humanitarian colour and COPOMA dashboard figures from 12 October cannot establish current marine safety or terminal availability. [source, dashboard]^[1][10]

Analytical inference · The NHC Twenty-One-E and Trudy bulletins share cyclone identifier EP212026; this is a naming progression, not two cyclones. [baseline, name-series, nhc19a]^[9][12][2]