[tz] Timekeeping in the news

[Marshall Eubanks]

On Tue, Dec 24, 2019 at 10:03 PM Howard Hinnant
<howard.hinnant at gmail.com> wrote:
>
> 11h...  Sure smells like a time zone issue.  Such as not taking time zones into account, or taking them into account incorrectly.  Fwiw, there’s an 11h difference between Cape Canaveral (launch site) and India (popular location for outsourced programming).

No, India is 5 hours and 30 minutes ahead of UTC and 10 hr 30 min
ahead of EST, and that half an hour does indeed matter.

Regards
Marshall

> It would be great to know the facts...
>
> Howard
>
> On Dec 24, 2019, at 8:48 PM, Alan Mintz <alan.mintz at gmail.com> wrote:
> >
> > Oops. The correct NYT link for the 11 hours: https://www.nytimes.com/2019/12/22/science/boeing-starliner-landing.html .
> >
> > On Tue, Dec 24, 2019 at 5:46 PM Alan Mintz <alan.mintz at gmail.com> wrote:
> > Here's the NYT article that mentions the 11 hours: https://forum.nasaspaceflight.com/index.php?topic=43958.860 and an interesting (though "armchair") analysis, noting that the mission countdown started at T-11 hours: https://forum.nasaspaceflight.com/index.php?topic=43958.860 .
> >
> >
> > On Tue, Dec 24, 2019 at 4:42 PM Marshall Eubanks <marshall.eubanks at gmail.com> wrote:
> > It was a time transfer error - the mission elapsed time clock was off
> > by 11 hours because it took the wrong time from the Atlas at
> > separation. They were very lucky not to lose the spacecraft.
> >
> > https://arstechnica.com/science/2019/12/something-went-wrong-with-the-starliner-spacecrafts-first-flight/
> >
> > Regards
> > Marshall Eubanks
> >
> > On Tue, Dec 24, 2019 at 4:15 PM Arthur David Olson
> > <arthurdavidolson at gmail.com> wrote:
> > >
> > > "Boeing Starliner Ends Up In Wrong Orbit After Clock Problem."
> > >
> > > https://www.nytimes.com/2019/12/20/science/boeing-starliner-launch.html
> > >
> > >     @dashdashado
> >
> >
> > --
> > Alan Mintz <Alan.Mintz at gMail.com>
> >
> >
> > --
> > Alan Mintz <Alan.Mintz at gMail.com>
>