The Phoenix Mars Scout Lander, the first robotic explorer in NASA's “Scout Program,” launched on 4 August 2007, will land on the northern plains of Mars in late May 2008, prior to the northern Martian summer. The Phoenix mission “follows the water” by landing in a region where NASA's Mars Odyssey orbiter has discovered evidence of ice‐rich soil very near the Martian surface. For 3 months after arrival, the fixed Lander will perform in situ investigations that will characterize the chemistry of the materials at the local surface, subsurface, and atmosphere, and will identify potential evidence of key elements significant to the biological potential of Mars. The Lander will employ a robotic arm to dig to the ice layer, and will analyze the acquired samples using a suite of deck‐mounted science instruments. The development of the baseline strategy to achieve the objectives of this mission involves the integration of a variety of elements into a coherent mission plan. These elements are involved in defining plans for the launch phase, interplanetary cruise, atmospheric entry, descent and landing, landing site selection, and the surface operations. An overview of the integrated mission plan, from launch through surface operations, is described.

This paper addresses NASA's requirement on the 2007 Phoenix Mars Lander to provide spacecraft communications during entry, descent, and landing on Mars to allow the identification of probable root cause should any mission failure occur. The Phoenix mission launched on 4 August 2007 and will land on 25 May 2008 on the northern plains of Mars to conduct a three-month study of the Martian environment. The paper discusses the architectural trades in designing a communications link and surveys the entry, descent, and landing communications approaches taken by previous missions. It then discusses the Phoenix-specific constraints and degrees of freedoms and presents a novel and robust implementation approach to entry, descent, and landing communications. The overall methodology and conclusions described herein can serve as a pathfinder for the entry, descent, and landing communications architecture and implementation of future Mars landed missions.

No abstract

No abstract

No abstract