https://www.nasa.gov/missions/artemis-ii/arow/
From 3/8/1988 ( as me, Kerry Burgess, while enlisted paygrade E-5, designated Fire Controlman Petty Officer Second Class (FC2), my official enlisted US Navy documents includes: Terrier MK 152 guided-missiles Fire Control Computers Complex Operator (operator and advanced technician, UNIVAC digital-computers Mk152 Terrier System for, primarily, SM2-ER {Extended Range} Standard Missiles ordnance) - CF-division, Missile Plot, USS Wainwright CG-28, US Navy, following my graduation Naval Missiles School, Dam Neck, Virginia ) To 4/6/2026 ( next Monday ) is 13908 days
13908 = 6954 + 6954
From 11/2/1965 ( my known birth date in Antlers, Oklahoma, USA, as Kerry Wayne Burgess ) To 11/16/1984 ( premiere USA film "Night of the Comet" ) is 6954 days
https://www.nasa.gov/blogs/missions/2026/04/03/artemis-ii-flight-day-3-crew-prepares-for-first-correction-burn-readies-to-receive-lunar-observation-assignment/
The lunar science team in mission control is selecting geologic features on the Moon’s surface that will be visible to the crew as Orion loops around it on Monday, April 6. During the six-hour lunar science observation period, the Sun, Moon, and the Orion spacecraft will be aligned such that the crew will see about 20% of the Moon’s far side, the hemisphere not visible from Earth, lit by the Sun.
https://www.nasa.gov/blogs/missions/2026/04/02/artemis-ii-flight-day-2-orion-completes-tli-burn-crew-begins-journey-to-the-moon/
excerpt - from internet
https://www.cockatoo.com/content/artemis-ii-views-countdown-launch
Artemis II views, countdown & launch
CNN
Apr 2, 2026
30:45
Copy. NTD COSE hold requested. Copy that. I have an LCC violation of O-CT-004 S-band transponder anomaly. This was a transient LCC violation, so transponder one had a demodulated SNR estimate that went down to 2 dBm. When it should have been between 10 and 13, it is now back up to 12, but we did lose that for just a moment. It does not appear that we lost our bit sync or carrier lock, which would be indicative that we lost our lock with the vehicle. So, at this point, recommendation would still be go.
31:27
However, we do have a pre-planned contingency procedure if we want to look at that. But again, this is transient, so we're back in a nominal range.
31:34
All right.
31:34
Let's see. LP, NTD?
31:37
Yeah, we're not seeing that hit. So I guess the question for COSC, was that less than three samples?
31:41
Was that below our persistence? Stand by, let me look. It did look like it did persist for several seconds on mine, but let me take a look at the number of samples. Could I get a repeat on the affected LCC, please?
31:56
Yes, ma'am, that's going to be O-CT-004.
32:03
Thank you. Yeah, I was taking a look at the data right here.
32:35
Looks like that was a single sample.
32:37
Yeah, copy that. RFDS does report that they also lost lock for about five seconds. So I would love to ask KUS and see if they also lost lock for about five seconds, so I would love to ask KUS and see if they also lost lock with the vehicle for any extended amount of period.
32:55
And COSC, while we're doing that, these are 110th hertz measurements, correct? So we would have had to lose it for over 10 seconds to get a second sample? Yes, sir. That's correct. It is 1 tenth Hertz. Yes, so from our perspective, the allowance is effectively up to 30 seconds, up to 3 samples based on the 1 tenth Hertz. This is not an LCC violation, I believe.
33:24
Yes, sir. I would agree with that at this point. Copy that. on the 1 tenths hertz. This is not an LCC violation, I believe. Yes, sir. I would agree with that at this point. Copy that. For check, can KUS and 232, I don't think they have 212 access. We're trying to verify, but...
33:46
But it sounds like they have a loss of lock as well. About two seconds. Okay. And I guess for both KUS and COSE, do we have lock now?
33:51
That's affirmed.
33:52
We do have lock for COSE.
34:00
Yeah, so from the integration console perspective, we did have a temporary loss there within the allowable and per the requirement.
34:07
Let's go.
34:08
And this is Houston Flight.
34:09
We have lock and we have good telemetry here in GSE.
34:14
And KUS is reported to have good lock now. So with all of that, OSC, then are we in a go configuration per your LCC? Yes, sir. Recommendation would be go. Okay. LPE, you concur with that? Yes, sir. LPE concurs go. And Launch Director?
34:33
Yes, sir. Launch Director concurs go. All right. And I'm going to go ahead and just verify everybody has everything else complete, Launch Director? And if we do, we'll be ready to pick up the poll at that time, unless there's something else that you're aware of.
- by me, Kerry Wayne Burgess, posted by me: 5:15 PM Pacific-timezone USA Friday 04/03/2026
