Results for “Perigee” — Page 21

NASA NTRSDate not supplied

Mission Design & Operations Approach for the HelioSwarm Mission

HelioSwarm: The Nature of Turbulence in Space Plasmas is a transformational mission to explore the dynamic three-dimensional mechanisms controlling the physics of plasma turbulence, a ubiquitous process occurring in the heliosphere and plasmas throughout the universe. Turbulence is the process by which energy contained in fluctuating magnetic fields and plasma motion cascades from large to smaller spatial scales. HelioSwarm achieves its science goals by making simultaneous measurements across a wide range of measurement baselines, spanning magnetohydrodynamic scales (1000’s of km) to sub-ion heating scales (10’s of km), using a novel nine-spacecraft swarm. The swarm operates in a high-altitude lunar resonant Earth orbit (two-week period, ~63 RE apogee, ~13 RE perigee), giving it access to both the pristine solar wind and regions of strongly driven turbulence (specifically the magnetosphere and foreshock), and utilizes customized relative orbital motion of the swarm members to produce the range of measurement baselines and configurations. The swarm comprises eight “node” spacecraft, manufactured by Blue Canyon Technologies, and a “hub” spacecraft produced by Northrop Grumman Corp. The hub serves as a communications relay, with all communications between the ground and the nodes flowing through it. Mission operations are conducted within the Multi-Mission Operations Center at the NASA Ames Research Center and science operations at the University of New Hampshire, Durham. HelioSwarm was selected in 2022 as one of NASA’s newest Heliophysics Explorer missions to proceed from mission concept into mission implementation, with a target launch in 2029. This paper provides an overview of the mission’s science goals and objectives, the mission design, and the concept of operations, with an emphasis on how the swarm aspects of the mission both enable the science measurements and present unique operational challenges. The paper then describes the proposed development approach for the mission operations system and ground data system which relies on a selective combination of scaling strategies to meet the challenges.

HelioSwarm↗

NASA NTRSDate not supplied

An Investigation Into Transecting Satellites in Future Space Traffic Management Scenarios

The number of satellites expected to populate the near-Earth space environment is set to dramatically increase in the coming decade as new large constellations are approved and deployed. Current strategies for placing new batches of these satellites on orbit often involve launching into an initial orbit, and then performing apogee raising maneuvers to reach a target altitude. Similarly, end-of-life planning for these constellation satellites can consist of de-orbit burns that lower perigee to permit disposal via re-entry. Both the raising and de-orbiting maneuvers can result in the individual satellites traveling in high-eccentricity orbits that have the potential to transect other spacecraft trajectories. While individual large constellations may be able to coexist in separate altitude and inclination bands, having thousands of satellites moving between these bands as new satellites are replaced and old ones are removed could pose additional collision risks. Similar concerns have been raised regarding the impact that large numbers of university-class CubeSats might have in terms of their overall collision risk, especially as these satellites typically do not have propulsion systems for active maneuvering. To assess the impact that transecting satellites might have to future space traffic management strategies, this study explored a variety of future realistic scenarios using a high-fidelity simulation tool. The model can simulate the orbit of tens of thousands of resident space objects (RSOs) simultaneously, to include active satellites, debris, rocket bodies, or even future hypothetical scenarios, using a realistic force model that incorporates non-spherical gravity, atmospheric drag, solar radiation pressure, and more. As the model is run forward in time, various statistics and meta-data are gathered on any predicted conjunction event, providing insight into the nature and frequency of potential collisions, e.g., what size are the two satellites, who operates the satellites, are they active or passive objects, etc. Additional customization is available in terms of how probability of collision is computed, and how the probability ellipsoids and screening volumes are determined. The simulation tool also allows for rule-based maneuvers for active satellites, e.g, given an advance conjunction “warning,” one or both of the satellites can maneuver to a safe distance. A wide range of maneuvers can be implemented using impulsive or low-thrust methods, and the latencies can also be varied, e.g., using maneuver lead times of 48 hours, 24 hours, or 12 hours. Validation of the simulation results is performed against current and historical datasets available, to include comparisons to prior conjunction data messages (CDMs), object properties (mass, volume, etc.), and two-line-element records from both public and internal sources. Using the simulation environment, an assessment on the general risks that transecting satellites might pose for hypothetical future space object environments will be presented. This will involve the simulation of approximately 50,000 new large constellation satellites, in addition to the existing catalog of approximately 20,000 known resident space objects (RSOs), over propagation periods of one month to one year. A description of the simulation methodologies, scenarios evaluated, and validation methods will also be presented, as well as a preliminary assessment of the effectiveness of several candidate maneuver strategies that have the potential to reduce collision risk between active satellites.

