Skip to content

LILY ANNE

Tug · United States · AIS Class A

IMO8987113MMSI368420770Call signWDQ3886Last AIS position Oct 5, 2026, 16:25 UTC

In short

LILY ANNE (Tug, United States flag) was last seen on AIS on , under way at 4.2 kn, near Port Chester (North Atlantic Ocean). Its crew-entered AIS destination is NEW YORK HARBOR; its reported draught is 3.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 12:33 UTC).

Current voyage: from Tottenville, Staten Island (departed Oct 5, 2026, 08:27 UTC) to NEW YORK HARBOR

Vessel type
Tug
Year built
—
Gross tonnage
—
Size (length × beam)
24 m × 9 m
Registered owner
—

Watch this ship

Get an email when LILY ANNE arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

Free forever. No card. A free account follows up to 5 ships and ports.

Last reported position

received
Position
41.0786° N, 73.8805° W
Area
North Atlantic Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
4.2 kn
Course
354°
Heading
357°
41.0786° N, 73.8805° W
Open the full live map →

Last 30 days: 7 port calls (Tottenville, Staten Island, Bayonne, Brooklyn/New York, and Port Newark).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
LILY ANNE
IMO numberWhat is an IMO number?
8987113
MMSIWhat is an MMSI?
368420770
Call signWhat is a call sign?
WDQ3886
Vessel type
Tug
AIS ship type
Towing
Length overall
24 m
Beam
9 m
Year built
—

A tag next to a value names the register that supplied it (hover or tap it for the record and date). Values without a tag come from the ship's own AIS broadcasts or from Wikidata. Position and identity are derived live from AIS.

Ownership & management

Each line shows where the fact comes from. Links backed by an identifier point to the company page.

No owner, operator or manager is recorded for this vessel yet.

Timeline

Dated events for this ship from every source Voydar holds, newest first. Each line names its source; derived items say how they were derived.

DateEventSource
Left Tottenville, Staten IslandAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Tottenville, Staten IslandAIS-detectedVoydar port-call detector (AIS geofence)
Left BayonneAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BayonneAIS-detectedVoydar port-call detector (AIS geofence)
Left Brooklyn/New YorkAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Brooklyn/New YorkAIS-detectedVoydar port-call detector (AIS geofence)

Owner, operator and manager changes found by comparing yearly EU MRV reports are dated to the reporting year ("during 2025"), not to a day. Port calls here are the most recent only; the full lists are further down.

Incidents & investigations Authority-reported

Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.

  • Occurred Sep 17, 2018ACC · Towing/BargeNTSB marine investigations (CAROL)Stamford, CT, USA

    Seeley / Sea Jay / WEEKS 207, Stamford, CT, USA (NTSB DCA18FM039)Report published Nov 7, 2019

    …..was the mates poor decision in attempting the tripping maneuver so close to the marina piers instead of waiting to attempt the maneuver just slightly to the north in the turning basin which was wider and more forgiving if the maneuver was unsuccessful.

Source: NTSB marine investigations (CAROL). Courtesy: National Transportation Safety Board. Licence: US Government work (17 U.S.C. §105), public domain.

Port calls

Two kinds of evidence, kept apart: calls Voydar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Tottenville, Staten Island USTTVOct 5, 2026, 06:55 UTCOct 5, 2026, 08:27 UTC1 h 32 min
Bayonne USBAYOct 3, 2026, 19:31 UTCOct 3, 2026, 21:18 UTC1 h 47 min
Brooklyn/New York USBOYOct 2, 2026, 04:23 UTCOct 2, 2026, 08:15 UTC3 h 52 min
Brooklyn/New York USBOYSep 29, 2026, 22:10 UTCSep 30, 2026, 11:57 UTC13 h 47 min
Bayonne USBAYSep 28, 2026, 12:47 UTCSep 29, 2026, 03:59 UTC15 h 12 min
Port Newark USPNJSep 15, 2026, 13:01 UTCSep 17, 2026, 17:47 UTC2 d 4 h
Port Newark USPNJSep 12, 2026, 19:06 UTCSep 15, 2026, 12:59 UTC2 d 17 h

Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.

Frequently asked questions

Where is LILY ANNE now?
LILY ANNE (Tug, United States flag) was last seen on AIS on Oct 5, 2026, 16:25 UTC, under way at 4.2 kn, near Port Chester (North Atlantic Ocean). The crew-entered destination was NEW YORK HARBOR (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 12:33 UTC). This report does not confirm the ship’s current route.
What kind of ship is LILY ANNE?
LILY ANNE is a tug sailing under the flag of United States. The vessel is 24 m long with a beam of 9 m.
What sanctions and inspection records does Voydar hold for LILY ANNE?
Voydar has no matched sanctions record displayed for LILY ANNE from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels, the New Zealand Russia Sanctions Register and the French national asset-freeze register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for LILY ANNE. Missing records do not establish whether the ship has been detained.

Use this data

This page is also available as JSON, free, with the source and licence of every section. Sections whose sources do not permit redistribution are listed as withheld.

GET /api/v1/vessels/8987113
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using this data in code?

Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro adds internal business use; API plans add building the data into your own products.

See plans