1. EOS Aura Science Team Meeting
Report from the Mission Operations Working Group (MOWG) Meeting October 28, 2008
Angie Kelly
EOS Science Interface Manager
Constellation Team Manager
NASA Goddard Space Flight Center
Greenbelt, Md

2. EOS AURA Mission Operations Working Group Meeting
AGENDA
EOS AURA Mission Operations Working Group Meeting
12:30
Greetings/Introduction/Agenda Review
All
12:40
EOS Update
A. Kelly
1:00
Aura Status
B. Guit
1:20
HIRDLS
C. Hepplewhite, J. Barnett
1:40
MLS
D. Miller/D. Cuddy
2:00
OMIS
J. Claas
2:20
OMI DB in Sodankyla
O. Aulamo
2:40
TES
R. Murdock
3:00
BREAK (15 minutes)
3:15
FD Report: Aura Relocation, Debris Avoidance, Inclination Maneuvers, etc.
J. Levi
3:35
EDOS Status
T. Wood
3:55
Ground System Re-engineering Plans & Schedule
P. Johnson
4:15
Introduction: FOT Hot Topics (see Operations Splinter Sessions below)
D. Mantziaras
4:30
Summary/Actions/Next Steps
4:45 -7:00
FOT Hot Topics Splinter Session (2.25 hours)
FOT and IOTs

3. MOWG Meeting Attendees Columbia, Maryland October 2008
GSFC

4. Aura Mission Operations Status
Topics
Major Activities & Events Since Oct 2007
Aura Relocation
Spacecraft Subsystems Summary
Anomalies
Planned Activities
Propellant Usage & Lifetime Estimates
Overall Summary
Additional Information
Aura Mission Operations Status

5. Major Activities/Events (Since last Science Team Meeting on 10/02/07)
• Aura Relocation- completed May 2008
• 06/26/08: Debris Avoidance Maneuver
07/15/08: 4-Year Anniversary
08/15/08: HQ Mission Status Review
Continuing Upgrade of the Ground System
Replacement and upgrade of hardware and software in the Mission Operations Center due to aging hardware/software and new security requirements
EOS Data Capture and Level Zero Processing (EDOS) Upgrade: enhanced capability to support future missions, e.g., data capture up to 500 Mbps (Dec 2008)
Aura Mission Operations Status

6. Aura Relocation In the Afternoon Constellation (A-Train)
CALIPSO
There are currently 5 satellites in the “A-Train”: Aqua, CloudSat, CALIPSO, PARASOL, and Aura.
OCO and Glory missions will launch in January and June 2009, respectively
Mission
MLT
Aqua
01:37:24
CloudSat
01:46:13
CALIPSO
01:46:24
PARASOL
01:36:22
Aura
01:46:00
CloudSat
As of October 22, 2008
GSFC

7. Aura Rephasing (1 of 2)
At the request of the Aura Project Scientist, Aura was moved from its current location (15 minutes behind Aqua) to ~ 8 minutes behind Aqua—completed on May 8, 2008
Aura is now on a different ground track than Aqua (+18 kilometer (East) offset of Aqua’s WRS-2 path) to enable MLS/CloudSat viewing goal
Aura FOT is maintaining the Control Box to ±10 km (±20 km requirement)
A-Train Control Box Configuration
GSFC 7

8. Aura MLS now sees the same air mass as CloudSat and CALIPSO
Aura Rephasing (2 of 2)
Aura MLS now sees the same air mass as CloudSat and CALIPSO
Ground track
(WRS Paths)
Equator
CloudSat ground track
Orbit Plane
MLTAN – 13:35 13:44
Aqua
PARASOL
MLS
AIRS +/- 825 km
MODIS +/ km
OMI +/ km N
MLS Limb track
Aura
CloudSat
CALIPSO
8 min
7 min
~7 min 10 sec
GSFC 8

9. Spacecraft Subsystems Status
COMMENTS
Command & Data Handling (CDH)
Solid State Recorder (SSR) holds 3 orbits of data
Nominal
SSR Formatter Multiplexer Unit (FMU) Anomaly (Dec 4, 2007)
Communications (COMM)
Electrical Power System (EPS)
Solar Panel Connector Anomaly (Jan 12, 2005)
Flight Software (FSW)
Guidance, Navigation & Control (GN&C)
Propulsion (PROP)
Dual Thruster Module (DTM-3) Anomaly (Aug 16, 2005)
Thermal Control System (TCS)
All subsystems are configured to primary hardware.
Aura Mission Operations Status

