How to use it

One question, answered from what Elite last wrote about the carrier.

1 Own a fleet carrier and let it write a status once.

Open the carrier management screen in Elite once.

Elite writes a carrier status, and D47 then has your fuel, cargo, balance, jump range and services.

carrier report Ask Nothing to set up. Open the carrier management screen once and D47 has the figures. Fuel, cargo, balance, jump range and every service come from the same screen.

2 Ask any of the ways in.

Say "how is my carrier", "carrier fuel" or "carrier services".

D47 reads the figures with no language model involved.

how is my carrier carrier report · carrier status · carrier services · carrier fuel Any of these reaches the same tool with no model in the loop.

3 Select the captain, then use the comms key.

Say "comms captain", then hold the comms push-to-talk and say "how much fuel have we got".

The captain answers, and answers every comms question while the captain stays selected.

how much fuel have we got Comms key CARRIER · CAPTAIN answers every comms question while selected. Push-to-talk still reaches the core, even when you start with "Captain". More than 500 light years away, the core says the carrier is out of range.

! The one that stops people.

Note the date the figures were reported before you rely on them.

Fuel, cargo and balance each carry the date they were reported.

Figures are only as fresh as the last time you opened the screen. Fuel, cargo and balance carry the date they were reported, because the carrier keeps working while you are away.
Why it works this way

The carrier's own figures, apart from "where is it".

1 "Where is my carrier" and "how is my carrier" are different questions.

"where is my carrier" system, and when that was last seen "how is my carrier" fuel, cargo, balance, jump range, services Kept apart so a short question does not answer with everything it did not ask for.

2 The figures come from one journal event, and it only writes when you look.

CarrierStats fuel · cargo · balance · jump range · docking access · services Elite writes it when the carrier management screen opens, not continuously. A report says how old its own figures are rather than pretending they are live.

3 No carrier known is not the same as no carrier.

"I have not seen you own a fleet carrier this session." Not "you have no carrier" — D47 only knows what the journal has shown it.

4 The captain keeps a separate conversation, and the core overhears it.

Captain own brief, own transcript core hears each exchange as overheard The captain never answers as the core, and the core can still refer to what was said.

The details

The fleet carrier’s own figures, apart from its position — get_fleet on the Journal page answers where it is.

Ask for it

“carrier report” “carrier status” “how is my carrier” “carrier services” “carrier fuel”

Fleet carrier Sacred Fire (BNH-T2F) is in Fixture Nebula Point, as of 2026-09-05 00:00 UTC.
Fuel 792 t, as of 2026-09-05 00:00 UTC.
Cargo 540/25000 t (2% full), as of 2026-09-05 00:00 UTC.
Balance 750,352,669 cr.
Jump range 500 ly.
Docking access: all.
Services:
  BlackMarket: not bought
  Refuel: open, staffed by Rosa Guthrie
  Repair: closed, staffed by Ev Chang

Talk to the captain

“comms captain”, then on the comms key: “how much fuel have we got”

With the Carrier comms channel selecting the captain, what you say on the comms push-to-talk goes to the carrier’s captain instead of the core, and is spoken in the captain’s voice. The captain uses no tools. They know the carrier report above and, of your ships, how many there are and each one’s name and hull. Asked about fuel, they give the carrier’s tritium; anything else they leave to the core. Every comms question reaches them while they stay selected:

if (selected is not { Channel: CommsChannel.Carrier, SubChannel.Key: CommsChannels.CaptainKey }

“Tower” on the same channel reaches tower control the same way. Push-to-talk always goes to the core. The core is told each exchange as one it overheard, so it can refer to it, but the captain’s answers are not added to the core’s own conversation.

With galaxy search on, a carrier more than 500 light years from you is out of range: the core says so and gives the distance, and no model is asked. With galaxy search off, or when the distance cannot be found, the captain answers. The captain cannot be reached until a carrier you own and its system have been seen in the journal.

Between 250 and 500 light years the line gets weaker the further away the carrier is. The static under the captain’s voice rises, the voice sounds narrower, short stretches of it drop out, and words are lost, each run of them shown as “…” in the panel and the caption:

public static double Strength(double? lightYears) => lightYears switch

The core overhears only the words that came through. The captain’s own conversation keeps the full answer.

What Directive 47 actually knows about your carrier

Only what CarrierStats reports, and only from the last time you opened the carrier management screen:

Known From
Fuel CarrierStats.FuelLevel
Cargo against capacity CarrierStats.SpaceUsage
Balance CarrierStats.Finance.CarrierBalance
Jump range CarrierStats.JumpRangeCurr
Docking access CarrierStats.DockingAccess
Pending decommission CarrierStats.PendingDecommission
Services and who staffs each CarrierStats.Crew 
/// <summary>Tritium in the carrier's own tank, from CarrierStats.</summary>
public int? FuelLevel { get; init; }

Every figure carries the date it was read, because a carrier keeps jumping, trading and burning fuel while you are away from the screen that reports it. A booked jump — destination, body and departure time — comes from CarrierJumpRequest instead, and is cleared the moment the jump fires or is cancelled.

If no CarrierStats has ever been seen, the report says so rather than saying you have no carrier — those are different answers, and only one of them is true.

The page shows the carrier’s hull beside its tiles, from the same fetch and the same Hull pictures setting as a ship’s picture; see the pictures. The mini panel and the squadron’s carrier show none.

The tool surface, for contributors

describe_carrier

Reports the system it is in, a booked jump, fuel, cargo against capacity, balance, jump range, docking access, the decommission flag and every service with its state and crew. Takes no arguments.

{"type":"object","properties":{},"required":[],"additionalProperties":false}