Our team's discovery last summer of a faint (V~26.1) new satellite (provisionally called "P4") around Pluto demonstrated that the Pluto system is even richer with orbiting material than previously suspected. Moreover, P4's location near yet another Charon mean motion resonance (MMR), as Nix and Hydra also are, suggests that still more Charon MMRs could be populated with small, as yet undetected, satellites. Further still, there is now some evidence from HST for a debris ring inside Charon's orbit. While these are exciting developments scientifically, they have, more importantly, exposed a potentially catastrophic threat to NASA's New Horizons (NH) spacecraft as it passes through the Pluto system in July 2015 - i.e., debris ejected from Pluto's small satellites may be creating hazards to flight. We propose a Director's Discretionary Time (DDT) program comprised of 34 orbits of Hubble observations for our time-critical need in 2012 to investigate potential hazards to NASA's New Horizons spacecraft as it flies through the Pluto system in July 2015, and to certify potential new trajectory options for the NH mission if it must "bail out" to a safe haven. The results from this Hubble DDT program will be unique and will have profound implications for the New Horizons mission, a top scientific priority of the last NASA Planetary Decadal Survey. All images will be taken with the WFC3 camera using the F350LP filter for maximum sensitivity. For solar-type objects, the throughput of the F350LP filter is ~1.6x larger than for the F606W filter, which was used during the Jun-Jul 2011 observations. All images are taken with the UVIS2-C512-SUB aperture (512 x 512 array) to minimize overhead. Our program has two principal measurement objectives: (1) search for faint satellites (V <= 24.5) and debris (I/F <= 3x10-7) within Charon's orbit (i.e., within ~0.9" of Pluto), and (2) search for even fainter satellites (V <= 28) and debris (I/F <= 1x10-7) in Charon's instability strip (where we hope the SHBOT aim point will be) and between Hydra's orbit and the edge of the CCD sub-array (which extends to ~3x Hydra's orbit; the SHBOT aim point would have to be in this region if the Charon instability strip is deemed to be unsafe). These two different objectives require two different observing strategies. We must take many (32 total per orbit, 16 at each of two dither locations) relatively short exposures (30s) to search for satellites within Charon's orbit, going deep but preventing saturation in the region of interest. To achieve maximum sensitivity for the deep search outside Charon's orbit, we use individual exposure times of 175s with enough different images (12 total per orbit, 6 at each of two dither locations) to provide excellent rejection of cosmic rays and star trails, while still yielding long total exposure times (the total exposure time per orbit is 2.2x the value achieved for the orbits using 30s exposures). Objective #1 (search for satellites and debris within Charon's orbit): 4 pairs of visits with 2 orbits per visit = 4 x 2 x 2 = 16 orbits Each orbit consists of the following exposures: 1 x 3s exposure to get an unsaturated image of Pluto 16 x 30s exposures at one location on the CCD 16 x 30s exposures at a dithered location on the CCD We request two orbits per visit because comparing the positions of objects in two consecutive orbits is a powerful technique for determining that the object is in orbit around Pluto. The number of visits is dictated by the requirement to detect any satellite that could be on a stable orbit inside Charon's orbit. Among the latter, objects in the 1:2 MMR with Charon appear to be the most promising candidates (representative orbits are shown by the blue dotted curves in figure 3), and we have designed an observing strategy to detect those, if they exist. For the first three pairs of visits (i.e., for the first six visits), each visit should be separated from the preceding visit by ~1.6 days, which is half the orbital period of the 1:2 MMR satellites. If an object in the 1:2 MMR is detected during the first visit, it will probably be too close to Pluto to be seen 1.6 days later (i.e., in the second visit of the first pair), but should be observable 3.2 days later (i.e., in the first visit of the second pair). Similarly, an object in the 1:2 MMR that is not seen in the first visit, should be observable 1.6 days later, and then again 3.2 days after that first detection (i.e., 4.8 days after the first visit). By adding a third pair of visits, we expect to cover virtually the entire orbital phase space for the 1:2 MMR satellites. However, we also want to cover potential satellites in stable, non-resonant orbits, and which might be missed if we only use a regular observing cadence synchronized to the 1:2 MMR objects. Our simulations suggest we need two additional visits (i.e., bringing the grand total to eight visits), with a different time separation than the others, to provide ~90% phase space coverage of potential satellites orbiting between Pluto and Charon. In addition to the cadence, other parameters we will want to optimize in phase2 (when possible) include the Pluto-Charon separation (minimized to reduce the number of unusable pixels in the area of interest) and Hubble's roll angle (to keep Charon at a fixed CCD location for two consecutive orbits and perhaps to put Pluto and Charon in the same CCD column). Note that these observations will also provide a deep search for debris within Charon's orbit, although the sensitivity will not be as high as for the observations described below. Objective #2 (search for satellites and debris from Charon's orbit out to ~10" from Pluto): 3 pairs of visits with 3 orbits per visit = 3 x 2 x 3 = 18 orbits Each orbit consists of the following exposures: 1 x 3s exposure to get an unsaturated image of Pluto 6 x 175s exposures at one location on the CCD 6 x 175s exposures at a dithered location on the CCD We will follow the same technique employed during the June-July 2011 observations to optimize the search for rings. That is, Hubble's roll angle and the time between the visits in each pair will be adjusted so that Pluto and Charon have the same relative locations on the CCD for each visit, while the ring orientation on the CCD changes by 90 degrees between the two visits. Thus, subtracting the combined image (i.e., the combination of all images in three consecutive orbits) from one visit from the combined image from its paired visit will yield a unique "crossed ellipses" signature (one positive and one negative), if a ring is present. Repeating this process for a total of three different times (i.e., taking three pairs of visits) will allow us to observe at three different orientations of the Pluto system, thus convincingly confirming or refuting the tentative detection of a ring inside Charon's orbit (Fig. 2). Comparing the images from three consecutive orbits provides a powerful tool for detecting real objects in orbit around Pluto. (For satellites outside Hydra's distance, blinking the images between the first and third orbits is necessary to detect plutocentric motion.) By combining the images from all three orbits within a visit, by using a wider filter, and by obtaining three pairs of visits, we estimate that the I/F limit reached by our proposed program will be ~3x lower than achieved during our June 2011 observations. Our Total Request is, therefore, 34 orbits. Most of the data collected by our program will be in the background noise limited regime. Scattered and diffracted light from Pluto and Charon dwarf all other background sources. P4 (V~26) should be detectable in most, if not all, of the individual 175s images (it was detected in 37 of the 48 images taken during cycle 17 [GO-11556] using F350LP with 180s exposure times), which is a nice feature to have. Using 30s exposures allows us to probe the dynamically stable region inside Charon's orbit, to within ~0.4" of the center of Pluto. The intensity of the scattered light level is well determined from our previous Hubble observations, and we have used these numbers in the WFC3 ETC to calculate the sensitivity of our planned observations. The zodiacal light in the ETC is scaled by a factor of 11 to simulate the scattered light level at Nix's distance from Pluto. A scaling factor of 170 is used to simulate the scattered light level at ~0.4" from Pluto, which defines the inner edge of the orbital stability zone within Charon's orbit. Despite these high background light levels, the ETC shows SNR=9.2 for V=26.7 for a single orbit of observations at Nix's distance from Pluto (using a 3 pixel radius aperture; WFC3 ETC ID 231401) when using the 175s exposures. We find SNR=3.2 is achieved for V=26.0 in a single orbit of observations at ~0.4" from Pluto (WFC3 ETC ID 233059) when using the 30s exposures. These ETC results are generally consistent with our image-based simulations, in which we injected synthetic objects in the Hubble data obtained in September 2011 (Figs. 7-8). For regions outside of Charon's orbit that are clear of image artifacts and star trail residuals, we can detect down to V~27.5 in a single orbit of observations using 12 x 175s exposures. By co-adding data from two orbits, the sensitivity limit can be pushed down to V~28.1. For satellites outside of Hydra's orbit, we can reach V~28.3 by co-adding data from three consecutive orbits. In the region inside Charon's orbit, systematic effects associated with the telescope's "focus breathing" and optical imperfections limit our sensitivity compared to the ETC predictions, which are based on counting statistics. We find that satellites having V~24.5, perhaps even as low as V~25, should be detectable inside Charon's orbit. We request a total of 34 orbits near the time of the next Pluto opposition period in late-June 2012. We have identified a 2-week window that is optimal for our program (2012 Jun 18 through Jul 01, inclusive; indicated by the green curve in Fig. 9), but some of our observations can be scheduled outside this window, if necessary. Our program requires specific roll angles and observing cadences to optimize the search for satellites and debris, and we are already working with STScI's premier moving target Program Coordinator (Tony Roman) on the scheduling of these observations. Tony expertly handled the scheduling of Showalter's observing program last summer (GO-12436), which required roll angle and timing constraints. The types of observations we're requesting during the 2012 Pluto opposition are similar to those successfully performed in June 2011. Our initial analysis (including in consultation with Tony) indicates that our program can be scheduled in a way that meets the objectives of our DD program. SOLAR SYSTEM 0 false 0.0 0.0 false false false false SUPPORTED SOLAR SYSTEM PLANET Pluto system STD=PLUTO EARTH SOLAR SYSTEM Copy of target 1. Used in visits 82 - 85 which needed to be reprocessed due to leap second. PLANET Pluto system STD=PLUTO EARTH SOLAR SYSTEM Because the sub-Earth latitude of Pluto is ~ 44 degrees, the OLG of Charon needs to be 35, 145, 215 or 325 to place it along a diagonal from Pluto, assuming Pluto is oriented with its pole parallel or perpendicular to the UVIS Y-axis. PLANET Pluto with Charon along a 45 degree diagonal in the first orbital quadrant. STD=PLUTO OLG OF CHARON BETWEEN 20 50 EARTH SOLAR SYSTEM Because the sub-Earth latitude of Pluto is ~ 44 degrees, the OLG of Charon needs to be 35, 145, 215 or 325 to place it along a diagonal from Pluto, assuming Pluto is oriented with its pole parallel or perpendicular to the UVIS Y-axis. PLANET Pluto with Charon along a 45 degree diagonal in its second orbital quadrant. STD=PLUTO OLG OF CHARON BETWEEN 130 160 EARTH SOLAR SYSTEM Because the sub-Earth latitude of Pluto is ~ 44 degrees, the OLG of Charon needs to be 35, 145, 215 or 325 to place it along a diagonal from Pluto, assuming Pluto is oriented with its pole parallel or perpendicular to the UVIS Y-axis. PLANET Pluto with Charon along a 45 degree diagonal in the third orbital quadrant. STD=PLUTO OLG OF CHARON BETWEEN 199 230 EARTH SOLAR SYSTEM Because the sub-Earth latitude of Pluto is ~ 44 degrees, the OLG of Charon needs to be 35, 145, 215 or 325 to place it along a diagonal from Pluto, assuming Pluto is oriented with its pole parallel or perpendicular to the UVIS Y-axis. PLANET Pluto with Charon along a 45 degree diagonal in the fourth orbital quadrant. STD=PLUTO OLG OF CHARON BETWEEN 305 340 EARTH SOLAR SYSTEM Because the sub-Earth latitude of Pluto is ~ 44 degrees, the OLG of Charon needs to be 35, 145, 215 or 325 to place it along a diagonal from Pluto, assuming Pluto is oriented with its pole parallel or perpendicular to the UVIS Y-axis. PLANET Pluto with Charon along a 45 degree diagonal in the first orbital quadrant. STD=PLUTO OLG OF CHARON BETWEEN 15 50 EARTH SOLAR SYSTEM Because the sub-Earth latitude of Pluto is ~ 44 degrees, the OLG of Charon needs to be 35, 145, 215 or 325 to place it along a diagonal from Pluto, assuming Pluto is oriented with its pole parallel or perpendicular to the UVIS Y-axis. PLANET Pluto with Charon along a 45 degree diagonal in its second orbital quadrant. STD=PLUTO OLG OF CHARON BETWEEN 120 160 EARTH SOLAR SYSTEM Because the sub-Earth latitude of Pluto is ~ 44 degrees, the OLG of Charon needs to be 35, 145, 215 or 325 to place it along a diagonal from Pluto, assuming Pluto is oriented with its pole parallel or perpendicular to the UVIS Y-axis. PLANET Pluto with Charon along a 45 degree diagonal in the third orbital quadrant. STD=PLUTO OLG OF CHARON BETWEEN 196 230 EARTH SOLAR SYSTEM Because the sub-Earth latitude of Pluto is ~ 44 degrees, the OLG of Charon needs to be 35, 145, 215 or 325 to place it along a diagonal from Pluto, assuming Pluto is oriented with its pole parallel or perpendicular to the UVIS Y-axis. PLANET Pluto with Charon along a 45 degree diagonal in the fourth orbital quadrant. STD=PLUTO OLG OF CHARON BETWEEN 308 340 EARTH WFC3/UVIS Imaging No No F350LP WFC3/UVIS Imaging No No F350LP Using ephemeris for target 12801-31-PLUTO-CHARON-1ST-QUADRANT ephemeris data for target 12801-31-PLUTO-CHARON-1ST-QUADRANT does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Pluto with its prograde rotation pole oriented downward, parallel to the UVIS Y-axis; Charon on the diagonal at lower right (1st orbital quadrant). To be scheduled along with Visit 32 or 33. 1340821807000 196.0 (Tic-Visit :proposal-id 12801 :visit-id "31" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:23:32.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 178480 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "31" :obset-id "31" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "31" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2698 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "31" :orbit-number 2 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "31" :orbit-number 3 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 232 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) false 3 0 Using ephemeris for target 12801-32-PLUTO-CHARON-4TH-QUADRANT ephemeris data for target 12801-32-PLUTO-CHARON-4TH-QUADRANT does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Pluto with its prograde rotation pole pointed rightward, perpendicular to the UVIS Y-axis; Charon on the diagonal at lower right (4th orbital quadrant). To be scheduled along with Visit 31. Either Visit 32 or 33 must be scheduled, but not both. To match the position of Charon most accurately, the optimal timing of Visit 32 would be either 0.8 or 1.8 Charon orbits (5.15 days or 11.53 days) later than Visit 31. (Tic-Visit :proposal-id 12801 :visit-id "32" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:23:36.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 178480 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "32" :obset-id "32" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "32" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2698 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "32" :orbit-number 2 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "32" :orbit-number 3 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 232 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) false 3 0 Execute either Visit 32 or Visit 33, but not both. Using ephemeris for target 12801-33-PLUTO-CHARON-2ND-QUADRANT ephemeris data for target 12801-33-PLUTO-CHARON-2ND-QUADRANT does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Pluto with its prograde rotation pole oriented leftward, perpendicular to the UVIS Y-axis; Charon on the diagonal at lower right (2nd orbital quadrant). To be scheduled along with Visit 31. Either Visit 32 or 33 must be scheduled, but not both. To match the position of Charon most accurately, the optimal timing of Visit 33 would be either 0.7 or 1.7 Charon orbits (4.43 or 10.82 days) earlier than Visit 31. (Tic-Visit :proposal-id 12801 :visit-id "33" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:23:40.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 178480 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "33" :obset-id "33" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "33" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2698 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "33" :orbit-number 2 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "33" :orbit-number 3 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 232 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) false 3 0 Execute either Visit 32 or Visit 33, but not both. Using ephemeris for target 12801-41-PLUTO-CHARON-2ND-QUADRANT-PLUS ephemeris data for target 12801-41-PLUTO-CHARON-2ND-QUADRANT-PLUS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Pluto with its prograde rotation pole oriented downward, parallel to the UVIS Y-axis; Charon on the diagonal at upper right (2nd orbital quadrant). To be scheduled along with Visit 42 or 43. 1340982658000 187.99999999999994 (Tic-Visit :proposal-id 12801 :visit-id "41" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:23:50.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 178480 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "41" :obset-id "41" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "41" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2698 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "41" :orbit-number 2 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "41" :orbit-number 3 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 232 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) false 3 0 Using ephemeris for target 12801-42-PLUTO-CHARON-1ST-QUADRANT ephemeris data for target 12801-42-PLUTO-CHARON-1ST-QUADRANT does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Pluto with its prograde rotation pole pointed rightward, perpendicular to the UVIS Y-axis; Charon on the diagonal at upper right (1st orbital quadrant). To be scheduled along with Visit 41. Either Visit 42 or 43 must be scheduled, but not both. To match the position of Charon most accurately, the optimal timing of Visit 42 would be either 0.7 or 1.7 Charon orbits (4.43 or 10.82 days) later than Visit 41. (Tic-Visit :proposal-id 12801 :visit-id "42" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:23:54.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 178480 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "42" :obset-id "42" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "42" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2698 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "42" :orbit-number 2 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "42" :orbit-number 3 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 232 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) false 3 0 Execute either Visit42 or Visit 43, but not both. Using ephemeris for target 12801-43-PLUTO-CHARON-3RD-QUADRANT ephemeris data for target 12801-43-PLUTO-CHARON-3RD-QUADRANT does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Pluto with its prograde rotation pole oriented leftward, perpendicular to the UVIS Y-axis; Charon on the diagonal at upper right (3rd orbital quadrant). To be scheduled along with Visit 41. Either Visit 42 or 43 must be scheduled, but not both. To match the position of Charon most accurately, the optimal timing of Visit 43 would be either 0.8 or 1.8 Charon orbits (5.15 days or 11.53 days) earlier than Visit 41. 1339442816000 278.0 (Tic-Visit :proposal-id 12801 :visit-id "43" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:23:59.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 178480 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "43" :obset-id "43" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "43" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2698 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "43" :orbit-number 2 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "43" :orbit-number 3 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 232 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) false 3 0 Execute either Visit42 or Visit 43, but not both. Using ephemeris for target 12801-61-PLUTO-CHARON-4TH-QUADRANT ephemeris data for target 12801-61-PLUTO-CHARON-4TH-QUADRANT does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Pluto with its prograde rotation pole oriented downward, parallel to the UVIS Y-axis; Charon on the diagonal at lower left (4th orbital quadrant). To be scheduled along with Visit 62 or 63. 1340712624000 195.6882974281549 (Tic-Visit :proposal-id 12801 :visit-id "61" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:02.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 178480 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "61" :obset-id "61" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "61" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2698 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "61" :orbit-number 2 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "61" :orbit-number 3 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 232 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) false 3 0 Using ephemeris for target 12801-62-PLUTO-CHARON-3RD-QUADRANT ephemeris data for target 12801-62-PLUTO-CHARON-3RD-QUADRANT does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Pluto with its prograde rotation pole pointed rightward, perpendicular to the UVIS Y-axis; Charon on the diagonal at lower left (3rd orbital quadrant). To be scheduled along with Visit 61. Either Visit 62 or 63 must be scheduled, but not both. To match the position of Charon most accurately, the optimal timing of Visit 62 would be either 0.7 or 1.7 Charon orbits (4.43 or 10.82 days) later than Visit 61. (Tic-Visit :proposal-id 12801 :visit-id "62" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:06.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 178480 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "62" :obset-id "62" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "62" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2698 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "62" :orbit-number 2 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "62" :orbit-number 3 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 232 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) false 3 0 Execute either Visit 62 or Visit 63, but not both. Using ephemeris for target 12801-63-PLUTO-CHARON-1ST-QUADRANT ephemeris data for target 12801-63-PLUTO-CHARON-1ST-QUADRANT does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Pluto with its prograde rotation pole oriented leftward, perpendicular to the UVIS Y-axis; Charon on the diagonal at lower left (1st orbital quadrant). To be scheduled along with Visit 61. Either Visit 62 or 63 must be scheduled, but not both. To match the position of Charon most accurately, the optimal timing of Visit 63 would be either 0.8 or 1.8 Charon orbits (5.15 days or 11.53 days) earlier than Visit 61. (Tic-Visit :proposal-id 12801 :visit-id "63" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:09.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 178480 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "63" :obset-id "63" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "63" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2698 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "63" :orbit-number 2 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) (Tic-Orbit :proposal-id 12801 :visit-id "63" :orbit-number 3 :pcs-time 222 :si-vis-utilization 2837 :al-overhead-at-end 0 :internal-dur-at-end 232 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3126 :pcs-gap 0 ) false 3 0 Execute either Visit 62 or Visit 63, but not both. Using ephemeris for target 12801-70-PLUTO ephemeris data for target 12801-70-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([71 After 70 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 1 observations cover one half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. If there is any choice in when to schedule, this should be scheduled as close to the middle of the window as possible. Once the schedule is known, the roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. 1339212595000 246.0 (Tic-Visit :proposal-id 12801 :visit-id "70" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:14.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 155600 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "70" :obset-id "70" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "70" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2824 :al-overhead-at-end 0 :internal-dur-at-end 207 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-71-PLUTO ephemeris data for target 12801-71-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([71 After 70 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 1 observations cover one half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. Once the schedule is known, the relative roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. 1339218344000 250.5 (Tic-Visit :proposal-id 12801 :visit-id "71" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:16.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 155600 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "71" :obset-id "71" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "71" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2824 :al-overhead-at-end 0 :internal-dur-at-end 207 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-72-PLUTO ephemeris data for target 12801-72-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([73 After 72 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 1 observations cover one half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. If there is any choice in when to schedule, this should be scheduled as close to the middle of the window as possible. Once the schedule is known, the roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. 1339477060000 242.19999999999996 (Tic-Visit :proposal-id 12801 :visit-id "72" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:19.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 155600 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "72" :obset-id "72" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "72" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2824 :al-overhead-at-end 0 :internal-dur-at-end 207 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-73-PLUTO ephemeris data for target 12801-73-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([73 After 72 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 1 observations cover one half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. Once the schedule is known, the relative roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. 1339482810000 246.89999999999998 (Tic-Visit :proposal-id 12801 :visit-id "73" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:22.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 155600 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "73" :obset-id "73" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "73" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2824 :al-overhead-at-end 0 :internal-dur-at-end 207 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-74-PLUTO ephemeris data for target 12801-74-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([75 After 74 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 1 observations cover one half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. If there is any choice in when to schedule, this should be scheduled as close to the middle of the window as possible. Once the schedule is known, the roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. 1339776019000 246.29999999999995 (Tic-Visit :proposal-id 12801 :visit-id "74" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:24.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 155600 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "74" :obset-id "74" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "74" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2824 :al-overhead-at-end 0 :internal-dur-at-end 207 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-75-PLUTO ephemeris data for target 12801-75-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([75 After 74 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 1 observations cover one half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. Once the schedule is known, the relative roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. 1339781768000 251.09999999999997 (Tic-Visit :proposal-id 12801 :visit-id "75" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:26.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 155600 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "75" :obset-id "75" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "75" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2824 :al-overhead-at-end 0 :internal-dur-at-end 207 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-76-PLUTO ephemeris data for target 12801-76-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([77 After 76 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 1 observations cover one half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. If there is any choice in when to schedule, this should be scheduled as close to the middle of the window as possible. Once the schedule is known, the roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. 1340023186000 243.5 (Tic-Visit :proposal-id 12801 :visit-id "76" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:28.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 146448 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "76" :obset-id "76" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "76" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2656 :al-overhead-at-end 0 :internal-dur-at-end 197 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-77-PLUTO ephemeris data for target 12801-77-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([77 After 76 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 1 observations cover one half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. Once the schedule is known, the relative roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. 1340028933000 248.5 (Tic-Visit :proposal-id 12801 :visit-id "77" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:30.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 146448 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "77" :obset-id "77" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "77" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2656 :al-overhead-at-end 0 :internal-dur-at-end 197 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-78-PLUTO ephemeris data for target 12801-78-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([79 After 78 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 2 observations cover the second half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. These visits do not cover the second half of the region as well due to the available roll angles. This visit is not at the ideal time but its window is a compromise between the geometry desired and the roll angle needed. There is an extra +30 roll off the optimum for this program to compensate for this issue. If there is any choice in when to schedule, this should be scheduled as early in the window as possible. Once the schedule is known, the roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. 1340798794000 202.39999999999998 (Tic-Visit :proposal-id 12801 :visit-id "78" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:32.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 146448 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "78" :obset-id "78" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "78" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2656 :al-overhead-at-end 0 :internal-dur-at-end 197 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-79-PLUTO ephemeris data for target 12801-79-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([79 After 78 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 2 observations cover the second half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. These visits do not cover the second half of the region as well due to the available roll angles. Once the schedule is known, the relative roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. 1340804539000 206.29999999999998 (Tic-Visit :proposal-id 12801 :visit-id "79" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:35.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 146448 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "79" :obset-id "79" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "79" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2656 :al-overhead-at-end 0 :internal-dur-at-end 197 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-80-PLUTO ephemeris data for target 12801-80-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([81 After 80 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 2 observations cover the second half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. These visits do not cover the second half of the region as well due to the available roll angles. If there is any choice in when to schedule, this should be scheduled as close to the middle of the window as possible. Once the schedule is known, the roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. The gap in the BETWEEN window is to avoid a Pluto stellar occultation event. 1341057306000 178.7 (Tic-Visit :proposal-id 12801 :visit-id "80" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:37.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 146448 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "80" :obset-id "80" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "80" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2656 :al-overhead-at-end 0 :internal-dur-at-end 197 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-81-PLUTO ephemeris data for target 12801-81-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([81 After 80 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 2 observations cover the second half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. These visits do not cover the second half of the region as well due to the available roll angles. Once the schedule is known, the relative roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. 1341063051000 181.5 (Tic-Visit :proposal-id 12801 :visit-id "81" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:39.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 146448 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "81" :obset-id "81" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "81" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2656 :al-overhead-at-end 0 :internal-dur-at-end 197 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-82-PLUTO ephemeris data for target 12801-82-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([83 After 82 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 2 observations cover the second half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. These visits do not cover the second half of the region as well due to the available roll angles. If there is any choice in when to schedule, this should be scheduled in the second half of the window. Once the schedule is known, the roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. (Tic-Visit :proposal-id 12801 :visit-id "82" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:42.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 146448 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "82" :obset-id "82" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "82" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2656 :al-overhead-at-end 0 :internal-dur-at-end 197 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-83-PLUTO ephemeris data for target 12801-83-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([83 After 82 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 2 observations cover the second half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. These visits do not cover the second half of the region as well due to the available roll angles. Once the schedule is known, the relative roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. (Tic-Visit :proposal-id 12801 :visit-id "83" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:44.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 146448 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "83" :obset-id "83" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "83" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2656 :al-overhead-at-end 0 :internal-dur-at-end 197 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-84-PLUTO ephemeris data for target 12801-84-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([85 After 84 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 2 observations cover the second half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. These visits do not cover the second half of the region as well due to the available roll angles. This visit is not at the ideal time but its window is a compromise between the geometry desired and the roll angle needed. There is an extra -30 roll off the optimum for this program to compensate for this issue. If there is any choice in when to schedule, this should be scheduled as late in the window as possible. Once the schedule is known, the roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. (Tic-Visit :proposal-id 12801 :visit-id "84" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:23:02.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 146448 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "84" :obset-id "84" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "84" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2656 :al-overhead-at-end 0 :internal-dur-at-end 197 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0 Using ephemeris for target 12801-85-PLUTO ephemeris data for target 12801-85-PLUTO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 11.213 to 13.121. ephemeris interval: 12.121 to 14.121 Timing link suitability includes constraints ([85 After 84 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 20.0. CASM was run in Phase II mode. Part 2 observations cover the second half of the notional 1:2 MMR resonance zone. Visits appear in linked pairs where the roll between visits is set to put Charon at the same PA in the two visits. Each visit has a timing constraint and a roll constraint that causes Charon to be either directly above or directly below Pluto on the image. This puts the prime search region to the left or right of the bleeding trails from the saturated Pluto and Charon images. These visits do not cover the second half of the region as well due to the available roll angles. Once the schedule is known, the relative roll angle may need a small adjustment to refine the placement of all targets and regions on the WFC3 focal plane. (Tic-Visit :proposal-id 12801 :visit-id "85" :proposal-version -1 :trans-version "20120125" :date "08-May-2012 16:24:46.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 146448 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12801 :visit-id "85" :obset-id "85" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12801 :visit-id "85" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2656 :al-overhead-at-end 0 :internal-dur-at-end 197 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3234 :pcs-gap 0 ) false 1 0