Set up the Satcom Direct (Gogo) integration

KármánLogs connects directly to Satcom Direct, now part of Gogo, through its ADX (Aviation Data Exchange) platform. Once a tail is connected, you can pull its real OUT, OFF, ON, and IN times, block and flight time, and fuel burn straight from the aircraft's own datalink into a logbook entry. No timing by hand, no copying numbers off a trip sheet.

What you need

Before you start, line up three things:

• An ATP subscription in KármánLogs. The integration lives under Settings → Integrations, a section that only appears on the ATP plan.
• The aircraft set up on Satcom Direct with FlightDeck Freedom Datalink service. The movement data KármánLogs reads comes from that service, so the tail has to be provisioned for it by Gogo.
• An ADX account and three credentials for each tail: a Client ID, a Client Secret, and a Subscription Key.

ADX, Azure, and the app each label those credentials a little differently, so here is how they line up:

KármánLogs field	Also called	Where it comes from
Client ID	client_id	Issued per aircraft when Gogo activates ADX for the tail
Client Secret	client_secret	Issued per aircraft when Gogo activates ADX for the tail
Subscription Key	Primary (or Secondary) API access key	Your ADX profile, after you request API access

Step 1: Get your ADX credentials

1. Create an account on the ADX (Aviation Data Exchange) website.
2. Request your API access through the ADX site. Once it is issued, your Primary and Secondary access keys appear on your Profile tab to copy. Either one is your Subscription Key in the app.
3. Get your Client ID and Client Secret. These are tied to a specific aircraft and are issued when Gogo activates ADX services for that tail. If you do not see them on your account, request them from Satcom Direct support at support@satcomdirect.com.

These credentials are per aircraft. A flight department with three tails gets three sets.

Step 2: Enter your credentials in KármánLogs

1. First, make sure the aircraft already exists in your Aircraft list. The integration attaches credentials to a tail you have already added.
2. Go to Settings → Integrations → Satcom Direct.
3. Tap Add Aircraft Credentials.
4. Choose the aircraft these credentials belong to.
5. Paste the Client ID, Client Secret, and Subscription Key. Turn on Show Credentials if you want to confirm the paste came through clean, with no stray spaces.
6. Tap Save.

Repeat for each aircraft. Every tail keeps its own credentials.

Step 3: Test the connection

Next to each configured aircraft, tap Test. A green checkmark means both the login and the movement data feed are working. If it fails, the message points you at the part to fix:

What you see	What it means	What to do
OAuth failed, check Client ID, Client Secret, and Subscription Key	One of the three credentials is wrong or has a stray space	Re-paste from ADX and use Show Credentials to compare character for character
Movement API rejected the subscription key	The key logs in fine but is not entitled to movement data	Confirm you copied your ADX Primary or Secondary access key, not a key for a different ADX product
Movement API error, or no data for a provisioned tail	The tail is not set up for the ADX movement service	Ask Satcom Direct to provision FlightDeck Freedom Datalink for that aircraft

Step 4: Pull times into a flight

Once a tail tests green, there are two ways to bring its times in:

• From the dashboard. Add the Quick Add widget to your dashboard, then tap it. KármánLogs fetches the recent movements for your primary aircraft, each showing its OUT / OFF / ON / IN, block time, and flight time. Tap a flight to add it to your logbook.
• From the flight form. While adding or editing a flight, enter the aircraft, departure, and arrival, then tap Retrieve from Satcom (Gogo). The matching movement's times drop straight into the entry.

Either way, the entry is filled with the four times, block and flight time, and fuel burn where the aircraft reports it. If KármánLogs already has a scheduled or existing flight that matches, it offers to update that one instead of creating a duplicate.

Good to know

• It is not live. ADX returns a movement after it has been processed, not the instant you set the brake. If a flight you just finished is not there yet, give it a little time and pull again.
• Times are Zulu (UTC), the same basis the rest of your logbook stores.
• Light aircraft are already covered. For aircraft that are not on a Satcom Direct datalink, KármánLogs can still capture your OOOI times on-device from your phone's GPS, free on every plan. The Satcom Direct integration is the option for reading the times straight from the aircraft's own datalink, which is what most corporate and charter departments want across a fleet. See Automatic OOOI times for how the on-device option works.

Your credentials stay on your device

Your Client ID, Client Secret, and Subscription Key are stored in your device's Keychain and nowhere else. They are not synced to iCloud and are never sent to KármánLogs. The app uses them only to authenticate directly with Satcom Direct's ADX servers when you pull times. You can remove a tail's credentials any time from Settings → Integrations → Satcom Direct by tapping the trash icon next to it.