Brian Gunter↗

NASA NTRSDate not supplied

An Investigation Into Transecting Satellites in Future Space Traffic Management Scenarios

The number of satellites expected to populate the near-Earth space environment is set to dramatically increase in the coming decade as new large constellations are approved and deployed. Current strategies for deploying new batches of these satellites often involve launching into an initial orbit, and then performing apogee raising maneuvers to reach a target altitude. Similarly, end-of-life planning for these constellation satellites can consist of de-orbit burns that lower perigee to permit disposal via re-entry. Both the raising and de-orbiting maneuvers can result in the individual satellites traveling in transecting orbits that have the potential to cross other spacecraft trajectories. While individual large constellations may be able to coexist in separate altitude and inclination bands, having thousands of satellites moving between these bands as new satellites are added and old satellites are removed could pose additional collision risks. Similar concerns have been raised regarding the impact that large numbers of university-class CubeSats might have in terms of their overall collision risk, especially as these satellites typically do not have propulsion systems for active maneuvering. To assess the impact that transecting satellites might have on future space traffic management strategies, this study explored a variety of realistic future scenarios using a high-fidelity simulation tool. The model can simulate the orbit of tens of thousands of resident space objects (RSOs) simultaneously, to include active satellites, debris, rocket bodies, or even future hypothetical satellite constellations, using a realistic force model that incorporates non-spherical gravity, atmospheric drag, and solar radiation pressure, as well as station-keeping. The simulation can be customized to accommodate different methods of calculating the probability of collision, as well as the process for determining probability ellipsoids and screening volumes. This makes it possible to replicate, and compare, different processes used by different spacecraft operators and space situational awareness (SSA) providers. As the model is run forward in time, each conjunction event is recorded, allowing for the analysis of statistics and meta-data related to these events, providing insight into the nature and frequency of potential collisions, such as whether are they active or passive objects, what size are the two objects, and who owns the objects (if known). This information makes it possible to characterize how changes to the status quo affect the number and type of conjunctions that occur, as well as the distributional effects on various types of satellite operators. To assess the general risks that transecting satellites might pose for hypothetical future space object environments, approximately 60,000 new large constellation satellites were considered, in addition to the existing catalog of approximately 7800 known resident space objects (RSOs), over a simulation period of one year. The results indicate that the future space environment will introduce a non-linear increase in conjunction events as the number of RSOs also increase. This will require adjustments to spacecraft fuel budgets in order to conduct the avoidance maneuvers necessary to minimize collision risk, both for existing and new satellites. This increase is due in large part to the higher density of RSOs and the overlap between some constellation orbits. Current catalog objects were shown to require three times more ∆V for collision avoidance (CA) maneuvers in the simulated future environment, and some constellation spacecraft were estimated to devote the majority of their annual ∆V to CA. The impact of small satellites was found to be proportional for the current space environment, and actually decreased in terms of percentage for the future scenario, suggesting that small satellites do not pose an outsized collision risk. Lastly, transecting satellites were found to contribute thousands of additional conjunctions outside of their operational orbit, and may require up to an additional 5% in CA maneuver fuel allocation.

conjunction assessment↗

NASA NTRS2023

TESS Data Release Notes: Sector 61, DR86

