Days to Seconds

The Clock That Never Resets After Liftoff

A flight plan is written the way people talk: a three-day transit, an eight-day lunar profile, a six-month crew increment. The vehicle does not think in any of those. From the moment the hold-downs release, the onboard counter starts adding one, and every telemetry frame, every burn command and every fault timestamp is pinned to that single growing number of seconds. Mission elapsed time is shown as days, hours, minutes and seconds for the people watching, but underneath it is one integer.

So the same schedule exists in two forms at once, and moving between them is constant work: the press kit says 84 days, the sequence file wants 7 257 600.

Conversion factor: 1 d = 86 400 s, so multiply days by 86 400. A two-week free-flight profile of 14 d is 1 209 600 s on the counter, and one elapsed day is 86 400 — the point where the day field increments and the seconds field wraps back to zero.

Why Flight Controllers Live in Seconds

Liftoff is the only zero that matters

A launch can slip by a day or a season without changing a line of the timeline, because everything downstream is written relative to T-0 rather than to a date. Slip the launch and the whole plan slides with it, untouched.

Telemetry is stamped, not narrated

Downlinked frames carry a counter value, not a sentence. Two ground stations in different time zones can order the same packets without agreeing on anything except how many seconds have passed since the vehicle left the pad.

Plans are written in days, logs in seconds

Crew rotations, consumable margins and public schedules all arrive in whole days. The reconstruction after the flight comes back in raw counter values, and somebody has to reconcile the two documents.

Burns are commanded in seconds

An engine firing lasts tens or hundreds of seconds and is scheduled at a counter value. A manoeuvre pencilled in for day 3 of the flight only becomes executable once that day has a number attached to it.

Reading a Mission Plan in Counter Ticks

Most of the work is turning one written duration into the value a sequence file or a plotting window expects, then checking that answer against a log that came back the other way round.

Put the planned length in the left box

Type 3, 8 or 182 and the second count appears while you are still typing. Fractional days are accepted, so 1.02749 for a sol needs no reformatting, and a comma decimal mark behaves exactly like a full stop.

Split the flight into named phases

Ascent, phasing, docked operations, undock and entry each get their own figure. Converting them one at a time and adding the second counts keeps the arithmetic auditable, which a single lump total never is.

Turn a downlinked counter back into days

Press swap (↔) and the pair runs s → d, so a fault logged at 703 115 resolves to 8.13790509 d and lands in the right slot of a written timeline. Typing into the right field back-solves the left one just as well.

Hand the bare counter to your tooling

The copy control gives digits with nothing attached — no unit, no separators — which is what a sequence table or a plotting axis will take. Selecting inside a field and pressing Ctrl + C also drops the spacing.

The day here is exactly 86 400 s: it carries no leap second and it is not a Martian sol. If your schedule is counted in sols, work from 88 775 s and keep the two clocks in separate columns rather than hoping one covers both.

Mission Phases and the Second Counts Behind Them

Durations that get quoted in days, alongside the counter value each one represents. The short entries are single events inside a flight; the long ones are whole missions, and the spread between them is why one document can never sit comfortably on a single unit.

Mission or phase	Quoted duration (days)	Counter value (seconds)	Why it is counted that way
One low-Earth orbit	0.0645 d	about 5 574 s	Period near 93 min, so roughly 15.5 laps a day
Fast rendezvous to a station	0.125 d	about 10 800 s	A couple of orbits, planned to the second
One Martian sol	1.02749 d	88 775 s	Surface teams work the sol, not the terrestrial day
Countdown from call to stations	1.79166667 d	154 800 s	43 h of clock time, interrupted by built-in holds
Apollo 11, liftoff to splashdown	8.13790509 d	703 115 s	Logged as 8 d 3 h 18 min 35 s of elapsed time
Skylab 4 crew stay	84 d	7 257 600 s	A whole-day figure by design, for crew scheduling
Standard station increment	182 d	15 724 800 s	Half a year of rotation, laid out in days from the start
Longest single spaceflight	437.75 d	37 821 600 s	437 d 18 h, a record still quoted in both units

Read down the counter column and the two-unit habit explains itself: a rendezvous and a record-length stay differ by a factor of roughly 3 500, and no display shows both usefully. Days keep a schedule readable at a glance; seconds keep it precise enough to command an engine with. The dangerous entry is the sol at 1.02749 d, close enough to one day that somebody rounds it and quietly throws away forty minutes.

What the Converter Adds to a Flight-Plan Review

A day-count plan becomes a counter value

Both boxes update on every keystroke, so a phase list can be walked through without pausing, and a revised duration shows its new counter value before the pen leaves the page.

Back-solve a logged counter into days

Reverse the pair with the swap control and raw values pulled out of a downlink resolve to the day figure a written reconstruction is organised around.

Sol-length figures keep their fractions

Eight decimals survive, so 1.02749 d stays visibly distinct from a round day instead of collapsing into it the way a two-decimal field would force it to.

Counter values leave without separators

Copying yields unpunctuated digits, ready for a field that rejects a grouped number and would otherwise truncate whatever it failed to parse.

Questions From the Flight Operations Room

What is mission elapsed time and where does it start?

It is the time since the vehicle left the pad, counted forward with no reference to any calendar. Zero is the liftoff instant, and displays usually group the value as days, hours, minutes and seconds. Because it is anchored to an event rather than a date, a schedule built on it survives a launch slip without a single edit: everything still happens at the same elapsed value, whatever day the flight actually begins. That is also why the underlying quantity is a plain second count, with the grouping into days a courtesy for whoever is reading the screen.

Why does telemetry count seconds instead of stamping a date?

A single monotonically increasing counter leaves nothing to argue about. There is no time zone, no daylight-saving jump, no disagreement between two teams over a date format, and no way for two frames to claim the same instant. Ordering packets becomes a comparison of integers, which every receiver does identically. It is also cheap on a link where each bit is budgeted: one field rather than six. Human-readable dates get attached later, on the ground, by whoever writes the report rather than by the vehicle itself.

How many seconds long is a Martian sol, and why does the offset matter?

A sol runs about 88 775 s against the 86 400 s of the day used here, a gap of roughly 2 375 s or a little under forty minutes. Across a surface campaign that offset piles up relentlessly: a team living on sols drifts a full terrestrial day out of step about every five weeks, which is why sol-based shift patterns are so hard on the people keeping them. For arithmetic, treat a sol as 1.02749 d or convert straight from seconds, and never let a sol figure sit unlabelled in a column of days.

How do I get an orbit count for a day from a period in minutes?

Convert the day to seconds and divide by the period in seconds. A period near 93 min is 5 580 s, and 86 400 divided by 5 580 gives about 15.5 circuits a day. The half is what makes ground tracks interesting: a spacecraft does not cross the same longitude at the same clock time on consecutive days, so contact windows shift. Period depends on altitude, so use the value for the orbit you are working with rather than a remembered one, and recompute after every reboost.

Do built-in holds mean the countdown clock disagrees with the wall clock?

Yes, deliberately. A countdown is a sequence of tasks with planned pauses written into it, so the T-minus display stops while the wall clock keeps running. Announce a start at T-43 h and liftoff is not 154 800 s away in real time; it is 154 800 s of clock plus however long the holds absorb, and an unplanned hold stretches it further again. Convert the T-minus figure if you want the counter value, but never publish it as a time remaining without the hold budget added on top.