"> LRIT (Long Range Identification & Tracking) - Equipment Database

LRIT (Long Range Identification & Tracking)

medium 3 models total

LRIT transmits ship identity, position and time to the flag state by satellite every six hours under SOLAS V/19-1; unlike AIS it broadcasts to nobody nearby, only to the flag state and, on request, port and coastal states, and it has no chart display on the bridge at all.

Read more — LRIT (Long Range Identification & Tracking) explained

What sets LRIT apart

LRIT is not a navigation instrument the bridge team reads — it is a reporting system that transmits a ship's identity, position and the time of that position to shore authorities automatically every six hours, with no chart display and no watchkeeping function on board. Unlike AIS, which broadcasts openly to any receiver in range, LRIT sends data only to the flag state and, on request, to port and coastal states, and it works globally by satellite rather than being limited to VHF range near the coast.

LRIT reporting chain
The shipborne LRIT unit takes a position fix from the GNSS antenna and reports it by satellite every six hours to an Application Service Provider, which passes it on to the flag state data centre and, on request, to a coastal or port state.

Main components

Shipborne transmitting equipment

A satellite communication terminal, typically Inmarsat-C or equivalent, configured to poll the ship's position from GPS and transmit identity, position and timestamp automatically at the required interval without operator action.

Application Service Provider (ASP)

The shore-based link between the ship's terminal and the flag state's data centre, handling the message format and routing rather than the raw satellite communication itself.

Data Centre and Data Distribution Plan

The flag state's LRIT Data Centre stores position reports and releases them according to a Data Distribution Plan that defines which coastal and port states may request the ship's data and under what conditions.

Regulations and class

LRIT is mandatory under SOLAS Chapter V, Regulation 19-1, for passenger ships, cargo ships of 300 gross tonnage and above on international voyages, and mobile offshore drilling units. The requirement is transmission of position at least every six hours, with the system able to be polled more frequently by the flag state. Class or a recognised organisation on the flag state's behalf verifies conformance testing was carried out and issues a Conformance Test Report, without which the certificate cannot be endorsed.

Typical faults

  • Terminal loses GPS input while the satellite link stays up — position reports transmit with stale or no coordinates, and the fault can go unnoticed on the bridge since there is no visible alarm on most integrations
  • Airtime subscription lapses — LRIT reporting stops even though the underlying satellite terminal is functioning normally for other traffic
  • Configuration reverted after a terminal software update — polling interval or destination address no longer matches the flag state's Data Distribution Plan
  • Conformance testing not repeated after equipment replacement — certificate becomes technically invalid even though the new terminal reports correctly

What to look for in a supplier

  • Confirmed conformance with the flag state's current LRIT Data Centre and Application Service Provider, since these vary and not every terminal integrates with every combination
  • Integration path that does not depend solely on the ship's other satcom terminal, to avoid a single point of failure for both routine communications and mandatory reporting
  • Support for remote reconfiguration if the vessel changes flag or ASP mid-life
  • Documented conformance test history available for inspection at survey

What LRIT is not

Because LRIT shares a satellite terminal category with other systems, it is sometimes confused with Ship Security Alert System equipment or with the vessel's general satcom package. It performs none of those functions — it exists solely to satisfy the SOLAS position reporting requirement, and disabling it, even temporarily, is treated by flag states as a reportable deficiency rather than a maintenance choice left to the master's discretion.

If LRIT stops reporting, do not assume it is a terminal fault before checking the airtime subscription status — a lapsed subscription is a more common cause than hardware failure and is invisible from the bridge until someone checks it.

3 manufacturers · 3 models

CLS (Collecte Localisation Satellites)

1
CLS (Collecte Localisation Satellites) LRIT Terminal
LRIT Terminal
Satellite LRIT · Navigation Data / Sensor · Satellite LRIT terminal
Technology
Satellite
Imo required
ja
Common Failures & Inspection Points
  • CLS data center dependency
  • Reporting interval compliance
  • Flag state registration
Service: CLS operates LRIT data center for many flag states.
Spare Parts: CLS (Collecte Localisation Satellites): Ersatzteile per Hersteller-Netzwerk. Lead time: 1-4 Wochen. Backup-Systeme an Bord pflichtgemäß.
Strengths
  • Direct integration with CLS’s global LRIT data centre – streamlined reporting to many flag states
  • Meets IMO mandatory LRIT requirements out‑of‑the‑box
  • Compact, bridge‑mounted unit with low power draw suitable for retrofit or new builds
  • Supports automatic position updates at configurable intervals (typically every 6 hours)
  • Provides a single‑point interface for both AIS and satellite communications
Weaknesses
  • Reliance on CLS data centre creates a single point of failure; outage can halt reporting
  • Strict reporting‑interval compliance may trigger non‑conformance if the terminal loses connectivity
  • Requires flag‑state registration with CLS, limiting flexibility for vessels that change registries frequently
  • Subscription and data‑service fees are managed exclusively through CLS, reducing vendor choice
  • Limited public technical documentation; integration support may depend on CLS service contracts
