The CONTOUR Spacecraft Performance Tests were series of tests performed with the spacecraft after integration of the instruments onto the spacecraft was complete. The objectives were to verify spacecraft-level requirements by test and demonstration; confirm that subsytem, component and software requirements verified in standalone testing are likewise verified when the CONTOUR spacecraft is in a near-flight configuration and exposed to environmental stresses; and make engineering measurements characterizing spacecraft performance. The full test required 6 days for completion. Science Operations and the instrument engineering teams supported these tests by providing real-time STOL scripts for individual instrument testing. We also provided a sequenced SSR record stress test (normally on Day 2), and a sequenced Encounter test (normally performed on Day 3) that involved all instruments. The Encounter SPT ran about 3 hours and included G&C (pointing) and a full CRISP tracking simulation through closest approach. The complete set of tests was originally intended to execute 5 times in all, but due to various problems along the way, there were more executions than 5. Dates of the SPT Encounter Tests are given below: I don't have a complete coherent log of all of the various tests and portions of the test that were executed over those months. But we do know from the individual test lists located in the directory harch/test_data_summaries/ when the encounter tests were performed, some of the SSR Stress Tests, and when all of the individual instrument functionals were performed as a part of the test series. I can say that Encounter Tests were performed on 1/9/02, 3/11/02, 3/20/02, 3/23/02, 4/9/02, 4/17, and 5/3 of 2002. There was also a very preliminary dry run during the week of December 17, 2001. The test sequences provided in this directory are for the Encounter sequence. The Encounter SPT sequence involved all instruments with the exception that the dry run in December 2001 and the January 9, 2002 executions did not include CRISP. In general these tests were very successful. They helped to identify some problems that were fixed. I have included a comparison spreadsheet, where I compared the results of 3 of the executions of the Encounter SPT test. Except for known data outages and known glitches, the comparison confirmed that the sequences were executing and instruments performing as expected.