SPACEFLIGHTSAFETYHANDBOOKFORSATELLITEOPERATORS
VERSION 1.3 JANUARY 2017
JSpOCProcessesforSatelliteConjunctionAssessment&CollisionAvoidance
JFCCSPACE,JointSpaceOperationsCenterVandenbergAFB,California,USATel+1‐805‐605‐3533www.space‐track.org
TABLE OF CONTENTS
Contents
RevisionHistory _________________________________________________________________________________________ 1
SpaceflightSafetyProcess_______________________________________________________________________________ 2
ConjunctionAssessment(CA)____________________________________________________________________________________2
CollisionAvoidance(COLA)______________________________________________________________________________________3
BasicEmergencyCAandCOLAServices ________________________________________________________________________3
AdvancedCAandCOLAServices_________________________________________________________________________________4
ScreeningSchedule _______________________________________________________________________________________________4
ScreeningVolumes________________________________________________________________________________________________5
ReportingCriteria_________________________________________________________________________________________________6
Notifications_______________________________________________________________________________________________________7
BasicEmergencyCANotifications_______________________________________________________________________________7
AdvancedCANotifications_______________________________________________________________________________________8
LaunchCA _________________________________________________________________________________________________________8
EarlyOrbitCA_____________________________________________________________________________________________________9
End‐of‐Life/DisposalSupport__________________________________________________________________________________10
DeorbitSupport_________________________________________________________________________________________________10
Tasking___________________________________________________________________________________________________________10
EphemerisFormats_____________________________________________________________________________________11
Overview_________________________________________________________________________________________________________11
NASAEphemerisFormat_______________________________________________________________________________________12
UTCEphemerisFormat_________________________________________________________________________________________13
GenericOn‐OrbitEphemerisFormat__________________________________________________________________________14
ModifiedITCEphemerisFormat_______________________________________________________________________________15
OrbitalEphemerisMessage(OEM)Format___________________________________________________________________16
HowtoNameEphemerisFiles_________________________________________________________________________19
Overview_________________________________________________________________________________________________________19
FileNameExamples ____________________________________________________________________________________________20
HowtoSubmitEphemerisFiles_______________________________________________________________________21
TABLE OF CONTENTS
Overview_________________________________________________________________________________________________________21
SubmittingEphmerisThroughSpace‐Track.org______________________________________________________________22
ManualUploadofEphmerisFiles______________________________________________________________________________22
APIUploadofEphemerisFiles_________________________________________________________________________________23
Email_____________________________________________________________________________________________________________23
GuidanceforHigh‐InterestEvents_____________________________________________________________________________23
ManeuverNotificationFormat_________________________________________________________________________24
Overview_________________________________________________________________________________________________________24
Format___________________________________________________________________________________________________________24
HowtoNameManeuverNotifications ________________________________________________________________29
FileNames_______________________________________________________________________________________________________29
FileVerification__________________________________________________________________________________________________29
HowtoSubmitManeuverNotifications_______________________________________________________________30
Overview_________________________________________________________________________________________________________30
SubmittingManeuverNotificationsThroughSpace‐Track.org ______________________________________________31
ManualUploadofManeuverNotifications____________________________________________________________________31
APIUploadofManeuverNotifications_________________________________________________________________________32
UpdatingManeuverNotifications______________________________________________________________________________32
Email_____________________________________________________________________________________________________________32
ContactUs_______________________________________________________________________________________________33
JSpOCSpaceflightSafetyCrew_________________________________________________________________________________33
JSpOCSSASharingTeam________________________________________________________________________________________33
Space‐Track.orgAdministrationTeam_________________________________________________________________________33
TABLE OF CONTENTS
REVISION HISTORY
Page1
RevisionHistory
Version Description of Changes Date
1.1 1.CorrectedNORAD_CAT_IDinManeuverNotificationformat,pg.252.AdditionofcontactinformationforSpace‐Track.org,pg.32
12Aug16
1.2 1.Definitionsofellipsoidandcovariancescreenings,pg.5‐6 27Aug161.3 1.Screeningschedule,pg.4
2.CorrectiontoBasicReportingCriteriaforLEOCDMs,pg.63.AddeddecimalnotationrequirementtoOEM,pg.184.Added“USER_DEFINED_MAN_ID”tomaneuvernotification,pg.275.Addedadditionalvaluesto“USER_DEFINED_MAN_PURPOSE,”pg.286.Changed“SOLVED”to“DETERMINED”for“USER_DEFINED_MAN_STATUS,”pg.287.Under“HowtoNameManeuverNotifications”updated“FileNames”andadded“FileVerification,”pg.298.Updated“SubmittingManeuverNotifications”toexplainthateachorganizationhastheirownmaneuverfolder,pg.319.Added“UpdatingManeuverNotifications,”pg.31
3Jan17
SPACEFLIGHT SAFETY PROCESS
Page2
SpaceflightSafetyProcess
CONJUNCTION ASSESSMENT (CA)
TheJSpOC’sConjunctionAssessment(CA)processidentifiescloseapproachesbetweenactivesatellitesandothercatalogedspaceobjects.ItbeginswithsatelliteobservationsfromtheU.S.SpaceSurveillanceNetwork(SSN),whichincludesavarietyofsensorsthroughouttheworldthatdetect,track,catalogandidentifyobjectsorbitingEarth.SSNobservationsareinputintotheJSpOC’smodelimplementing“SpecialPerturbations”(SP)orbitpropagationtheory.Orbitdetermination(OD)isperformedautomaticallymultipletimesperdaytodeterminethepositionandvelocityofeachobject,whichisthenupdatedintheJSpOC’sHighAccuracyCatalog(HAC).TheJSpOCSpaceflightSafetyTeamusestheHACtoscreentheorbitaltrajectoriesofallactivesatellitesagainsttherestofthecatalog,whichincludesotheractivesatellites.
Eachactivesatellitescreenedisreferredtoasaprimaryobject,andalloftheotherobjectsintheHACarereferredtoassecondaryobjects.TheJSpOCperformstwotypesofscreenings:
1. HACScreenings:SPcatalogdataforactivesatellitesscreenedagainstSPcatalogdataforallcatalogedspaceobjects
2. EphemerisScreenings:Ephemerisprovidedbythesatelliteowner/operator(O/O)screenedagainsttheSPcatalogdataforallcatalogedspaceobjects
TheJSpOCperformsscreeningsforeveryactivesatelliteandO/Oephemerisaminimumofonceevery24hoursinaccordancewiththeprocessinthefollowingdiagram:
Figure1:ConjunctionAssessmentScreeningProcess
SPACEFLIGHT SAFETY PROCESS
Page3
ThescreeningprocessstartswiththeupdateoforbitalinformationfortheentirecatalogbasedondatafromtheSSNsensorsandupdatedDynamicCalibrationAtmosphere(DCA)coefficients.Theseupdatestakeplaceevery8‐hours(referenceTable1:ScreeningSchedule).Usingthisdata,theJSpOCperformsaninitialscreeningofallactivesatellitesagainsttherestofthecatalogtoidentifyconjunctioncandidateswithinscreeningcriteria.ThesecandidatesarereevaluatedbytheJSpOC’sOrbitalSafetyAnalysts(OSAs)toensurethatallofthemostcurrentobservationsareincorporatedintotheOD.TheJSpOCthenconductsarefinementscreeningtoupdatetheconjunctionestimatesofallofthecandidatesidentifiedintheinitialscreening.Iftheparametersoftheconjunctionfallwithincriteriathatidentifiesacloseapproach,theJSpOCwillnotifytheO/Oofthesatellite(s)inaccordancewiththecriteriaandmethodslistedinReportingCriteria.BasedonthequalityoftheOD,theJSpOCmayalsoincreasesensortaskingontheprimaryorsecondaryobjects.
COLLISION AVOIDANCE (COLA)
Collisionavoidance(COLA)istheprocessofplanningandpossiblyexecutingamaneuverinresponsetoacloseapproachidentifiedduringtheCAprocess.BasedoninformationreceivedintheCAnotifications,theO/Odecideswhetherornottoperformcollisionavoidancebymaneuveringtheirsatellite.IftheydonotperformCOLA,theJSpOCwillcontinuetomonitortheconjunctionandprovideupdatesbasedondatafromtheSSNuntilthetimeofclosestapproach(TCA)haspassed.IftheO/OdecidestoperformCOLA,theymaysendtheJSpOCtheirpredictiveephemerisdata(inthecorrectformatandcoordinatesystem)whichtheJSpOCwillthenscreenagainsttheHACandprovidenotificationswithinreportingcriteriatotheO/Osothattheymaydecidehowtoproceed.ThisexchangeofdatamaycontinueuntiltheTCA,afterwhichtheJSpOCwillresumeroutinescreeningoftheactivesatelliteinaccordancewiththescreeningschedule.
BASIC EMERGENCY CA AND COLA SERVICES
TheJSpOCperformsCAandprovidesCOLAsupportforallsatelliteoperatorsasanemergencyservicetoensurespaceflightsafety.Alloperatorsareeligibleforthisbasicservice,whichincludes:
1. HACscreeningsusingbasicscreeningcriteria2. Operationalephemerisscreeningsusingregime‐basedscreeningcriteria3. EphemerisscreeningsforCOLA
3.1 Ephemerisversussecondaryobject,or3.2 Ephemerisversusfullcatalog
4. HAC‘1versus1’requests:screeningoneprimaryobjectagainstonesecondaryusingHACdata5. Closeapproachnotifications(CANs)byemailforeventsthatmeetemergencyreportablecriteria6. ConjunctionDataMessages(CDMs)onSpace‐Track.orgforeventsthatmeetemergencyreportable
criteria
SPACEFLIGHT SAFETY PROCESS
Page4
ADVANCED CA AND COLA SERVICES
O/OswhohavesignedaSpaceSituationalAwareness(SSA)SharingAgreementwithUSSTRATCOMmayrequestAdvancedCAandCOLAthroughtheOrbitalDataRequest(ODR)process.(Visithttps://www.space‐track.org/documentation#/odrformoreinformation.)AdvancedCAandCOLAsupportincludes:
1. HACscreeningsusingadvancedscreeningcriteria2. Operationalephemerisscreeningsusingregime‐basedscreeningcriteria3. EphemerisscreeningsforCOLA
3.1 Ephemerisversussecondaryobject,or3.2 Ephemerisversusfullcatalog
4. HAC‘1versus1’requests:screeningoneprimaryobjectagainstonesecondaryusingHACdata5. Closeapproachnotifications(CANs)byemailforeventsthatmeetemergencyreportablecriteria6. CDMsonSpace‐Track.orgforalleventswithinadvancedcriteria
SCREENING SCHEDULE
ThefilenamedictateshowtheJSpOCwilltreatephemerisfiles.IftheO/Odesignatesitas“Special”theJSpOCwilltreatitashigh‐interestandscreenitassoonaspossible.Ifitisdesignatedas“Operational”theJSpOCwillscreenitaccordingtothescheduleinTable1:ScreeningSchedule.ResultsforSpecialephemerisareprovidedwithin1‐4hoursofreceivingtheephemeris,andOperationalresultsareprovidedwithin4‐8hoursofthescheduledscreeningtimes.
Table 1: Screening Schedule
1430–2230UTCNearEarthHACNearEarthEphemeris(includesallephemerissubmittedbetween0630–1430UTC)GEOHAC(forsatellitesfrom0to180longitude)2230–0630UTC:NearEarthHACNearEarthEphemeris(includesallephemerissubmittedbetween1430–2230UTC)*HEO/MEOHACDeepSpaceEphemeris(includesallephemerissubmittedbetween0630–2230UTC)*0630–1430UTC:NearEarthHACNearEarthEphemeris(includesallephemerissubmittedbetween2230–0630UTC)*GEOHAC(forsatellitesfrom180to359.99longitude)DeepSpaceEphemeris(includesallephemerissubmittedbetween2230‐0630UTC)*
SPACEFLIGHT SAFETY PROCESS
Page5
SCREENING VOLUMES
ThefollowingtablesdefinewhatscreeningvolumesanddurationstheJSpOCusesforbasicCA,advancedCA,andephemerisscreenings.TheJSpOCconductstwotypesofscreenings:ellipsoidandcovariance.Bothscreeningsusecovariance‐based“uncertaintyvolumes”aroundthesatellitesandthephysicalsizeofthesatellitesthemselves(referredtoas“exclusionvolumes”).Thesamebasicmathematicalapproachisusedforbothellipsoidandcovarianceoptions,althoughprobabilityofcollision(Pc)isonlycomputedforthecovarianceoption.Fortheellipsoidscreeningoption,theuncertaintyvolumeisstaticthroughoutthescreeningprocess,whereascovariancescreeningsemployajointuncertaintyvolumethatisbasedontime‐varyingcovariancevaluesfortheprimaryandsecondaryobjectsatthetimeofclosestapproach.PleasevisitSpace‐Track.orgformoreinformationonHowtheJSpOCCalculatesProbabilityofCollision.
Table 2: Basic Screening Volumes
Screening OrbitRegimeDefinition Propagation Radial In‐Track Cross‐Track
GEOBasicEllipsoid
1300min<Period<1800minEccentricity<0.25&Inclination<35º 10days 10km 10km 10km
HEOBasicEllipsoid
Perigee<2000km&Eccentricity>0.25 10days 10km 10km 10km
MEOBasicEllipsoid
600min<Period<800minEccentricity<0.25 10days 10km 10km 10km
LEOBasicCovariance
Perigee≤2000kmEccentricity<0.25
7days 1km 1km 1km
Table 3: Advanced Screening Volumes
Screening OrbitRegimeDefinition Propagation Radial In‐Track Cross‐Track
GEOAdvancedEllipsoid
1300min<Period<1800minEccentricity<0.25&Inclination<35º 10days 20km 20km 20km
HEOAdvancedEllipsoid
Perigee<2000km&Eccentricity>0.25
10days 20km 20km 20km
MEOAdvancedEllipsoid
600min<Period<800minEccentricity<0.25
10days 20km 20km 20km
LEO4AdvancedCovariance
1200km<Perigee≤2000kmEccentricity<0.25
7days 0.5km 2km 2km
LEO3AdvancedCovariance
750km<Perigee≤1200kmEccentricity<0.25
7days 0.5km 12km 10km
LEO2AdvancedCovariance
500km<Perigee≤750kmEccentricity<0.25
7days 0.5km 28km 29km
LEO1AdvancedCovariance
Perigee≤500kmEccentricity<0.25
7days 2km 44km 51km
SPACEFLIGHT SAFETY PROCESS
Page6
Table 4: Ephemeris Screening Volumes
Screening OrbitRegimeDefinition Propagation Radial In‐Track Cross‐Track
DeepSpaceEllipsoid
Period>225min 10days 20km 20km 20km
NearEarthCovariance
Period<225min 7days 2km 25km 25km
REPORTING CRITERIA
ThefollowingtablesdefinethereportingcriteriausedforbasicandadvancedCAandCOLA.ThesetablesapplytobothHACandephemerisscreenings.
Table 5: Basic Reporting Criteria
ReportingCriteria:
Space‐TrackCriteria EmergencyCriteriaEmergency
PhoneCallCriteria
NotificationMethod: CDM CDM&CANemail CDM,CANemail&phonecall
GEOTCA≤10daysandOverallmiss≤10km
TCA≤3daysandOverallmiss≤5km
TCA≤3daysandOverallmiss≤500m
HEOReportingbasedontheregimeofthesecondaryobjectinthepredictedconjunctionatTCAusingmissdistancecriteriaonly.
MEOTCA≤10daysandOverallmiss≤10km
TCA≤3daysandOverallmiss≤5km
TCA≤3daysandOverallmiss≤500m
LEOTCA≤3daysandOverallmiss≤1kmandProbabilityofCollision≥e^‐4
TCA≤3daysandOverallmiss≤1kmandProbabilityofCollision≥e^‐4
TCA≤3daysandOverallmiss≤1kmandProbabilityofCollision≥e^‐2
Table 6: Advanced Reporting Criteria
ReportingCriteria:
Space‐TrackCriteria EmergencyCriteriaEmergency
PhoneCallCriteria
NotificationMethod: CDM CDM&CANemail CDM,CANemail&phonecall
GEOAllresultswithAdvancedScreeningVolumes
TCA≤3daysandOverallmiss≤5km
TCA≤3daysandOverallmiss≤500m
HEOAllresultswithAdvancedScreeningVolumes
ReportingbasedontheregimeofthesecondaryobjectinthepredictedconjunctionatTCA
MEOAllresultswithAdvancedScreeningVolumes
TCA≤3daysandOverallmiss≤5km
TCA≤3daysandOverallmiss≤500m
LEOAllresultswithAdvancedScreeningVolumes
TCA≤3daysandOverallmiss≤1kmandProbabilityofCollision≥e^‐4
TCA≤3daysandOverallmiss≤1kmandProbabilityofCollision≥e^‐2
SPACEFLIGHT SAFETY PROCESS
Page7
NOTIFICATIONS
O/Oswillreceiveavarietyofemailnotificationsdependingonthescreeningperformedandresultsproduced.AlloftheseemailsaregeneratedandtransmittedbySpace‐Track,basedonfilesthattheJSpOCSpaceflightSafetyCrewhasuploadedtothewebsite.Themessagesare:
• CloseApproachNotification(CAN)email:sentforeverypredictionthatmeetsemergencyreportablecriteria.Includesprimary,secondary,missdistances,TCA,andfornearearthevents,ProbabilityofCollision(Pc),OnlysenttoemailaddressesthattheO/OhasdesignatedtoreceiveCANs.(ControlledbytheJSpOC–[email protected])
• CDMemail:notifiesO/OsthatnewCDMsareavailableonSpace‐Trackfortheirorganization.Alluserswith‘CDMNotification’permissionsreceivethisemail.(Controlledbyeachorganization’sPrimaryRepresentativeortheJSpOC.)
• Negativeresultsemail:Confirmsthataspecificephemerisfilehasbeenscreenedandstatesthattherearenoresultswithintheephemerisscreeningvolume.
• Expandedresultsemail:Confirmsthataspecificephemerisfilehasbeenscreened,andthatthereareresultsthatarewithintheephemerisscreeningvolumes,butnotwithinemergencyreportablecriteria.
Thereareslightdifferencesbetweenthenotificationssentforbasicandadvancedservices.ThefollowingchartsshowwhichmessagesshouldbeexpectedfordifferentscenarioswithintheCAandCOLAprocess.
BASIC EMERGENCY CA NOTIFICATIONS
Figure2:BasicEmergencyCANotifications
SPACEFLIGHT SAFETY PROCESS
Page8
ADVANCED CA NOTIFICATIONS
Figure3:AdvancedCANotifications
LAUNCH CA
TheJSpOCalsoprovidesCAandCOLAservicesforspecificphasesofasatellite’slifetime.LaunchCAidentifiespotentialconjunctionsthatmayresultinacollisionbetweenlaunchingobjectsandon‐orbitobjects.UsingO/O‐providedinformation,theJSpOCscreensthelaunchvehicleagainstthespacecatalogandidentifiesperiodsduringthelaunchwindowwhichmayputtherocketandpayloadatincreasedriskforcollision.Screeningbeginsatanaltitudeof150kmorgreaterandcontinuesuntileitherlocationuncertaintymakesperformingthescreeningnolongerfeasibleoruntiltherocketbody/sub‐orbitalcomponentsdescendto150kmorless.ToreceiveLaunchCAtheO/Oshould:
SubmitanODR SubmitaForm22,whichdetailstheparametersofthescreeningrequests
Providelaunchtrajectoriesinthecorrectformat
SPACEFLIGHT SAFETY PROCESS
Page9
EARLY ORBIT CA
EarlyOrbitCAincludesthescreeningofO/O‐providedephemerisagainstthecatalogtofacilitatethesafemaneuveringofanewlylaunchedobjectintoitsfinalorbit.TheJSpOCwillscreentheephemerisusingearlyorbitscreeningvolumesandreportallresultsinaccordancewithadvancedreportingcriteria.TheO/Omayprovidemorethanoneephemerisfileforeachmaneuvertoallowanalysisofmultiplescenarios.ToreceiveearlyorbitCAsupporttheO/Oshould:
Pre‐launch:o SubmitanODRrequestingearlyorbitCA,specifyingthepreferredscreeningvolumeo RegisterforauseraccountonSpace‐Track.orgo Providetheearlyorbitmaneuverplano Sendinpre‐launchephemerisfortesting,ifdesired
Post‐launch:o Provideephemerisinthecorrectformatandusingthecorrectfilenameformatforeach
screeningo Provideanupdatedmaneuverplan,ifneeded
Table 3: Early Orbit Screening Volumes
Screening OrbitRegimeDefinition Propagation Radial In‐Track Cross‐Track
GEOAdvanced
1300min<Period<1800minEccentricity<0.25&Inclination<35º
10days 12km 364km 30km
HEOAdvanced
Perigee<2000km&Eccentricity>0.25
10days 40km 77km 107km
MEOAdvanced
600min<Period<800minEccentricity<0.25 10days 2.2km 17km 21km
LEO4Advanced
1200km<Perigee≤2000kmEccentricity<0.25
7days 0.5km 2km 2km
LEO3Advanced
750km<Perigee≤1200kmEccentricity<0.25
7days 0.5km 12km 10km
LEO2Advanced
500km<Perigee≤750kmEccentricity<0.25
7days 0.5km 28km 29km
LEO1Advanced
Perigee≤500kmEccentricity<0.25
7days 2km 44km 51km
SPACEFLIGHT SAFETY PROCESS
Page10
END-OF-LIFE/DISPOSAL SUPPORT
IfanO/Odecidestomoveasatellitetoaless‐populatedorbitattheendofitslifetime,theJSpOCwillassisttheO/Obyscreeningmaneuverephemerisandprovidingresults.AllO/O‐providedephemeriswillbescreenedusingstandardephemerisscreeningvolumes,andresultswillbeprovidedinaccordancewithbasisoradvancedreportingcriteria.Toreceiveend‐of‐life/disposalCAtheO/Oshould:
SubmitanODRifallresultswithinadvancedreportingcriteriaaredesired(noODRisrequiredforbasicreportingcriteria)
Providethemaneuverplan Provideephemerisinthecorrectformatandusingthecorrectfilenameformatforeachscreening
DEORBIT SUPPORT
Adeorbitisthecontrolledreentryofasatelliteintotheearth’satmosphere.IfanO/Odecidestodeorbitasatelliteorrocketstagethroughaseriesofmaneuvers,theJSpOCcanprovideCAscreenings,aswellascoordinatewithNASAtoensurethedeorbitingspacecraftsafelydescendsthroughtheInternationalSpaceStation’s(ISS)orbit.Afterthespacecraftcompletestheirmaneuvers,theJSpOCcanconfirmfinalreentry.Toreceivethisservice,theO/Oshould:
SubmitanODRifallresultswithinadvancedreportingcriteriaaredesired(noODRisrequiredforbasicreportingcriteria)
Providethemaneuverplan Provideephemerisinthecorrectformatandusingthecorrectfilenameformatforeachscreening
TASKING
Incertainsituations,moreobservationsonanobjectwillimprovethequalityoftheconjunctionprediction.Tocollectmoreobservations,theJSpOCcanincreasethetaskingpriorityandrevisitfrequencyassignedtosensors.TheJSpOChasimbeddedthisintheroutinescreeningcycleasseeninFigure1.Ifanobjectmeetsanyofthefollowingcriteria,itstaskingwillbeautomaticallyincreased:
Nottrackedwithin72hours,or Lessthan20observationsincurrentDC,or TwoorlesssensorscontributingtocurrentDC,or
Atleastonecomponentofcovarianceover100,000m2
Foremergencyreportableevents,theO/OmaycontacttheJSpOCtoconfirmthatbothobjectsintheconjunctionaretaskedappropriatelybyemailingjspocspacecorrespondence@us.af.mil.
EPHEMERIS FORMATS
Page11
EphemerisFormats
OVERVIEW
Satelliteoperatorsmayprovideephemerisinvariousformats,whichwillbeconvertedintoformatsthatcanbeprocessedbytheJSpOC’sASW(AstrodynamicsSupportWorkstation)/SuperComputationofMissBetweenOrbits(COMBO)software.Operatorsmayelecttoincludecovariancedatainordertoaccommodateprobabilityofcollisioncalculations.
Allephemerisformatsmustbeinthemeanequator/meanequinox(MEME)J2000.0framewithpositionalvalues(x,y,z)giveninkilometerunitsandvelocityvalues(dX,dY,dZ)giveninunitsofkilometers/second.Ifcovariancevaluesareprovided,theymustbeintheUVWorbitalreferenceframe.
Allephemerisformatsmayincludeinformationalheaderlinespriortothedatalineswhichprovidedate,time,andstatevector(positionandvelocity)values.Eachformatdiffersinthenumberandcontentofheaderlines,formatofthedateandtimevalues,anddifferentprecision(numberofdecimalplaces)forthestatevectorcomponents.
TheJSpOC’sconversionutilitysoftwareconvertsallephemerisformatstotrueequator/meanequinox(TEME)ofDateforepochJ2000.ThemostrecenttimeconstantsdatafilewithintheJSpOCmissionsystemcorrectsforleapseconds.
TheNASAandUTCformatsincludepositionandvelocityonly.TheJSpOCacceptsthreeformatswithcovariance:
• GeneralOn‐Orbit(GOO)mayinclude3x3(6lowertriangularmatrix)positioncovariancedatavalues,
• ModifiedITCmayinclude6x6(21lowertriangularmatrix)positionandvelocitycovariancedatavalues
• OrbitalEphemerisMessage(OEM)format,bothwithandwithoutcovariancedata,whichincludesacapabilityforprocessing6x6(21lowertriangularmatrix)positionandvelocitycovariancedatavalues.VisittheConsultativeCommitteeforSpaceDataSystems(CCSDS)websiteformoreinformationontheOEM:http://public.ccsds.org/publications/archive/502x0b2c1.pdf
EPHEMERIS FORMATS
Page12
NASA EPHEMERIS FORMAT
TheNASAephemerisdatafileformatcontainsnodescriptiveheaderlinesprecedingtheephemerisdata.EachdatalinecontainsadateformattedasYYDOY(onlytwodigitsofyearandDayofYear(DOY)inplaceofmonthandday),atimestampformattedasHHMMSS.SSS,andthestatevectorposition(x,y,z)andvelocity(dx,dy,dy)values.
Figure4:NASAEphemerisFormatExample
TheJSpOC’sconversionutilityseparatestheentriesoneachephemerisdatalinewhereveroneormorespace(i.e.““)charactersarefound.Foreachdatalinethisprocessingresultsinacombineddate/timefield(i.e.“yyDOYhhmmss.sss”)andeachstatevectorcomponent(i.e.position(x,y,z)andvelocity(i.e.dx,dy,dz))value.Thisephemerisformatdoesnotincludecovariancevalues.
EPHEMERIS FORMATS
Page13
UTC EPHEMERIS FORMAT
TheUTCephemerisdatafileformatcontains21descriptiveandheaderlinesprecedingtheephemerisdata.EachdatalinecontainsadateformattedasYYYY/MM/DD,atimestampformattedasHH:MM:SS.SSS,andthestatevectorposition(x,y,z)andvelocity(dx,dy,dy)values.
Figure5:UTCEphemerisFormatExample
Theconversionutilityignoresthe21headeranddescriptivelinesandseparatestheentriesoneachephemerisdatalinewhereveroneormorespace(i.e.““)charactersarefound.Foreachdatalinethisprocessingresultsinadatefield(i.e.“yyyy/mm/dd”),atimefield(i.e.“hh:mm:ss.sss”)andeachstatevectorcomponent(i.e.position(x,y,z)andvelocity(i.e.dx,dy,dz))value.
Thedatefieldisseparatedintomonth,day,andyearvalueswhereveraforwardslash(i.e.“/”)characterisfound;andthetimefieldisseparatedintohour,minute,andsecondvalueswhereveracolon(i.e.“:”)characterisfound.TheDayofYear(DOY)valueiscalculatedfromthemonthandday,takingintoaccountanyadjustmentneededforaleapyear.
Thisephemerisformatdoesnotincludecovariancevalues.
EPHEMERIS FORMATS
Page14
GENERIC ON-ORBIT EPHEMERIS FORMAT
TheGenericOn‐Orbitephemerisdatafileformatistheonlyformatthatisrequiredtocontainpositioncovariancedatainadditiontoephemerisdata.Itcontainsfourdescriptiveandheaderlines,wherethefourthindicatestheorbitalreferenceframeofthecovariancedata.Thedatasectionconsistsof,foreachephemerisdatapoint,onelinewhichcontainstheepochdateandtimeandstatevector,followedbyonelineholdingthesixvaluesofthe3x3lowertriangularpositioncovariancematrix.
Figure6:GenericOn‐OrbitDataExample
Theconversionutilitymakesarudimentarycheckthatthecorrectnumberofdatalinesarepresent.Thenumberofheaderlinesissubtractedfromthenumberoflinesintheephemerisdatafile;iftheresultisnotdivisibleby2(astatevectorlineplusacovariancedataline)awarningmessageisoutput,buttheconversioncontinues.
Theconversionutilityignorestheheaderanddescriptivelinesexceptforthecovarianceorbitframereferencevalue.Itthenreadsthedatalinesingroupsoftwoandseparatestheentriesoneachdatalinewhereveroneormorespace(i.e.““)charactersarefound.Foreachgroupoftwodatalinesthisprocessingresultsinadate/timefield(i.e.“yyyDOYhhmmss.sss”),eachstatevectorcomponent(i.e.position(x,y,z)andvelocity(i.e.dx,dy,dz))valueand6covariancevalues.
Thecombineddate/timefieldisseparatedintoyear,DayofYear,hour,minute,andsecondvalues.
EPHEMERIS FORMATS
Page15
MODIFIED ITC EPHEMERIS FORMAT
TheModifiedITCephemerisdatafileformatistheonlyformatthatisrequiredtocontainbothpositionalandvelocitycovariancedatainadditiontoephemerisdata.Itcontainsfourdescriptiveandheaderlines,wherethefourthindicatestheorbitalreferenceframeofthecovariancedata.Thedatasectionconsistsof,foreachephemerisdatapoint,onelinewhichcontainstheepochdateandtimeandstatevector,followedbythreelinesholdingthetwenty‐onevaluesofthe6x6lowertriangularpositionandvelocitycovariancematrix.
Figure7:ModifiedITCDataExample
Theconversionutilitymakesarudimentarycheckthatthecorrectnumberofdatalinesarepresent.Thenumberofheaderlinesissubtractedfromthenumberoflinesintheephemerisdatafile;iftheresultisnotdivisibleby2(astatevectorlineplusacovariancedataline)awarningmessageisoutput,buttheconversioncontinues.
Thepreprocessingscriptignorestheheaderanddescriptivelinesexceptforthecovarianceorbitframereferencevalue.Itthenreadsthedatalinesingroupsoffourandseparatestheentriesoneachdatalinewhereveroneormorespace(i.e.““)charactersarefound.Foreachgroupoffourdatalinesthisprocessingresultsinadate/timefield(i.e.“yyyDOYhhmmss.sss”),eachstatevectorcomponent(i.e.position(x,y,z)andvelocity(i.e.dx,dy,dz))valueand21covariancevalues.
Thecombineddate/timefieldisseparatedintoyear,DayofYear,hour,minute,andsecondvalues.
EPHEMERIS FORMATS
Page16
ORBITAL EPHEMERIS MESSAGE (OEM) FORMAT
TheOEMephemerisdatafileformatcontainsavariablenumberofoptionaldescriptivelinesinterspersedwithblocksofephemerisandoptionallycovariancedata.NotethatblocksofcovariancedatamaycontainmorethanonesetofcovariancedataseparatedbyEPOCHkeywords.
Foracompletediscussionofthisephemerisdataformatreferto:“OrbitEphemerisMessage(OEM)”,OrbitDataMessages,ConsultativeCommitteeforSpaceDataSystems(CCSDS),RecommendedStandardCCSDS502.0‐B‐2,BlueBook,November2009.
Figure8:OEM(withoutcovariance)Example
EPHEMERIS FORMATS
Page17
Figure9:OEM(withcovariance)Example
Theconversionutilityremovesalllinesthatareblankorcontainthekeywords(definedintheformatdocument)CCSDS_OEM_VERS,CENTER_NAME,COMMENT,COV_REF_FRAME,CREATION_DATE,INTERPOLATION,INTERPOLATION_DEGREE,META_START,META_STOP,OBJECT_ID,OBJECT_NAME,ORIGINATOR,REF_FRAME,START_TIME,STOP_TIME,TIME_SYSTEM,USEABLE_START_TIME,orUSEABLE_STOP_TIME.Thisreducesthedatafiletolinescontainingblocksofephemerisdataandoptionalblocksofcovariancedata.ThecovariancedatablocksaredelimitedbylinescontainingthekeywordsCOVARIANCE_STARTandCOVARIANCE_STOP.Therecanbemorethanonesectionofcovariancedata
EPHEMERIS FORMATS
Page18
withinablock,eachdelimitedbyanEPOCHline.Thedate/timevaluesoftheoptionalcovariancedataontheEPOCHlinesarenotguaranteedbytheformatstandardtomatchanyephemerisdatadate/timevalues.
Thevaluesoneachephemerisdatalineareseparatedoutwhereveroneormorespace(i.e.““)charactersarefound.
Foreachephemerisdataline,furtherprocessingresultsindate/timefields(i.e.“yyyy‐mm‐dd”and“hh:mm:ss.sss”)andeachstatevectorcomponent(i.e.position(x,y,z)andvelocity(i.e.dx,dy,dz))value.StatevectorcomponentsmustbeindecimalnotationasseeninFigure9.Foreachoptionalblockofcovariancedata,processingresultsindate/timefields(i.e.“yyyy‐mm‐dd”and“hh:mm:ss.sss”)andthe21covariancevalues.
Thedatefieldisseparatedintomonth,day,andyear,valueswhereveradash(i.e.“‐”)characterisfound;andthetimefieldisseparatedintohour,minute,andsecondvalueswhereveracolon(i.e.“:”)characterisfound.TheDayofYear(DOY)valueiscalculatedfromthemonthandday,takingintoaccountanyadjustmentneededforaleapyear.
Theconversionutilitythenmatchesbydateandtimethecovariancedata,ifitexists,toalineofephemerisdata.Ifthedateandtimeexactlymatches,thecovariancedataisappendedtotheephemerisstatevectorforthatdateandtime.Thecovariancedataisdiscardedifthedateandtimedonotmatchforasectionofcovariancedata.Ephemerisdatalinesthatdonothavedateandtimematchesofcovariancedatawillhavetwenty‐onezero(i.e.“0.0”)valuesfollowingthestatevector.
HOW TO NAME EPHEMERIS FILES
Page19
HowtoNameEphemerisFiles
OVERVIEW
TheJSpOCrequiresthatsatelliteoperatorsnametheirfilesfollowingaspecificformat,whichdictateshowtheephemerisfilewillbeprocessed.IftheO/OsubmitstheirfilesthroughthewebsiteSpace‐Track.org,Space‐Trackwillverifythefileisnamedcorrectly,andreturnerrormessagesifitisnot.Thefilenameformatis:
<DataType>_<Catalog#>_<CommonName>_<DayTimeGroup>_<Operational/Special>_<MetaData>_<classification>.<FileExtension>
Table 7: Ephemeris File Name Convention
Data Field Description Normative Value (N) or Example (E)
Obligatory
DataType Thetypeofdatabeingprovided. (N)MEME(unlessotherwisedirectedbytheJSpOC)Thisentrymustbeinuppercaseletters
Yes
Catalog# The5‐digitdesignatorfortheobjectasdefinedinUSSTRATCOM’ssatellitecataloghttps://www.space‐track.org/#/catalog
Iftheobjectisnotcataloged,use:
UCN##fornear‐earthobjects
UCD##fordeep‐spaceobjects
Substitute##with01,02,03etc.uptothetotalnumberoffilessubmitted
(E)25544
(E)00900
(E)UCN01
(E)UCD02
Yes
CommonName Thespacecraftnamefortheobject.RecommendusingthecommonnamelistedinUSSTRATCOM’ssatellitecataloghttps://www.space‐track.org/#/catalog
Iftheobjectisnotcataloged,usethecommonnamedesignatedbythesatelliteoperator
(E)ISS(ZARYA)(E)CALSHERE1
Yes
DayTimeGroup Three‐digitdayofyearandHH:MMinUTC,whereHHisthehourinthe24‐hoursystem
(E)3001224=Oct25,2015at12:24pmUTC
Yes
Continuedonnextpage
HOW TO NAME EPHEMERIS FILES
Page20
Table 7: Ephemeris File Name Convention, cont.
Data Field Description Normative Value (N) or Example (E)
Obligatory
Operational/Special
An“Operational”filerepresentswherethesatelliteisplannedtogoandmayormaynotincludemaneuvers
Thesefilestypicallyincorporatenormalstation‐keeps,orrepresentafreefallorbit
Ifmaneuversareincluded,theJSpOCassumesthesewilldefinitelyoccur.Otherwise,thefilesshouldbesubmittedasSpecial.
A“Special”filerepresentswherethesatelliteisplannedtogoifaspecialmaneuverisexecuted
A“Special”fileisusedforplanningpurposesonly,unlessthemaneuverbecomesoperational,inwhichcaseitmustberesubmittedas“Operational”
All“Special”fileswillbetreatedashigh‐interest
*Multiplespecialfilesmaybesubmittedforthesamesatellite,butonlyoneoperationalfileatatimecanbesubmittedpersatellite*
(E)Operational
(E)Special
Yes
MetaData Additionalinformationprovidedatthediscretionofthesatelliteoperator.Oftenusedtoindicatemaneuverstatus,ormaneuveroptionplan.
(E)nomnvr
(E)stationkeepingmnvr
(E)mnvr01
(E)burn02
No
Classification Thesecurityclassificationofthedata.Onlyunclassifiedfileswillbeacceptedthroughwww.space‐track.org
(E)unclassified
(E)UNCLASSIFIED
(E)Unclassified
Yes
FileExtension Indicatesthetypeoffile (N).txt(unlessotherwisedirectedbytheJSpOC)
Yes
FILE NAME EXAMPLES
• MEME_25544_ISS_1651200_operational__unclassified.txt
• MEME_25544_ISS(ZARYA)_1651200_operational_nomnvr_UNCLASSIFIED.txt
• MEME_25544_ISS_1651200_special_mnvr01_Unclassified.txt
• MEME_25544_ISS_1651200_special_burn02_unclassified.txt
• MEME_UCN01_SPACESAT1_1651200_special_burn01_Unclassified.txt
HOW TO SUBMIT EPHEMERIS FILES
Page21
HowtoSubmitEphemerisFiles
OVERVIEW
Ephemerisfilesmaybesubmittedinthreeways:
1. ThroughthewebsiteSpace‐Track.org(preferred):
1.1 Manually,or1.2 UsingApplicationProgrammingInterface(API)
2. ByemailtotheJSpOCSpaceflightSafetyCrewatjspocspacecorrespondence@us.af.mil
Space‐Track.orgisthemostefficientandsecuremethodofsubmittingephemerisfilesonarecurringbasis.Tosetupaccess,contacttheJSpOC’[email protected]+1‐805‐606‐2675.TheSSASharingCellwillrequestthefollowinginformation:
1. ThetitleofyourCDMaccount(theaccountunderwhichyouaccessCDMsontheOperatorPanel)2. TheSpace‐Trackusernamesofthepersonnelwhowilluploadephemerisforyoursatellite
constellation
TheSSASharingCellwillcreateapermissions‐basedephemerisfolderforyourorganizationthatwillonlybeaccessedbytheJSpOCandthepersonnelyouauthorize.Youwillhaveupload,download,anddeletepermissionstothefolder,whichyouwillaccessthroughtheFilesPanel:
Figure10:FilesPanelonSpace‐Track.org
HOW TO SUBMIT EPHEMERIS FILES
Page22
SUBMITTING EPHMERIS THROUGH SPACE-TRACK.ORG
OnceyouhaveanephemerisfolderontheFilesPanel,youwillalsohaveaccesstothe‘Download’and‘Upload’tabs.Onthe‘Upload’tabyoucanuploadavarietyoffilestothefoldersyouhavepermissionsto.Allofthesefolderswilldisplayinthe‘Destination’dropdownmenu:
Figure11:FilesPanelUploadTab‐Ephemeris
MANUAL UPLOAD OF EPHMERIS FILES
1. LogintoSpace‐Track.org,clickon‘Files’atthetopofthepage,andthenclickonthe‘Upload’tab2. Click‘Browse’andselectyourephemerisfiles
2.1 Maximumnumberoffilesinasingleuploadis1002.2 Maximumtotalsizeperuploadis60MB2.3 Filesmustbenamedinaccordancewithguidelinesin‘HowtoNameEphemerisFiles’
3. Usingthe‘Destination’dropdownmenu,selectthe‘/Ephemeris/’folderforyourorganization4. Click‘Upload’touploadthefiles5. Afterasuccessfulupload,thefileswilldisplayin‘MyUploads(Last30Days)’Table6. TheJSpOCSpaceflightSafetyCrewwillreceiveanotificationthatyouhaveuploadednewephemeris
filesforscreening.However,iftheephemerisis‘Special’orinresponsetoahigh‐interestevent,pleasephoneoremailtheSpaceflightSafetyCrewtonotifythemthatyouneedanimmediateresponse:+1‐805‐605‐[email protected]
HOW TO SUBMIT EPHEMERIS FILES
Page23
API UPLOAD OF EPHEMERIS FILES
PleasevisitSpace‐Track.org’s‘HowTo’pageforthemostup‐to‐dateguidanceonAPIcapabilities:https://www.space‐track.org/documentation#/howto
Similartomanualuploads:
1. Filesmustbenamedinaccordancewithguidelinesin‘HowtoNameEphemerisFiles’2. Afterasuccessfulupload,thefileswilldisplayin‘MyUploads(Last30Days)’Table3. TheJSpOCSpaceflightSafetyCrewwillreceiveanotificationthatyouhaveuploadednewephemeris
filesforscreening.However,iftheephemerisis‘Special’orinresponsetoahigh‐interestevent,pleasephoneoremailtheSpaceflightSafetyCrewtonotifythemthatyouneedanimmediateresponse:+1‐805‐605‐[email protected]
Ifyourorganizationdoesn’thaveanephemerisfolderontheFilesPanel,youmaysendyourephemerisbyemailtotheJSpOCSpaceflightSafetyCrew.Please:
1. Namefilesinaccordancewithguidelinesin‘HowtoNameEphemerisFiles’2. Sendonly.txtfiles‐.zipfilescannotbeaccepted
GUIDANCE FOR HIGH-INTEREST EVENTS
Afteryousubmityourephemeris,pleasesendanemailorphonetheJSpOCSpaceflightSafetyCrew([email protected]+1‐805‐605‐3533)toprovidethefollowinginformationregardingthehigh‐interestrequest:
1. Theconjunctioneventthatyouarerespondingto(providesecondaryobject,CDMIDnumber,and/ortimeofclosestapproach)
2. Theobject(s)youneedyourephemerisscreenedagainst(forexample,oneobject,ashortlistofobjects,orthewholecatalog)
3. ReferenceyourapprovedOrbitalDataRequest,ifapplicable4. ConfirmationthatyoudoordonothaveanSSASharingAgreementwithUSSTRATCOM(Formore
informationonSSASharingAgreements,pleasevisithttps://www.space‐track.org/documentation#/odr)
MANEUVER NOTIFICATION FORMAT
Page24
ManeuverNotificationFormat
OVERVIEW
TheJSpOCrespectfullyrequeststhatsatelliteoperatorsnotifytheJSpOCofplanned,confirmed,andcancelledmaneuvers.ThisallowstheJSpOCtomaintainamoreaccuratecatalog,anticipatespaceflightsafetyrisks,andprovidemorerelevantconjunctionnotifications.TheJSpOChaschosentheOrbitalParameterMessage(OPM)asthemostappropriatemethodofexchangingmaneuverinformation.However,tomakeitapplicabletoJSpOCoperationsandreportingprocedures,theJSpOChasmademodificationstothemessage,whicharedetailedinthefollowingManeuverNotificationFormat.GuidelinesthataddtoordeviatefromthedirectionprovidedintheCCSDSOrbitDataMessageBlueBookareindicatedinredtext.ToaccesstheBlueBookvisit:https://public.ccsds.org/Pubs/502x0b2c1.pdf
FORMAT
TheOPMshallberepresentedasacombinationofthefollowing:(1)aheader,(2)metadata(dataaboutdata),(3)data,and(4)optionalcomments.Space‐TrackonlyacceptsKVN.
ThefollowingtablesspecifyforeachsectionoftheOPM:(1)thekeywordtobeused,(2)ashortdescriptionoftheitem,(3)examplesofallowedvaluesortheunitsofthetimewhenapplicable,and(4)whethertheitemisobligatoryoroptional.
Table 8: OPM Header
Keyword Description Example ObligatoryCCSDS_OPM_VERS Formatversionintheformof‘x.y’,
where‘y’isincrementedforcorrectionsandminorchanges,and‘x’isincrementedformajorchanges.
2.0 Yes
COMMENT ReferenceODMBlueBook6.7 Thisisacomment No
CREATION_DATE Filecreationdate/timeinUTC 2015‐07‐04T12:00:00 Yes
ORIGINATOR Creatingagencyoroperator.MustbethesametitleastheCDMaccountonSpace‐Track.org
CNES,JAXA,ESA,IRIDIUM
Yes
USER_DEFINED_RELEASABILITY Acceptablevalues:PUBLIC,PRIVATEPUBLIC:OperatoragreestosharefilewithallothersatelliteoperatorswhohaveaccesstoSpace‐Track’sOperatorPanelPRIVATE:OperatorsagreestosharefilewithJSpOConly
PUBLIC No.Ifnotprovided,willdefaulttoPRIVATE
USER_DEFINED_CLASSIFICATION Acceptablevalue:UNCLASSIFIEDTheJSpOCwillonlyacceptunclassifiedfiles.
UNCLASSIFIED Yes
MANEUVER NOTIFICATION FORMAT
Page25
Table 9: OPM Metadata
Keyword Description Example ObligatoryCOMMENT ReferenceOrbitalDataMessageBlueBook
6.7Thisisacomment No
OBJECT_NAME Spacecraftnameforwhichtheorbitstateormaneuverinformationisprovided.RecommendusingcommonnamesintheSatelliteCatalogonwww.space‐track.org
ISS(ZARYA) Yes
OBJECT_ID Objectidentifieroftheobjectforwhichtheorbitstateisprovided.UseinternationaldesignatoraspublishedonSpace‐Track.orgusingformatYYYY‐NNNP{PP},where:YYYY=Yearoflaunch.NNN=ThreedigitserialnumberoflaunchinyearYYYY(withleadingzeros).P{PP}=Atleastonecapitalletterfortheidentificationofthepartbroughtintospacebythelaunch.
1998‐067A Yes
USER_DEFINED_NORAD_CAT_ID
5‐digitsatellitecatalognumberassignedbyUSSTRATCOM.
25544 No
CENTER_NAME Originofreferenceframe Earth Yes
REF_FRAME NameofreferenceframeinwhichthestatevectorandoptionalKeplarianelementdataaregiven
EME2000ITRFICRFTODTDR
Yes,ifstatevectorincluded
REF_FRAME_EPOCH Epochofreferenceframe,ifnotintrinsictothedefinitionofthereferenceframe.
2001‐11‐06T11:17:33 No
TIME_SYSTEM Timesystemusedforstatevector,maneuver,andcovariancedata.MustbeUTC.
UTC Yes
Table 10: OPM DATA – State Vector Components in specified Coordinate System
Keyword Description Units ObligatoryCOMMENT ReferenceOrbitalDataMessageBlueBook6.7 N/A NoEPOCH EpochofstatevectorinUTC N/A NoX PositionvectorX‐component km NoY PositionvectorY‐component km NoZ PositionvectorZ‐component km NoX_DOT VelocityvectorX‐component km/s NoY_DOT VelocityvectorY‐component km/s NoZ_DOT VelocityvectorZ‐component km/s No
MANEUVER NOTIFICATION FORMAT
Page26
TABLE 11: OPM DATA – OSCULATING KEPLARIAN ELEMENTS IN SPECIFIED REFERENCE FRAME
Keyword Description Units ObligatoryCOMMENT ReferenceOrbitalDataMessageBlueBook6.7 n/a NoSEMI_MAJOR_AXIS Semi‐majoraxis km NoECCENTRICITY Eccentricity n/a NoINCLINATION Inclination deg NoRA_OF_ASC_NODE Rightascensionoftheascendingnode deg NoARG_OF_PERICENTER Argumentofpericenter deg NoMEAN_ANOMALY Meananomaly deg NoGM Gravitationalcoefficient(GravitationalConstantxCentral
Mass)km**3/s**2 No
Table 12: OPM DATA – Spacecraft Parameters
Keyword Description Units ObligatoryCOMMENT ReferenceOrbitalDataMessageBlueBook6.7 n/a NoMASS Spacecraftmass kg NoSOLAR_RAD_AREA SolarRadiationPressureArea(AR) m**2 NoSOLAR_RAD_COEFF SolarRadiationPressureCoefficient(CR) n/a NoDRAG_AREA DragArea(AD) m**2 NoDRAG_COEFF DragCoefficient(CD) n/a No
Table 13: OPM DATA – Position/Velocity Covariance Matrix
Keyword Description Units ObligatoryCOMMENT ReferenceOrbitalDataMessageBlueBook6.7 n/a NoCOV_REF_FRAME Coordinatesystemforcovariancematrix n/a NoCX_X Covariancematrix[1,1] km**2 NoCY_X Covariancematrix[2,1] km**2 NoCY_Y Covariancematrix[2,2] km**2 NoCZ_X Covariancematrix[3,1] km**2 NoCZ_Y Covariancematrix[3,2] km**2 NoCZ_Z Covariancematrix[3,3] km**2 NoCX_DOT_X Covariancematrix[4,1] km**2/s NoCX_DOT_Y Covariancematrix[4,2] km**2/s NoCX_DOT_Z Covariancematrix[4,3] km**2/s NoCX_DOT_X_DOT Covariancematrix[4,4] km**2/s**2 NoCY_DOT_X Covariancematrix[5,1] km**2/s NoCY_DOT_Y Covariancematrix[5,2] km**2/s No
MANEUVER NOTIFICATION FORMAT
Page27
TABLE 13: OPM DATA – POSITION/VELOCITY COVARIANCE MATRIX, CONTINUED
Keyword Description Units ObligatoryCY_DOT_Z Covariancematrix[5,3] km**2/s NoCY_DOT_X_DOT Covariancematrix[5,4] km**2/s**2 NoCY_DOT_Y_DOT Covariancematrix[5,5] km**2/s**2 NoCZ_DOT_X Covariancematrix[6,1] km**2/s NoCZ_DOT_Y Covariancematrix[6,2] km**2/s NoCZ_DOT_Z Covariancematrix[6,3] km**2/s NoCZ_DOT_X_DOT Covariancematrix[6,4] km**2/s**2 NoCZ_DOT_Y_DOT Covariancematrix[6,5] km**2/s**2 NoCZ_DOT_Z_DOT Covariancematrix[6,6] km**2/s**2 No
Table 14: OPM DATA – Maneuver Parameters
Keyword Description Units ObligatoryCOMMENT ReferenceODMBlueBook6.7 n/a NoMAN_EPOCH_IGNITION Epochofignition.ReferenceODMBlueBook6.5.9 UTC YesMAN_DURATION Maneuverduration(If=0,impulsivemaneuver) s YesMAN_DELTA_MASS Masschangeduringmaneuver(valueis<0) kg NoMAN_REF_FRAME Coordinatesystemforvelocityincrementvector(value
mustbeselectedfromOPMBlueBookannexA)n/a Yes
MAN_DV_1 1stcomponentofthevelocityincrement km/s YesMAN_DV_2 2ndcomponentofthevelocityincrement km/s YesMAN_DV_3 3rdcomponentofthevelocityincrement km/s YesUSER_DEFINED_MAN_ID AuniqueIDappliedtothespecificmaneuverbythe
operator.UniqueIDsmaybe1‐30alphanumericcharacters,dashes,orunderscores
n/a No
USER_DEFINED_DV_OVERALL
Ifthisfieldisnotpopulated,Space‐TrackwillcalculateitbasedoncomponentDVs
km/s No
USER_DEFINED_EPHEM Nameofthecorrespondingephemerisfile,iftheoperatorhassubmittedephemeristotheJSpOCforscreening
n/a No
Continuedonnextpage
MANEUVER NOTIFICATION FORMAT
Page28
Table 14: OPM DATA – Maneuver Parameters, continued
USER_DEFINED_MAN_PURPOSE
Specifiesthepurposeofthemaneuver.Acceptablevalues:AEROBRAKE(Aerobraking)ATT_ADJUST(Attitudeadjust)COLA(Collisionavoidance)DISPOSAL(Disposal)FLYBY_TARG(Flybytargeting)LEOP(Launch&EarlyOrbit)MNVR_CLEANUP(Maneuvercleanup)MASS_ADJUST(Massadjust)TRIM(Orbittrim)OTHER(Other)PER_RED(Periodreduction)RELOCATION(Relocation)SCI_OBJ(Scienceobjective)SPIN_RATE_ADJUST(Spinrateadjust)SK(Station‐keeping)TRAJ_CORR(Trajectorycorrection)
n/a Yes
USER_DEFINED_TCA ForCOLAmaneuvers,providetheTimeofClosestApproach(TCA)inUTCofthecorrespondingconjunctionevent.RecommendusingtheTCAintheConjunctionDataMessage.
UTC YesforCOLA,Noforallothers
USER_DEFINED_MAN_STATUS
Acceptablevalues:PREDICTED,DETERMINED,CANCELLED.PREDICTED=plannedmaneuverDETERMINED=confirmedmaneuverCANCELLED=cancelledmaneuver
n/a Yes
HOW TO NAME MANEUVER NOTIFICATIONS
Page29
HowtoNameManeuverNotifications
FILE NAMES
TosimplifytheprocessforO/Os,Space‐TrackwillgeneratethefilenameforeachmaneuvernotificationusinginformationprovidedwithintheOPM,specificallytheRELEASABILITY,OBJECT_ID,ORIGINATOR,andCLASSIFICATIONfields.Consequently,theoperatormaynamethefileanythingtheywantaslongasitusesthe.opmextensionandisnotthesamenameasafilealreadyexistingintheoperator’smaneuverfolderonSpace‐Track.org.
FILE VERIFICATION
Space‐TrackwillrevieweachmaneuvernotificationasitisuploadedandrejectOPMsthatdon’tincluderequiredorcorrectlyformattedinformation.ToensureOPMsareaccepted,please:
• Include:
• ORIGINATOR(mustcorrelatetoanexistingCDMaccount)
• USER_DEFINED_CLASSIFICATION(mustbeunclassified)
• OBJECT_ID(objectmustbeinSpace‐Track’scurrentsatellitecatalog)
• USER_DEFINED_NORAD_CAT_ID(objectmustbeinSpace‐Track’scurrentsatellitecatalog)• MAN_EPOCH_IGNITION
• USER_DEFINED_MAN_PURPOSE
• USER_DEFINED_MAN_STATUS
• Remember:
• Inordertosubmitmaneuversforasatellite,theoperatormustalsohavepermissionstoaccessCDMsforthatsatellite
• IftheoperatorprovidesauniqueIDfortheOPM,itcannotexceed30alphanumericcharacters
• IftheoperatordoesnotdesignatetheOPMaspublicorprivate,itwilldefaulttoprivate
• TheremustbemaneuverinformationintheOPM;stateinformationonlywillnotbeaccepted
HOW TO SUBMIT MANEUVER NOTIFICATIONS
Page30
HowtoSubmitManeuverNotifications
OVERVIEW
Maneuvernotificationsmaybesubmittedinthreeways:
1. ThroughthewebsiteSpace‐Track.org(preferred)
1.1 Manually(GUI),or1.2 UsingApplicationProgrammingInterface(API)
2. ByemailtotheJSpOCSpaceflightSafetyCrew
Space‐Track.orgisthemostefficientandsecuremethodofsubmittingmaneuvernotificationsonarecurringbasis.AlloperatorswhohaveaccesstotheOperatorPanelwillautomaticallybegivenpermissionstouploadmaneuvernotificationsforthesatellitesassignedtotheirCDMaccount.TosetupaCDMaccount,contacttheJSpOC’[email protected]+1‐805‐606‐2675.
OnceanactiveCDMaccountisestablished,theoperator(s)assignedtotheaccountwillhaveaccesstotheOperatorandFilesPanels:
Figure12:FilesPanelonSpace‐Track.org
HOW TO SUBMIT MANEUVER NOTIFICATIONS
Page31
SUBMITTING MANEUVER NOTIFICATIONS THROUGH SPACE-TRACK.ORG
OntheFilesPanel,youwillhaveaccesstothe‘Download’and‘Upload’tabs.Onthe‘Upload’tabyoucanuploadavarietyoffilestothefoldersyouhavepermissionsto.Allofthesefolderswilldisplayinthe‘Destination’dropdownmenu:
Figure13:FilesPanelUploadTab‐Maneuvers
MANUAL UPLOAD OF MANEUVER NOTIFICATIONS
1. LogintoSpace‐Track.org,clickon‘Files’atthetopofthepage,andthenclickonthe‘Upload’tab2. Click‘Browse’andselectyourOPMmaneuvernotificationfiles
2.1 Maximumnumberoffilesinasingleuploadis1002.2 Maximumtotalsizeperuploadis60MB2.3 Filesmustbeformattedinaccordancewith‘ManeuverNotificationFormat’
3. Usingthe‘Destination’dropdownmenu,selectthe‘/Maneuvers/YourOrganization’folder.(Note:Tosetupamaneuverfolder,[email protected]+1‐805‐606‐2675.)
4. Click‘Upload’touploadthefiles.5. Afterasuccessfulupload,thefileswilldisplayin‘MyUploads(Last30Days)’Table6. TheSpaceflightSafetyCrewwillreceiveanotificationthatyouhaveuploadedanewmaneuver
HOW TO SUBMIT MANEUVER NOTIFICATIONS
Page32
API UPLOAD OF MANEUVER NOTIFICATIONS
PleasevisitSpace‐Track.org’s‘HowTo’pageforthemostup‐to‐dateguidanceonAPIcapabilities:https://www.space‐track.org/documentation#/howto
Similartomanualuploads:
1. Filesmustbeformattedinaccordancewith‘ManeuverNotificationFormat’2. Afterasuccessfulupload,thefileswilldisplayin‘MyUploads(Last30Days)’Table3. TheJSpOCSpaceflightSafetyCrewwillreceiveanotificationthatyouhaveprovidednewmaneuver
information.However,ifthemaneuverrequiresattentionasahigh‐interestevent,pleasephoneoremailtheSpaceflightSafetyCrew:+1‐805‐605‐[email protected]
UPDATING MANEUVER NOTIFICATIONS
InitialmaneuvernotificationsshouldbeginwithaUSER_DEFINED_MAN_STATUSof‘predicted’or‘determined.’Iftheinitialnotificationis‘determined,’theJSpOCwillconsiderthemaneuverconfirmedandcomplete.Iftheinitialnotificationissubmittedas‘predicted,’thentheJSpOCwillexpectafollow‐onnotificationforthesamesatellitewiththestatus:
• ‘cancelled’ifthemaneuverhasbeenaborted,or
• ‘determined’oncethemaneuveriscomplete
The‘cancelled’and‘determined’OPMscanbecorrelatedtotheoriginal‘predicted’OPMusingthesameMAN_EPOCH_IGNITIONortheUSER_DEFINED_MAN_ID.
Iftwo‘predicted’maneuvershaveoverlappingstartandstoptimes(ascalculatedbytheMAN_EPOCH_IGNITIONandMAN_DURATION)themostrecentlyuploadedmaneuver(indicatedbytheOPMfile’sINSERT_EPOCH)willtakeprecedentoverallotherOPMsthatoccurduringthesametimeperiod,andpreviousmaneuvernotificationswillbecancelled.
Ifyourorganizationdoesn’thaveaccesstotheOperatorandFilesPanels,youmaysendyourmaneuvernotificationsbyemailtotheJSpOCSpaceflightSafetyCrew.Please:
1. Formatthefilesinaccordancewith‘ManeuverNotificationFormat’2. Sendonly.opmfiles‐.zipfilescannotbeaccepted.Or,3. Ifit’snotpossibletousetheOPMformat,maneuvernotificationmaybeprovidedinthebodyofan
email.
CONTACT US
Page33
ContactUs
JSPOC SPACEFLIGHT SAFETY CREW
Forquestionsonconjunctionassessmentandcollisionavoidancesupport,pleasecontacttheJSpOCSpaceflightSafetyCrewbyemailatjspocspacecorrespondence@us.af.milorbyphoneat+1‐805‐605‐3533.Examplesofsupportinclude:
Questionsaboutscreeningresults Screeningsforhigh‐interestevents
MissingCDMs
JSPOC SSA SHARING TEAM
ForquestionsaboutspecializedSSAsupportordataproducts,pleasecontacttheJSpOCSSASharingTeambyemailatjspocssasharing@us.af.milorbyphoneat+1‐805‐606‐2675.Examplesinclude:
SubmittinganOrbitalDataRequestforadvancedservicesorsupport Questionsaboutdataformats Space‐Trackaccessandpermissions
Registeringyoursatellitetoreceivespaceflightsafetysupport
SPACE-TRACK.ORG ADMINISTRATION TEAM
ForquestionsabouttheSpace‐Track.orgwebsite,pleasecontactadmin@space‐track.org.Examplesinclude:
APIqueries Automation
Websiteperformance