Typical Vessels: TankerContainer shipBulk carrierPassenger vesselOffshore supply vessel
Decision Guide: Choose if: you need a turnkey LRIT solution that is already linked to the CLS data centre, you operate vessels for flag states that have contracts with CLS, and you value a single‑vendor installation and support model. Avoid if: you require multi‑data‑centre redundancy, want the freedom to switch LRIT service providers, or your flag state does not recognise CLS as an approved LRIT operator.
Use Cases: The terminal is typically installed on ocean‑going merchant ships to satisfy IMO LRIT obligations, enable real‑time fleet tracking for security and maritime domain awareness, and provide flag states with continuous vessel position data for regulatory compliance and incident response.

Cobham (Sailor)

1
Cobham (Sailor) LRIT via Inmarsat-C
LRIT via Inmarsat-C
Inmarsat-C · Navigation Data / Sensor · Inmarsat-C
Technology
Inmarsat-C
Imo required
ja
Common Failures & Inspection Points
  • Inmarsat-C dependency
  • Message scheduling issues
  • Configuration errors
Service: Uses existing Inmarsat-C for LRIT — no additional hardware.
Spare Parts: Cobham (Sailor): Ersatzteile per Hersteller-Netzwerk. Lead time: 1-4 Wochen. Backup-Systeme an Bord pflichtgemäß.
Strengths
  • Leverages already installed Inmarsat‑C equipment – no extra hardware cost
  • Fully compliant with IMO LRIT regulations for vessels >300 GT
  • Low power consumption and proven reliability of the Inmarsat‑C network
  • Simple software integration into existing bridge systems
  • Automatic scheduled position reports reduce crew workload
Weaknesses
  • Entirely dependent on Inmarsat‑C availability – service outage halts reporting
  • Limited bandwidth can cause message scheduling delays in congested areas
  • Configuration errors are common if not set up by experienced personnel
  • Not suitable for vessels without an existing Inmarsat‑C terminal
  • Updates to the LRIT software may require downtime
Typical Vessels: TankerContainer shipBulk carrierPassenger vesselOffshore support vessel
Certifications: IMO LRIT complianceDNV class approval
Decision Guide: Choose if: the ship already has an Inmarsat‑C terminal, you need a cost‑effective way to meet IMO LRIT requirements, and you prefer a low‑maintenance software solution. Avoid if: the vessel lacks Inmarsat‑C, you require higher data rates or real‑time tracking beyond scheduled reports, or you cannot guarantee regular software updates.
Use Cases: The system is typically installed on commercial cargo ships, tankers and passenger vessels that already carry an Inmarsat‑C transceiver. It is used to automatically transmit position reports to the LRIT Data Centre at intervals defined by IMO, ensuring regulatory compliance while minimizing crew intervention.

Pole Star

1
Pole Star Purplefinder LRIT
Purplefinder LRIT
Satellite LRIT · Navigation Data / Sensor · Satellite LRIT/SSAS
Technology
Satellite
Imo required
ja
Ssas combined
ja
Common Failures & Inspection Points
  • Satellite subscription cost
  • Antenna placement
  • Configuration after flag change
Service: Combined LRIT and SSAS in one unit. Pole Star is major LRIT CSP.
Spare Parts: Pole Star: Ersatzteile per Hersteller-Netzwerk. Lead time: 1-4 Wochen. Backup-Systeme an Bord pflichtgemäß.
Strengths
  • Integrates LRIT and SSAS functions, reducing installation space and cabling
  • Single antenna solution simplifies mounting on vessels with limited deck space
  • Direct connection to Pole Star's CSP ensures seamless data subscription and service management
  • Meets IMO mandatory LRIT requirement for vessels >300 GT
  • Remote firmware updates and configuration via satellite link
Weaknesses
  • Higher ongoing satellite subscription cost due to combined services
  • Antenna placement is critical; poor location can degrade signal performance
  • Re‑configuration after a flag change may require vendor assistance and downtime
  • Limited flexibility if a ship later wants separate LRIT or SSAS providers
  • Potential compatibility issues with legacy bridge integration systems
Typical Vessels: Bulk CarrierContainer ShipTankerGeneral Cargo VesselOffshore Support Vessel
Decision Guide: Choose if: you need a compact, single‑vendor solution that satisfies both IMO LRIT and SSAS requirements and have limited bridge deck space. Avoid if: subscription cost is a primary concern, the vessel frequently changes flag state, or you prefer separate dedicated systems for greater vendor flexibility.
Use Cases: Commonly installed on new builds and retrofits of merchant ships >300 GT that operate worldwide and must comply with IMO LRIT obligations while also requiring SSAS capability for anti‑piracy/security alerts. Ideal where bridge space is at a premium and a single satellite antenna is preferred.