Show departure and arrival times in the right local time zone. Retrieve airport time zone identifiers alongside airport codes and names, or download the directory to support time conversion across your travel product.
Abbreviated response. The ellipsis (…) represents omitted fields and is not part of the actual JSON. The UTC offset shown is an example, not a year-round offset; use the time zone identifier and the travel date for conversion.
Use timezone with a date-aware time zone library to display local times. Keep airport identifiers alongside it so departure and arrival locations are mapped separately.
Field
Type
Example
Description
airhex_id
Identifier
53779
Permanent Airhex record identifier for maintaining your local airport directory.
iata
String
LHR
Three-letter airport code for matching departure and arrival locations.
icao
String
EGLL
Four-letter airport identifier for matching aviation data sources.
name
String
London Heathrow Airport
Airport name for itinerary and passenger-information displays.
timezone
String
Europe/London
Named time zone identifier. Use it with the relevant timestamp to determine local time.
utc
Offset
1
UTC offset supplied in the airport record. Do not treat it as a fixed offset for every travel date.
Export active airports with commercial flights as CSV and retain timezone alongside airhex_id and airport codes. Your application can then resolve the time zone for each itinerary leg from a local directory.
Use icao when your source identifies airports with four-letter codes. This request resolves EGLL to the same Heathrow record and time zone as an IATA lookup for LHR.
Display a supplied UTC timestamp in airport local time
After retrieving timezone, pass it to your application’s date-time formatter with an unambiguous timestamp from your flight supplier. This JavaScript example uses Europe/London from the response. The timestamp is illustrative; the Airports API does not supply flight times.
Display each end of a journey in its own airport’s local time, with dates that help travelers understand overnight trips.
Passenger reminders
Use airport time zones in your notification logic so departure reminders can be shown in the local context of the traveler’s journey.
Consistent support and reporting
Let support teams view flight timestamps in airport local time while your systems retain unambiguous timestamps for comparisons and reporting.
Frequently asked questions
What is the difference between timezone and utc?
timezone identifies a named zone, such as Europe/London. utc supplies an offset in the airport record. An offset alone does not describe daylight-saving rules or changes across dates. Use the named zone with the actual travel timestamp when converting times.
How should I handle daylight saving time?
Use timezone with a date-aware library backed by current time zone rules. The library determines the offset for the date being converted. Do not apply the example UTC offset to every flight, and keep your application’s time zone data current as rules can change.
Does the API convert flight times for me?
No. It returns airport reference data, including time zone identifiers. Your application performs the conversion using timestamps supplied by your flight provider. There is no travel-date or time-conversion parameter on this endpoint.
What if my supplier already sends local flight times?
Confirm the supplier’s timestamp format before converting. Do not interpret a local time as UTC or convert it twice. A local date and time without an offset can be ambiguous around daylight-saving transitions; use an explicit offset or UTC timestamp from the supplier when available.
How do I handle departure and arrival in different time zones?
Resolve each airport separately and format each timestamp using that airport’s timezone. Include the local date where a journey crosses midnight. Calculate elapsed journey time from unambiguous timestamps, rather than subtracting the displayed local clock times.
Can I assume all airports in a country use the same time zone?
No. Retrieve the time zone for the specific airport record rather than inferring it from the country. If you search by city_code or country_code, read timezone from each returned airport.
Can I store airport time zones in my own database?
Yes, with an appropriate GEO Essentials license. Export with dump=1 and choose JSON, XML or CSV using response_type. Retain airhex_id and updated from the full response, refresh your airport mappings periodically, and maintain current time zone rules in the software that performs conversions.
What should I do if a time zone is missing or unsupported?
Validate the returned timezone before passing it to your formatter. Preserve the supplier’s original timestamp and offset where available, and flag unresolved mappings for review. Do not silently substitute the user’s device time zone or a guessed country-wide offset.
Give travelers clear local times for every airport
Support consistent local-time displays across itineraries, reminders and passenger information, without maintaining your own airport-to-time-zone directory.
Explore the complete airport dataset, including IATA and ICAO codes, names, city and country identifiers, time zones, coordinates, operational status and contact details. View all request parameters, coverage filters and response fields, with individual lookups and bulk exports in JSON, XML and CSV.