10. Anomalies Since October 2007
• 12/4/07: Solid State Recorder Anomaly
-- Intensive investigation and contingency planning (Jan- March 2008)
03/17/08: HIRDLS Chopper Shutdown
Ongoing recovery activities
05/11/08: OMI Row Anomaly #2
05/29/08: MLS THz Module SIF5 Electronics Anomaly
06/01 – 06/04/08: MLS Filter Band 07 Anomaly
06/09 – 6/12/08: TES to Safe Mode – ICS Only
10/01/08: JPL reported rapid decline in MLS Band 32 Channels 3 & 4
10/13/08: JPL reported Band 32 Channels 3 & 4 have recovered to 96% of their original values and are acceptable for normal science data processing
Aura Mission Operations Status

11. Aura Mission Operations Status
Planned Activities
12/11/08: Drag Make Up Maneuver #16
2009 Inclination Adjust Maneuvers (IAMs)
9-burn sequence over 8-weeks
March 11th, 17th & 19th
April 1st, 7th , 9th , 22nd , 28th & 30th
May 5th , 6th & 7th (Back-Up Dates)
degree delta-I; m/s delta-V
21.0 Kg
Dec 31, 2008: Leap Second
2009 Senior Review (Mission Ops Input)
How long can the mission last?
OCO (1/15/09) and Glory(6/15/09) Launches
Aura Mission Operations Status

12. Aura Mission Operations Status
Aqua/Aura Inclination Adjust Maneuvers (DRAFT Schedule for March – May 2009)
Sun
Mon
Tue
Wed
Thu
Fri
Sat
8 March 9
10 Aqua IAM #16
11 Aura IAM #13
12 Aqua IAM #17 13 14 15 16
17 Aura IAM #14
18 Aqua IAM #18
19 Aura IAM #15
20 EQUINOX 21 22 23
24 Contingency
25 Contingency
26 Contingency 27 28 29 30
31 Aqua IAM #19
1 April
Aura IAM #16
2 Aqua IAM #20
OPTIMUM DATE 3 4 5 6
7 Aura IAM #17
8 Aqua IAM #21
9 Aura IAM #18 10 11 12
14 Contingency
15 Contingency
16 Contingency 17 18 19 20
21 Aqua IAM #22
22 Aura IAM #19
23 Aqua IAM #23 24 25 26
28 Aura IAM #20
29 Aqua IAM #24
30 Aura IAM #21
1 May 2
5 Back Up IAM
6 Back Up IAM
7 Back Up IAM 8
Aura Mission Operations Status

13. Aura Mission Operations Status
Maneuver Locations
Aura Mission Operations Status

14. Aura Fuel Usage: (Actual & Predicted)
Fall 2004 Delta-i Maneuvers
Annual Delta-i Maneuvers
Fall 2006 Delta-i Maneuvers
Spring 2009 Delta-i Maneuvers
Spring 2007 Delta-i Maneuvers
Aura Mission Operations Status

15. MOWG Focus
GOAL: Continued operation of the spacecraft and instruments as they age
Understanding the current state of the instruments regarding any changes that may affect performance or data products
How to adjust operations in order to prolong instrument life and science mission
Understanding what are the various conditions that can cause an instrument to go to an “undesirable” state and implementing procedures to avoid them
Mutual understanding/detailed procedures between the FOT and IOT on how to deal with critical situations, i.e., red flags
Projected lifetime of the instrument based on current state

16. Aura Mission Operations Status
Summary
Spacecraft Status - GREEN
Instrument Status - GREEN
HIRDLS: Reduced Aperture; chopper recovery in progress
Chopper began exhibiting anomalous behavior in November 2006
Chopper Stalled March 17, 2008 (unable to re-start to date)
9/10/08: Initiated auto re-start Macro ~ 288 restart attempts/day
MLS: Operating Normally
Band 13 measurements suspended February 2006
THz Band 17 currently out of lock
OMI: Operating Normally
Two (2) Field-of-View Row Anomalies (September 2007 & May 2008)
TES: Operating Normally
August 2008: Modified Global Survey Observations to extend ICS lifetime
Implemented new Lubrication Macro to extend ICS lifetime
Data Capture/L0 Processing Status – GREEN
SSR Data Capture to 09/30/2008: %*
Ground Systems
Continuing ground system upgrade and technology refresh
Preparing for Senior Review in 2009 (First time)
Aura Mission Operations Status

17. Thank you! Questions?
GSFC