TESS Sector 61 observations include physical orbits 129 and 130 of the spacecraft around the Earth. Data collection was paused for a total of 0.63 days to download data. Data were downloaded approximately every seven days, once near apogee of each orbit and once near perigee. In total, there are 24.80 days of science data collected in Sector 61.

TESS↗

NASA NTRS2023

TESS Data Release Notes: Sector 62, DR88

TESS Sector 62 observations include physical orbits 131 and 132 of the spacecraft around the Earth. Data collection was paused for a total of 0.63 days to download data. Data were downloaded approximately every seven days, once near apogee of each orbit and once near perigee. In total, there are 25.08 days of science data collected in Sector 62.

TESS↗

NASA NTRS2023

TESS Data Release Notes: Sector 58, DR83

TESS Sector 58 observations include physical orbits 123 and 124 of the spacecraft around the Earth. Data collection was paused for a total of 0.63 days to download data. Data were downloaded approximately every seven days, once near apogee of each orbit and once near perigee. In total, there are 27.09 days of science data collected in Sector 58.

TESS↗

NASA NTRS2023

TESS Data Release Notes: Sector 59, DR84

TESS Sector 59 observations include physical orbits 125 and 126 of the spacecraft around the Earth. Data collection was paused for a total of 0.63 days to download data. Data were downloaded approximately every seven days, once near apogee of each orbit and once near perigee. Note that the Sector 59 data were briefly made available on 2023 January 18–19 before an issue was identified that required reprocessing. Data have since been reprocessed. The reprocessing has a minimal impact on the final light curves, but resulted in a different set of TCEs than initially released. Users should re-download the data if retrieved before January 19th. In total, there are 25.79 days of science data collected in Sector 59.

TESS↗

NASA NTRS2023

TESS Data Release Notes: Sector 60, DR85

TESS Sector 60 observations include physical orbits 127 and 128 of the spacecraft around the Earth. Data collection was paused for a total of 0.63 days to download data. Data were downloaded approximately every seven days, once near apogee of each orbit and once near perigee. At TJD 2949.99, the spacecraft entered into safe mode, resulting in instrument turn-off until TJD 2955.04. There are no FFIs, target pixel file data, or light curve data during this time. During these times (as well as when the spacecraft is transmitting data to ground systems) the data and timestamps in target-pixel files and light curve files are set to NULL. One FFI from Camera 1 in orbit 127 was corrupted prior to downlink from the spacecraft and could not be recovered. The FFIINDEX number is 00738895 (timestamp 2022358084201), and no FFI file for Camera 1 was produced for this cadence. In total, there are 20.01 days of science data collected in Sector 60.

TESS↗

NASA NTRS2023

Radioastron Discovery of A Mini-Cocoon Around the Restarted Parsec-Scale Jet in 3C 84

We present RadioAstron space-based very long baseline interferometry (VLBI) observations of the nearby radio galaxy 3C 84 (NGC 1275) at the centre of the Perseus cluster. The observations were carried out during a perigee passage of the Spektr-R spacecraft on September 21–22, 2013 and involved a global array of 24 ground radio telescopes observing at 5 GHz and 22 GHz, together with the Space Radio Telescope (SRT). Furthermore, the Very Long Baseline Array (VLBA) and the phased Very Large Array (VLA) observed the source quasi-simultaneously at 15 GHz and 43 GHz. Fringes between the ground array and the SRT were detected on baseline lengths up to 8.1 times the Earth’s diameter, providing unprecedented resolution for 3C 84 at these wavelengths. We note that the corresponding fringe spacing is 125 μas at 5 GHz and 27 μas at 22 GHz. Our space-VLBI images reveal a previously unseen sub-structure inside the compact ∼1 pc long jet that was ejected about ten years earlier. In the 5 GHz image, we detected, for the first time, low-intensity emission from a cocoon-like structure around the restarted jet. Our results suggest that the increased power of the young jet is inflating a bubble of hot plasma as it carves its way through the ambient medium of the central region of the galaxy. Here, we estimate the minimum energy stored in the mini-cocoon, along with its pressure, volume, expansion speed, and the ratio of heavy particles to relativistic electrons, as well as the density of the ambient medium. About half of the energy delivered by the jet is dumped into the mini-cocoon and the quasi-spherical shape of the bubble suggests that this energy may be transferred to a significantly larger volume of the interstellar medium than what would be accomplished by the well-collimated jet on its own. The pressure of the hot mini-cocoon also provides a natural explanation for the almost cylindrical jet profile seen in the 22 GHz RadioAstron image.

