Table 1
Parameters specific to the CDA and geometric parameters for the Enceladus flybys considered in this paper.
| Flyby | Date | Data type | Relative speed [km s−1] | Detectable range of grains radii(a) [µm] | Altitude at C/A [km] | N Lat, W Lon of C/A | Enceladus mean anomaly |
|---|---|---|---|---|---|---|---|
| E7 | 2 Nov. 2009 | HRD | 7.7 | M1: (1.7,∞) | 99 | -89°, 137° | 283° |
| M2: (3.1,∞) | |||||||
| M3: (6.7,∞) | |||||||
| m′1: (1.8,∞) | |||||||
| m′2: (3.1,∞) | |||||||
| E21 | 28 Oct. 2015 | HRD | 8.5 | M1: (1.6,∞) | 49 | −84°, 70° | 84° |
| M2: (2.8,∞) | |||||||
| M3: (6.2,∞) | |||||||
| m′1: (1.6,∞) | |||||||
| m′2: (2.9,∞) | |||||||
| E5 | 9 Oct. 2008 | DA | 17.7 | salt-poor: (0.2, 1.7) | 25 | −28°, 101° | 208° |
| salt-rich: (0.1, 1.1) | |||||||
| E17 | 27 Mar. 2012 | DA | 7.5 | salt-poor: (0.8, 6.2) | 74 | −86°, 154° | 209° |
| salt-rich: (0.5, 4.1) | |||||||
| E18 | 14 Apr. 2012 | DA | 7.5 | salt-poor: (0.8, 6.2) | 74 | −88°, 280° | 200° |
| salt-rich: (0.5, 4.1) |
Notes. The first column denotes the flyby, and the second column shows the CDA subsystem that obtained the data analyzed in this paper. The third column gives the velocity of the spacecraft relative to Enceladus. The fourth column denotes for E7 and E21 the HRD counters for which a rate profile was obtained, along with the range of grain radius the counter was sensitive to. For the E5, E17, and E18 encounters, this column gives the respective sensitive size range for the CA subsystem for salt-rich and salt-poor grains. Columns five, six, and eight give geometric parameters of the encounter, and column seven specifies the date of the flyby. (a)The derivation of the detectable size ranges for salt-poor and salt-rich particles (E5, E17, E18) is given in Sect. 2.1. The derivation of the HRD size thresholds is given in Sect. 2.3.
Current usage metrics show cumulative count of Article Views (full-text article views including HTML views, PDF and ePub downloads, according to the available data) and Abstracts Views on Vision4Press platform.
Data correspond to usage on the plateform after 2015. The current usage metrics is available 48-96 hours after online publication and is updated daily on week days.
Initial download of the metrics may take a while.