18. Aura Mission Operations Status
Additional Charts -
Aura Mission Operations Status

19. Aura’s Neighborhood (705 km Orbit)
GSFC

20. Earth Science Morning Constellation
SAC-C is staying 2 km above Landsat-7 & Terra
EO-1 is currently 15 km below Landsat-7 & Terra
Operating on a 2-year extension through 2009
Has enough propellant to last through 2011
• Terra and LandSat-7 are continuinng operations at 705 km.
Mission
MLT
Terra
10:30:03
EO-1
09:59:56
Landsat-7
10:01:03
SAC-C
08:14:41
Original Morning Constellation configuration
As of October 22, 2008
GSFC

21. Orbital Debris Avoidance
GSFC

22. Debris Avoidance
A number of missions are in a 705 km sun-synchronous polar orbit.
55 other objects reside in orbits with mean altitudes of 705 +/- 5 km, including, A-Train missions, Terra, EO-1, Landsat-5 and -7, and six Iridium satellites.
More than 1500 cataloged objects pass through this regime each day.
On average, one object comes close
Within 5 km of each constellation mission each day
Within 2 km of each constellation mission once or twice a week.
ESMO has a task with the DOD’s Joint Space Operations Center (JSpOC) to screen all A-Train and Morning Constellation missions to ensure their safety.

23. Debris Avoidance Maneuvers During June 2007 – July 2008
Aura performed a 2-second burn on June 26, 2008 to avoid a piece of well-tracked debris from a U.S. satellite.
CloudSat performed two small maneuvers on July 20 and 22, 2008 to avoid debris from a Delta I LV.
PARASOL performed an early drag make-up maneuver on October 20, 2008 to avoid a space object.
PARASOL is planning a possible avoidance maneuver on October 27
Terra is evaluating a debris avoidance maneuver this week

24. Aura Mission Operations Status
Spacecraft Anomalies
Command & Data Handling (C&DH) Subsystem Formatter Multiplexer Unit/Solid State Recorder (FMU/SSR) Anomaly
Started December 4, 2007:
Entered “quiet period” two-weeks later (12/18/07)
Occasional packet errors are still observed at pre-anomaly levels
No interruption to spacecraft or instrument operations
ESMO Anomaly Resolution Team Formed
NGST, AETD, FOT, MD
GSFC/AETD/NGST Anomaly Review Board Final Report
Most Likely Cause: Single Event Functional Interrupt (SEFI)
Continue to operate as is unless anomaly returns
FOT prepared to perform FMU/SSR Reset Procedures and/or C&DH Swap Procedures if necessary
No impact to operations or 6-year life expectancy
Aura Mission Operations Status

25. Updated Lifetime Estimate (September 2008)
Long-term orbit simulations were run for Aqua and Aura through 2017
Used mean nominal Schatten solar flux predictions
Estimated the frequency of drag make-up maneuvers to maintain Aqua’s WRS-2 ground track requirements
Estimated the required number of annual inclination maneuvers for Aqua and Aura to satisfy the OMI beta angle request and maintain Aqua’s mean local time (MLT) requirement
Did not include potential debris avoidance maneuvers
Lifetime predictions for Aqua and Aura show that both spacecraft will have sufficient fuel to maintain their current orbits within the Afternoon Constellation through 2016 and possibly well beyond
Further analyses will be performed by ESMO FD Team
Aura Mission Operations Status

26. Debris Assessment Software
The Debris Assessment Software (DAS) was created by the Orbital Debris Office in Johnson Space Center and is the Agency standard for end of mission life analyses and lifetime estimations
DAS requires several inputs from a user describing a spacecraft’s mission:
The operational orbit parameters
The mission launch date
Length of a mission’s lifetime
In turn, DAS outputs:
Whether this mission is compliant with NASA requirements for limiting orbital debris
A recommended apogee and perigee that will allow the spacecraft to reenter within a specific period and satisfy NASA requirements
Aqua and Aura will have enough fuel onboard to safely exit the constellation and deorbit to the DAS recommended apogees and perigees
Aura Mission Operations Status

27. Aura DAS Lifetime Estimate (September 2008)
Aura Mission Operations Status

28. Schatten & DAS 2.0.1 Solar Flux Predictions – Nominal Timing
Aura Mission Operations Status

29. Data Capture

30. Aura Mission Operations Status
Data Capture
SSR Data Capture to 09/30/2008: %*
SSR Anomaly
EDOS Ops Error
Norway Comm Outages
Aura Mission Operations Status