galaxies: jets↗

NASA NTRSDate not supplied

Decision Aid for Conjunction Risk Mitigation by Differential Drag

In the previous five years, the rate of conjunctions that the NASA Conjunction Assessment Risk Analysis (CARA) team processed and analyzed has more than tripled. (NASA CARA, 2024) New missions in the early development phases are now required to plan for dealing with conjunctions under the present space environment, and also projecting forward into a future likely with even further increased utilization of the space environment. Some missions are investigating the possibility of using differential drag to remediate conjunctions without expending limited fuel or for missions without propulsive capabilities. The NASA CARA team studied the historical record of conjunctions to evaluate the circumstances under which differential drag may be successfully applied and have developed a series of tables to use as a decision aid for missions considering differential drag. CARA records all conjunctions of their protected payloads, with historical records starting in 2005 (with significant conjunction events starting to occur on or after 2013). From this record, approximately 7,300 had a probability of collision (Pc) greater than 1 in 10,000, the nominal requirement for a risk mitigation maneuver (RMM) to be made per NASA Procedural Requirements (NPR) 8079.1 (NASA, 2023), at 3 days prior to the time of closest approach, the time analyzed for differential drag efficacy. CARA’s maneuver trade space tool (MTS) was used to prop-agate the primary satellite forward from that decision point with varying degrees of increase to ballistic coefficient (BC), and then recalculate the Pc to evaluate whether or not the conjunction was mitigated (Pc < 3E-6). These results were then binned and sorted along several axes, including altitude, amount of delta-BC, and (pre-maneuver) rate of energy dissipation, to identify underlying patterns. The altitude plot is shown in Figure 1. We found that differential drag was most successful for satellites with perigees below 560 km, and which could adopt an average delta-BC of 2 or greater (that is, increasing their ballistic coefficient by a factor of 3). However, this is a difficult threshold for a mission to clear; very few spacecraft are capable of adopting a high-drag configuration for 72 hours continuously. Planet’s Dove spacecraft use differential drag to remediate conjunctions (Griffith, et al., 2021), and they have a maximum delta-BC factor of 9, but in practice (with mission and charging constraints) they achieve a time-averaged delta-BC that is closer to 2 (Foster, et al., 2017). In contrast, a NASA mission in development reached out to CARA to evaluate the utility of differential drag to remediate potential conjunctions for a spacecraft which is capable of a similar high delta-BC, but with operational constraints that limit their time-averaged delta-BC to less than 1. CARA has developed tables that can be used as decision aids to advise missions-in-development about the best way to utilize their differential drag capabilities. For missions below 560 km with the operational flexibility to devote multiple days to holding a high-drag configuration (or a sufficiently high drag ratio to compensate for limitations on that time), they are able to successfully remediate high-risk conjunctions. Conversely, missions that do not meet these ex-acting criteria – most missions – can instead be advised to use on-board propulsion systems to perform RMMs or to turn their minimum-area face towards the approach vector, thereby reducing Pc at the moment of conjunction. (NASA, 2023)

risk mitigation↗

NASA NTRSDate not supplied

OSIRIS-REx Screening Experience & Lessons Learned

