GAR, API, PNR and PNRGOV: What’s the Difference?

Introduction

If you operate aircraft into or out of the UK, you’ve probably come across several terms relating to passenger data reporting: GAR, API, PNR and PNRGOV.

They’re closely related, but they’re not interchangeable. API and PNR describe two different types of passenger information. PNRGOV is an international standard used to transmit PNR data to governments. GAR is a specific UK reporting framework for international general aviation flights.

Getting the distinction right matters, because the information required, how it’s transmitted, and the deadlines involved all depend on the type of operation, the route, and the requirements of the government on the other end.

This guide walks through what each term actually means and how they fit together.

---

The Short Version

Term	What it is	Typical source	Who it applies to
API (Advance Passenger Information)	Passenger and crew identity and travel document data	Captured from travel documents, usually at check-in	Commercial and charter airlines
PNR (Passenger Name Record)	Reservation and journey information created during booking	Held in the airline’s reservation system	Any airline with a booking/CRS system
PNRGOV	An international message standard for transmitting PNR data to governments	Sent ahead of departure or arrival	Airlines reporting to states that require PNR
GAR (General Aviation Report)	A UK reporting framework covering the flight, aircraft and everyone on board	Submitted 48 to 2 hours before departure	International general aviation operators

 

API tells authorities who’s travelling. PNR tells them about the journey they’ve booked. PNRGOV is how that PNR data actually gets to governments. GAR is the UK’s own reporting requirement for general aviation flights, and it happens to include API-type data as part of what it asks for.

---

What Is API?

Advance Passenger Information is identity and travel document data: full name, date of birth, gender, nationality, and travel document number and details. It’s pulled from the passenger’s travel document itself, typically during check-in or departure control.

The standards behind API were developed jointly by the World Customs Organization, IATA and ICAO, so passenger information can be exchanged consistently between carriers and border authorities worldwide.

In short, API answers one question: who is on this aircraft?

---

What Is PNR?

PNR is a different kind of data entirely. It’s created through the reservation process and collected primarily for the airline’s own operational and commercial purposes, not for border control.

A PNR record can include the passenger’s name, itinerary and flight segments, contact details, ticketing information, seat allocation, baggage details, travel agency information, and more, depending on how the booking was made and which systems were involved.

Where API identifies the traveller, PNR paints a fuller picture of their journey and how it was booked.

---

Where Does PNRGOV Fit In?

This is the part that trips people up. PNRGOV isn’t a third category of passenger data. It’s the internationally recognised message standard used to actually transmit PNR data from an airline’s systems to a government’s border agency.

It was developed jointly by IATA, WCO and ICAO, and where a government requires PNR data, PNRGOV is the standardised format that data gets sent in. API typically travels through separate messaging standards like PAXLST, so API and PNR remain distinct data streams even when a government asks for both.

For an airline operating internationally, the real challenge isn’t just collecting the right passenger information. It’s making sure that information is extracted, formatted correctly, and sent to the right authority at the right time, for every route and every regulatory regime you fly into.

This is exactly the layer PNRGOV.com is built around: automating the generation and transmission of PNRGOV messages so charter and scheduled operators aren’t managing this by hand. See our Charter Airlines and Scheduled Airlines pages for more on how that works.

---

So Where Does GAR Fit?

GAR sits in a different part of the landscape altogether. The General Aviation Report is a UK requirement for international general aviation flights, and owners, agents and captains have to submit specified information about the flight and everyone on board to UK authorities before they fly.

It has to be submitted no earlier than 48 hours and no later than two hours before the aircraft’s expected departure time, either through the UK government’s Submit a GAR service, an approved third-party application, or a direct system connection.

It’s worth being precise here: GAR isn’t simply “what general aviation operators do instead of API,” because they don’t have a reservation or departure control system to generate that data from. It’s its own UK reporting framework with its own rules, and the information it captures actually includes API-type data as one part of what it asks for. GAR and API aren’t separate concepts competing for the same job. GAR describes a reporting requirement; API describes a type of data, and GAR happens to ask for some of it.

For the full breakdown of GAR deadlines and penalties, see our UK GAR Explained guide.

---

Which One Applies to Your Operation?

For scheduled and charter airlines, governments may require API, PNR, or both, depending on the route and the destination state’s requirements. Where PNR transmission is required, PNRGOV is the standard used to send it.

For international general aviation flights to or from the UK, GAR is generally what applies.

The type of aircraft alone doesn’t settle the question. The nature of the operation, the route, and the regulatory regime all factor in, which is exactly where charter, business aviation, and mixed operations tend to get caught out.

---

The Bottom Line

API is passenger and crew identity data. PNR is reservation and journey data. PNRGOV is the standard used to transmit PNR data to governments. GAR is the UK’s own reporting framework for general aviation flights.

For operators, the real work is managing all of this across different governments, routes and regulatory regimes, each with its own formats and deadlines.

PNRGOV.com automates exactly that: validating, transforming and transmitting the right passenger data to the right authorities at the right time, across PNR, API, visa and sanctions requirements.

If you’re not sure which reporting requirements apply to your operation, get in touch with the PNRGOV.com team and we’ll walk through what applies to your routes and systems.

---

Contact Us