NASA’s Artemis II Lunar Science Operations Report documents how scientists supported the April 2026 lunar flyby and recommends changes for later crewed missions. Released with the mission’s science materials on October 7, the report examines staffing, training, communications, cameras, and data handling. Its central operational finding is specific: continuous coverage at the science console did not always coincide with support from the rooms responsible for planning and analysis.
The Artemis II science operations team worked within a crewed spacecraft test mission. Science requests had to fit vehicle constraints, astronaut workload, communications, and the flight director’s authority. The recommendations concern how later missions could organize that support more consistently. They are lessons and proposals from the lunar science team, rather than evidence that NASA has approved new staffing levels, purchased equipment, or adopted every suggested procedure.
The operations report describes a Science Officer working at the SCIENCE console in the flight control room. That position connected lunar specialists with the mission’s other controllers and, when authorized, the astronauts. Two supporting facilities handled related work: the Science Evaluation Room and the Science Mission Operations Room. Their responsibilities included activity preparation, interpretation of incoming observations, and support for science deliverables.
This arrangement placed scientific advice within Artemis mission control, where decisions also depended on crew and spacecraft safety. The team recommends keeping the Science Officer in the front flight control room and preserving direct crew communication during science activities. The report explicitly retains deference to the flight director and primary capsule communicator. Direct access is a proposed operational method for focused scientific follow-up, not an independent science command channel.
Science Officers worked continuously from flight day two through flight day nine using three shifts. Most personnel in the supporting science rooms followed activity-based schedules, generally around eight hours per shift. Those schedules concentrated staff around known events and deliverables, but their changeovers did not match the SCIENCE console’s. Some important tasks arose when the console lacked supporting-room coverage.
The report recommends that future science teams accommodate three-shift coverage for those facilities. It also proposes flexible scheduling or on-call arrangements when event timing is uncertain. If staffing permits, longer-term analysis should have dedicated roles rather than being added to immediate operational support. These recommendations address availability and workload. The document does not quantify the additional personnel cost or present an approved staffing plan.
Training presents a related issue. Science Officers followed flight controller certification standards, but some supporting-room roles used informal feedback processes modeled on certification. The team also conducted integrated simulations, face-to-face meetings, and slower walkthroughs of activities in sequence. The report recommends clearer, more standardized training and feedback expectations for future missions whose science support could be more complex.
The practical purpose of standardization is to clarify what each person must be able to do before taking an operational role. Simulations can expose unclear handovers, competing responsibilities, or procedures that fail under realistic timing. Cross-training can provide coverage when assignments change. The report supports those uses of training without suggesting that a single certification model will suit every future mission or science activity.
Communication methods also required deliberate coordination. Team members worked across several NASA centers, using shared files, a wiki, text conversations, and operational voice loops. Templates supported shift preparation, handovers, console logs, and documentation. The report found no significant documentation gaps or lost information attributable to rapid voice communication, but it identifies discoverability as a continuing concern as files and procedures accumulate.
The team recommends retaining voice as the principal means of coordination between the supporting science room and flight control. Written messages remain appropriate for longer explanations and information requiring a permanent record. This division connects communication format with the task: a time-sensitive exchange differs from a procedure or analysis that others must retrieve later. More software alone would not resolve uncertainty about which record is authoritative.
Data handling provides a concrete example of operational prioritization. After the lunar flyby, the team gave recorded crew descriptions the highest downlink priority because they were needed for the flight day seven science conference. Audio preserved what astronauts had perceived during the observations. Selected photographs were intended to supply context. Actual communications capacity allowed more material to arrive before that conference than the minimum plan required.
The recommendation is to set downlink priorities according to the next science activity and prepare processes for both limited and unexpectedly large data deliveries. A useful file must arrive in time for the decision or discussion it supports. Early postflight interviews are another proposed improvement, allowing scientists to obtain crew perspectives sooner rather than relying mainly on later debriefs.
Camera recommendations distinguish recording from direct viewing. The team found that a Nikon D5 camera’s optical viewfinder also served as a monocular for comparing unaided-eye observations with magnified views. The Nikon Z9’s electronic viewfinder did not provide the same direct optical function. The report recommends considering at least one optical-viewfinder camera for relevant tasks, rather than treating its recommendation as a general ranking of camera brands.
Other equipment and training proposals concern annotations and external cameras. The team recommends more preparation for digital observational sketching, acknowledging that limited time and current tools can restrict detail. It also proposes linking spacecraft-camera capabilities to defined science objectives. Impact-flash monitoring, for example, requires sufficient spatial resolution and frame rate to record brief events. A camera useful for broad context may not satisfy that purpose.
The report further recommends allowing crew members to work in pairs during scientific exploration when possible. Discussion during an observation can help distinguish features and develop competing interpretations that ground scientists can examine. For future planning, the document provides a record of where the existing arrangement worked and where support was incomplete. Its recommendations become operational changes only through subsequent decisions about staffing, training, procedures, and hardware suited to the next mission’s actual requirements.