On September 24, 2023, the NASA OSIRIS-REx spacecraft returned a sample of asteroid Bennu, approaching on a hyperbolic impact trajectory relative to Earth. At approximately 108,000 km altitude and four hours prior to hitting the top of the atmosphere, the Sample Return Capsule (SRC) separated from the spacecraft bus, targeting the Utah Test and Training Range. Twenty minutes later, the bus performed a large divert maneuver to fly by at a perigee altitude of ~780 km. Given the immense scientific value of the sample, substantial efforts were undertaken by NASA CARA and the OSIRIS-REx mission to ensure safe passage of the objects from GEO through LEO. This presentation provides an overview of collision avoidance maneuver (CAM) options, results of screenings, coordination with DoD for contingency observations, and lessons learned for screening future Earth flyby and entry trajectories. Two particular challenges included screening two objects using a much larger than normal 250 km spherical monitor volume and decision planning for a single CAM while the SRC was still attached that would alter both trajectories. The larger, non-standard screening volume resulted in custom procedures that CARA personnel had to run manually for each screening, and the initial long propagation times while the objects were more than a week out required significant computing resources. With a single CAM opportunity at 13 hours out, the decision to execute a maneuver had to consider the risk to both objects, where one could imagine a situation where the maneuver would clear a high-risk conjunction for one object and introduce one for the other – begging the question of relative risk posture between the SRC and bus. These among other unique aspects of Earth flyby and entry missions led to novel planning and implementation procedures to support future missions of this type.

Dolan E. Highsmith↗

NASA NTRSDate not supplied

Decision Aid for Conjunction Risk Mitigation by Differential Drag

In the previous five years, the rate of conjunctions that the NASA Conjunction Assessment Risk Analysis (CARA) team processed and analyzed has more than tripled. (NASA CARA, 2024) New missions in the early development phases are now required to plan for dealing with conjunctions under the present space environment, and also projecting forward into a future likely with even further increased utilization of the space environment. Some missions are investigating the possibility of using differential drag to remediate conjunctions without expending limited fuel or for missions without propulsive capabilities. The NASA CARA team studied the historical record of conjunctions to evaluate the circumstances under which differential drag may be successfully applied and have developed a series of tables to use as a decision aid for missions considering differential drag. Currently, if a CARA-protected mission with maneuvering capabilities is predicted to have a conjunction with probability of collision (Pc) greater than 7E-5 (the default value of the ‘yellow threshold’, which may have some other value agreed by CARA and the mission during the Orbital Collison Avoidance Planning (OCAP) process), CARA will use its Maneuver Trade Space (MTS) tool to evaluate and recommend options for the timing and magnitude of a risk mitigation maneuver (RMM), based on the mission’s capabilities. If the conjunction’s Pc is greater than 1E-4, the ‘red threshold’, then an RMM must be executed per NASA Procedural Requirements (NPR) 8079.1 (NASA, 2023), although missions may execute an RMM even if the Pc is lower. The magnitude of the maneuver is typically a few cm/s, and CARA estimates how many will be required for the mission’s nominal lifetime – typically a few per year – during the OCAP process, to inform the mission’s delta-V requirement. For traditional satellites, this is usually smaller than other requirements for orbit insertion, maintenance, and disposal, but for CubeSats or other small satellite missions, a propulsion system may not provide much more than a few cm/s of delta-V or may not fit at all within the available budget of money, time, size, weight, and/or power (SWaP). Conversely, CubeSats often have deployable solar panels, which offer the capacity to have much higher areas facing some directions than others. Such a mission can instead use ‘differential drag’ to remediate a conjunction -- in other words, change its drag area (usually increasing) to deviate from the predicted collision course. This is how Planet’s Dove spacecraft maintain their formations and remediate conjunction risks without having on-board propulsion (Foster, et al., 2017) (Griffith, et al., 2021). CARA has been developing improvements to MTS to support differential-drag for NASA's missions -- where it is effective. CARA records all conjunctions of their protected payloads, with historical records starting in 2005 (with significant conjunction events starting to occur on or after 2013). From this record, approximately 7,300 had a Pc greater than 1E-4 at 3 days prior to the time of closest approach, the time analyzed for differential drag efficacy. Of those, approximately 4,300 had fully-defined covariance matrices stored for both the primary and secondary objects; this set of conjunctions is the basis for the analysis of this work. CARA’s MTS tool was used to propagate the primary satellite forward from that decision point with varying degrees of increase to ballistic coefficient (BC). Because these conjunctions came from multiple missions, the nondimensional ‘delta-BC’ factor was used to quantify and normalize the increase in ballistic coefficient, defined as follows: Delta-BC = BC_new / BC_old - 1 Positive delta-BC factors represent an increase in drag compared to the nominal attitude, while negative delta-BC factors (to a minimum of -1) represent a decrease in drag. At the conclusion of the differential-drag ‘maneuver’, the Pc was recalculated to evaluate whether or not the conjunction was mitigated (Pc < 3E-6). These results were then binned and sorted along several axes, including altitude, amount of delta-BC, and (pre-maneuver) rate of energy dissipation (EDR), to identify underlying patterns. The altitude plot is shown in Figure 1. To validate this analysis, we consulted the record of a NASA mission which uses differential drag to maintain its orbit and remediate conjunction risk. CARA’s empirical record of the mission’s orbit history suggests it achieves a delta-BC of 2.2. Of the twenty-one RMM plans that were submitted by this mission, eighteen were matched with conjunctions in the historical record; of those, twelve were successfully remediated (final measured Pc < 3E-6), and six were not. This is consistent with the expected efficacy for missions orbiting at that altitude. We are presently simulating this mission’s RMMs with MTS; this work is ongoing, but so far, the MTS results are qualitatively in agreement with the empirical results -- correctly predicting that a maneuver would or would not remediate a conjunction, if not exactly matching the final post-remediation Pc value. We found that differential drag was most successful for satellites with perigees below 560 km, and which could adopt an average delta-BC of 2 or greater (that is, increasing their ballistic coefficient by a factor of 3). However, this is a difficult threshold for a mission to clear; very few spacecraft are capable of adopting a high-drag configuration for 72 hours continuously. Planet’s Dove spacecraft use differential drag to remediate conjunctions (Griffith, et al., 2021), and they have a maximum delta-BC factor of 9, but in practice (with mission and charging constraints) they achieve a time-averaged delta-BC that is closer to 2 (Foster, et al., 2017). A mission’s differential drag utility strongly depends on the operational constraints that has the capacity to limit the time-averaged delta-BC. A mission with a high maximum delta-BC of 5 or more can have an effective delta-BC of less than 1 due to operational constraints such as instrument and solar panel pointing, especially if this constraint results in holding an intermediate drag value for most of its orbit. CARA has developed tables that can be used as decision aids to advise missions-in-development about the best way to utilize their differential drag capabilities. For missions below 560 km with the operational flexibility to devote multiple days to holding a high-drag configuration (or a sufficiently high drag ratio to compensate for limitations on that time), they are -- more likely than not -- able to successfully remediate high-risk conjunctions. Conversely, missions that do not meet these exacting criteria -- most missions -- can instead be advised to use on-board propulsion systems to perform RMMs, or to turn their minimum-area face towards the approach vector, thereby reducing Pc at the moment of conjunction due to the decreased Hard-Body Radius (HBR), that is a strongly correlated variable in the Pc calculations. (NASA, 2023)

conjunction assessment↗

NASA NTRSDate not supplied

Decision Aid for Conjunction Risk Mitigation by Differential Drag

The NASA Conjunction Assessment Risk Analysis (CARA) team has conducted are view of the historical record of high-risk conjunctions involving CARA-protected missions and evaluated whether (and how much) differential drag can provide effective mitigation. From this analysis, CARA has identified a rule of thumb: missions with perigees below 560 km capable of tripling their drag area for 72 hours(or a larger scale factor for a lesser amount of time) can reliably use differential drag to remediate high-risk events.

mission design↗