Skip to main content
HonestMOS
●InvestigationsCongress made VA disability claims free to file. An entire industry charges veterans anyway — and nobody can stop them.→
←Back to 13S Space Operations Officer — overview, pay, training, civilian translation, reviews
13SO1-O2

Space Operations Officer

O-1 to O-2 (Junior Officer) · Air Force

O1–O2O3–O4
HEADS UP

13S Space Operations Officer was a Cold-War-vintage Air Force AFSC, but the December 2019 Space Force stand-up moved the entire mission to USSF — 2,410 active-duty 13S Airmen transferred to Space Force as Guardians in the first major IST tranche. If you commissioned as 13S after 2021, you almost certainly went straight into USSF; if you're reading this with an active 13S AFSC, you're in a narrow legacy cohort. The Officer Training Course (OTC) at Peterson SFB became the unified Guardian pipeline in September 2024 (~12 months, covering intel, space, and cyber).

The Honest MOS Read
The 13S career field as an Air Force track is largely a historical artifact. The U.S. Space Force stood up on December 20, 2019; the inaugural Interservice Transfer (IST) window selected 2,410 active-duty space operators (13S) and space systems Airmen for transfer to USSF — that move was completed in tranches starting September 1 of the announced cycle. By 2026 the operational space mission has consolidated under USSF: missile warning, space domain awareness, satellite command and control, electromagnetic warfare against space-based threats, and orbital warfare TTPs all live in Space Force squadrons. If you are an O-1 or O-2 working under an active "13S" AFSC in the Air Force in 2026, your assignment is almost certainly to a residual Air Force role tied to space — joint staff, USAF requirements offices, ICBM-adjacent shops at AFGSC — not a frontline space ops squadron. Read your assignment briefing carefully. If you're actually heading to Space Force (62E in the new USSF coding), the pipeline you're now walking is the consolidated Officer Training Course at Peterson SFB. OTC launched its first class on September 3, 2024 — a 12-month course covering the three Space Force core pillars: intelligence, space operations, and cyber operations. The intent (from official USSF messaging) is "Guardians first, specialists second" — every new Guardian officer goes through the same OTC regardless of which downstream specialty they'll work. The first cohort of approximately 80 officers received their first operational assignments at the end of the program. Initial 13S/space-ops tech training historically ran through the 381st Training Group at Vandenberg SFB (then AFB), but the unified OTC at Peterson is the current entry pipeline. The follow-on professional education stack is Space 100 (initial), Space 200, Space 300 (advanced). Space 200 and Space 300 are run at Peterson; Space 100 is foundational pre-commissioning / early-career material. The "Space 200 before Maj" rule is published USSF policy — you cannot make Major without completing Space 200, which is the structural gate the career field places between O-3 and O-4. Base options inside USSF: Schriever SFB (CO), Peterson SFB (CO), Buckley SFB (CO), Vandenberg SFB (CA), Patrick SFB (FL), Los Angeles AFB (CA — soon to be re-designated). The community is geographically tight; Colorado Front Range is the operational center of gravity. The deployments are not the same shape as the rated Air Force — most Guardian work is CONUS-based ops floor work running real-time effects on orbit-relevant timelines. The financial pitch is structurally different from rated AF: no AvIP, no AvB, no ADSC tied to wings. USSF has its own promotion math: the 2024 O-4 board selected 210 captains for Major (the LSF-O and LSF-F categories); rates per category are published but the sample size is small relative to the AF rated communities (USSF has fewer than 10,000 active personnel total).
Career Arc
  • 01Commission → Officer Training Course (OTC) at Peterson SFB — ~12 months, three pillars (intel, space, cyber).
  • 02First operational assignment from OTC: Schriever / Peterson / Buckley / Vandenberg / Patrick / LA AFB squadrons.
  • 03MQT / IQT on specific weapon system (missile warning, SDA, SATCOM, EW, orbital warfare, etc.).
  • 04Mission Ready certification on operational floor / position.
  • 05Space 100 / 200 progression — Space 200 before Major (USSF policy).
  • 06Ground job rotation: scheduling, training, evaluations, OIC roles.
  • 07~Month 48: O-3 (Capt) — DOPMA timing, very high selection rate.
Common Screwups
  • ×Treating 13S as a current Air Force track. It's effectively legacy — the operational mission lives in USSF as 62E. Confirm your actual coding before planning your career.
  • ×Skipping Space 200. It's the structural gate to Major in USSF. There is no other ticket through.
  • ×Treating OTC as a check-the-box. It is the new institutional baseline for Guardian identity; senior leaders read it carefully.
  • ×DUI / Art 15. Same impact across DAF — career-ending, asked about forever.
  • ×Fitness fails — small-service culture means QoL impact is visible faster than in larger AF communities.

A Day in the Life

  • 0530Wake. Check the shift-turnover notes on your personal tablet before heading in — did anything happen on overnight watch that the oncoming briefing will reference? Text the outgoing crew lead if an anomaly is still active.
  • 0600Arrive at the ops building. Badge in through the outer perimeter — personal phone in the lockbox before entering the SCIF. Every time. No exceptions.
  • 0615-0700Shift turnover brief. The outgoing Mission Commander walks the crew through system status, any anomalies from the last period, current operational picture, and any command-level guidance affecting the watch. Take notes. Ask one clarifying question if you have one; do not ask questions you could answer from the status board.
  • 0700-0730Pre-contact preparation. Review the scheduled contact window: uplink parameters, expected telemetry configuration, standing order constraints, contingency branches if off-nominal. Confirm comms-link readiness with the ground system operator. Brief the MC on your pre-contact assessment before the window opens.
  • 0730-0930Contact window execution. As trainee crew: monitor, execute per standing orders, flag any deviation to MC immediately. The MC is the decision authority; your role is precise execution and clean observation. Log all actions in real time — not retrospectively.
  • 0930-1030Post-contact window. Write the post-contact report while the MC debriefs the crew. Verify timeline against the automated system log — any discrepancy between your notes and the log needs a reconciliation note, not an assumption that the log is right. Submit before the next crew rotation.
  • 1030-1200MQT academics or simulator event (if scheduled). This is the block the training section uses for formal MQT events. Treat every simulator event as a graded evaluation — the instructor writes a debrief that goes in your training record. Bring your own notes from the pre-event study; show up having read the applicable procedure.
  • 1200-1300Lunch. Eat with the crew. The culture of the ops floor — the way senior Guardians talk about the mission, the way anomalies get discussed informally, the institutional norms around crew discipline — is transmitted in these informal conversations more than in any formal training event. Listen more than you talk.
  • 1300-1500Afternoon contact window (if scheduled) or ground-job work. Ground-job work at this tier means: scheduling support, training-section tasker, OPR support-form drafting, or unit additional duty. Every LT has at least one additional duty; manage it so it does not bleed into contact-window preparation.
  • 1500-1700Doctrine and self-development. Block two hours of structured reading per shift-day when no additional contact window is scheduled. USSPD 1 in week 1. JP 3-14 in week 2. CFETP review in week 3. After initial setup: rotate through the current anomaly database (read the last 90 days of post-contact reports to understand what has gone wrong on this system before you touch it).
  • 1700-1800Shift turnover prep. Brief the oncoming crew lead on system status, any anomalies, open action items, and handoff notes. The quality of your turnover brief is an observable data point; the MC who receives a clean turnover remembers which crew did it.
  • 1800End of shift. Retrieve personal phone. Leave the building. The Guardian who checks work systems on a personal device outside the SCIF perimeter has a conversation with the SSO. Do not do it.
  • 1900-2100Personal time. MQT pre-study if a simulator event is next scheduled. Physical fitness maintenance — DAFMAN 36-2905 PFA is not the target; operational fitness is the target and the PFA is the byproduct. The LT who falls behind on fitness in a 10,000-person service has a visibility problem faster than in the AF.
  • Shift rotation / contingencyOps floor schedule rotates across day, swing, and midnight shifts depending on unit and mission. Contingency activations collapse the schedule. When the phone rings at 0300 for an anomaly requiring additional crew, the Guardian who knows the procedure cold is the one the MC calls first. That reputation is built in the everyday watches, not the contingency.

Weekly Cadence

The weekly rhythm for a junior 13S at an operational Space Delta squadron is anchored to the watchbill. A typical watchbill runs in 8- to 12-hour blocks across three shifts, with crew rotations structured around contact window scheduling for the specific mission set the squadron owns. A SATCOM C2 squadron at Schriever SFB runs a different contact density than a Missile Warning squadron at Buckley SFB — SATCOM has scheduled contact windows that can be forecasted; missile warning runs a continuous monitoring watch. GPS at Schriever runs the Master Control Station function with its own operational rhythm. Understand the specific watchbill structure your unit uses before your first week, and build your personal schedule around it. On non-watch days — typically two to three days per week depending on the watchbill rotation — the junior 13S is in MQT events (academics or simulator), ground-job billets, or professional development. MQT events should be the calendar priority; the ground-job billet and additional duties are managed around them, not the other way around. The junior officer who treats MQT events as interruptible and ground-job work as the primary obligation has inverted the priority stack the squadron DO cares about. The training section schedules simulator blocks weeks out; confirm your blocks on day one of each month and protect them. The week's third rhythm is institutional engagement under the Guardian Talent Management framework. The Space Force's developmental framework for junior officers is more deliberate than the legacy Air Force model — the SF has worked to build a formal mentorship structure, developmental assignment guidance, and career-milestone tracking that is more granular than the AF's legacy informal model. The junior 13S who actively engages — reads the SF officer career-development guidance, initiates rater-ratee conversations rather than waiting for the rater, and identifies the 24-month and 36-month MQT and professional-education milestones with specific planned completion dates — tracks ahead of the officer who waits for the institution to manage his development.

Key Skills — How to Drill Each

  1. 01
    Execute contact events and routine spacecraft health monitoring per squadron standing orders — anomaly recognition and immediate escalation to Mission Commander.
    The contact event is the job's atomic unit. Drill the pre-contact checklist until it is automatic — system configuration, comms-link verification, uplink parameter review, contingency branch selection. When an anomaly indication fires, run the applicable off-nominal procedure to the first decision point and call the MC immediately; the guidance that says 'notify the MC of any non-standard indication' exists precisely because your judgment as a trainee crew member is not calibrated yet. The Guardian who learns to say 'MC, I have a non-standard indication on X subsystem, I am at step 3 of the off-nominal procedure, requesting guidance' is the Guardian the MC trusts to hold a solo watch inside six months.
  2. 02
    Complete Mission Qualification Training (MQT) events in sequence with no lapsed currency windows.
    Build a personal MQT tracker on day one: every event, the due date, the currency refresh window, and who signs it. The squadron training section has the master database but you own your card. When a sim event gets scheduled, confirm the debrief date before you leave the scheduling meeting — the event that has no debrief scheduled is the event that expires without credit. The DO reads the currency report before every watchbill build; the officer whose card has a gap is the officer who drops off the watchbill. Dropping off the watchbill is the first event in a spiral that takes 18 months to recover.
  3. 03
    Brief the mission-type order for a scheduled contact event: objectives, constraints, execution timeline, and at least two contingency branches.
    The Space Force uses Mission-Type Orders derived from the joint doctrine in JP 3-14 and adapted for the space operations context. Your MTO brief should cover: mission objective (what we are doing and what 'done' looks like), constraints (power budget limits, thermal limits, contact window duration, priority of systems if a resource conflict emerges), execution timeline (keyed to the contact window, with time hacks for each critical action), and contingency branches (what the crew does if the uplink fails, if telemetry drops, if the ground system alarms before contact). Rehearse the brief with your trainer before you deliver it to the MC for the first time. The MC who sits your brief is grading whether you have internalized the mission or are reading from the checklist.
  4. 04
    Read and apply USSPD 1 and JP 3-14 as operational framing, not bookshelf doctrine.
    USSPD 1 is the Space Force's foundational doctrine publication — it defines the SF's warfighting functions, the relationship between space operations and joint force operations, and the conceptual framework that every operational brief in the Space Force implicitly references. JP 3-14 is the joint doctrinal frame for space operations — the document the USSPACECOM J3 and COCOM planners are working from when space effects are integrated into campaign plans. Read USSPD 1 in the first 30 days at your squadron. Read JP 3-14 Chapter 3 and Chapter 5 before your first interaction with the joint space operations cell. The junior officer who can frame his mission in joint doctrine terms is the officer the squadron DO sends to the joint-staff brief.
  5. 05
    Maintain TS/SCI clearance discipline: self-report, foreign-contact logging, SCIF physical security, and no cleared-device hygiene lapses.
    Your TS/SCI access is the product of a years-long government investigation and is the credential that enables every task in this career field. The self-report requirement under DoDM 5240.01 covers foreign contacts (any contact with a foreign national that involves an exchange about your work or your organization), foreign travel (pre-trip notification is required for most countries; post-trip debrief is required for all foreign travel), financial distress (debt counseling, garnishments, bankruptcy), and any contact that felt like an elicitation attempt. Report immediately, not at the next poly. The SCIF physical security requirements are absolute: no unsecured devices (personal phone, laptop, tablet) inside the SCIF boundary, no exceptions, no 'I just had it for a second.' The SSO's inspection of your facility will start with the access logs and the device policy acknowledgment file.
  6. 06
    Write a post-contact report and anomaly write-up that the next shift understands without calling you.
    The post-contact report is the mission record: contact time, systems operated, anomalies observed, actions taken, status at contact end, handoff notes for the next shift. The standard is that the oncoming crew reads your write-up and knows exactly what state the system is in without a 10-minute phone call. Write it during the debrief window while the MC is still in the room — the MC's real-time correction of your write-up is the most valuable feedback you get. Anomaly write-ups follow a structured format: what was observed, when, in what system state, what procedure was applied, what result, what action is pending (if any). The system engineer reads anomaly write-ups to build trend analysis; a write-up with a wrong timestamp or a missing parameter corrupts their data. Precision in writing is operational discipline.

Manuals & References — What Chapters Matter

  • USSPD 1 — U.S. Space Force Doctrine Publication 1, 'The Spacepower Doctrine.'
    Read it once in its entirety during the first 30 days and again when you receive orders to a joint billet. It defines the Space Force's operational roles (space superiority, space mobility and logistics, space domain awareness, space access and sustainment, C2, ISR), the relationship between spacepower and joint force operations, and the institutional frame every Space Force senior leader is working from. The junior officer who uses USSPD 1 terminology in mission briefings signals institutional alignment; the one who does not signal it signals that he is still using Air Force reflexes.
  • JP 3-14 — Joint Publication 3-14, Space Operations.
    Chapters 3 and 4 are the operational spine: Chapter 3 covers Space Control operations (offensive and defensive); Chapter 4 covers Space Force Application and Space Support. Read Chapter 5 (C2 of Space Operations) before any exposure to the USSPACECOM Joint Space Operations Center (JSpOC) function. The terminology in JP 3-14 is the terminology the COCOM J3 and CCMD planners use; showing up to a joint brief without it is like showing up to the gunnery table without having read the manual.
  • CFETP 13SX — Career Field Education and Training Plan for Space Operations Officers.
    The institutional training roadmap. Read the entire document in the first week: the training phases, the mandatory events, the currency windows, and the upgrade timeline from initial qual through Mission Commander and beyond. The CFETP is also the document your first rater uses to build the support-form bullets framing your OPR — the officer who knows what the CFETP says his milestones are is the officer who writes the support-form input the rater does not have to generate from scratch.
  • DAFMAN 36-2406 — Officer Evaluation System.
    Read it before your first initial counseling session with your rater. Chapters 3 and 4 cover the OPR process, the support-form input requirements, the rating scheme, and the senior rater profile. The junior officer who understands how the rating system works is the junior officer who gives his rater usable support-form bullets and understands what 'top block' means in terms of the senior rater's profile constraint.
  • Space 100 / Space 200 course materials (STARCOM professional education series).
    Space 100 is the foundational space operations education; Space 200 is the operational space integration course that is the published structural gate to Major in USSF. Treat Space 200 completion as a must-plan calendar item, not an afterthought — the O-4 board reads the record, and an unexplained Space 200 absence is a question the board answers without your input. Space 200 enrollment and scheduling runs through STARCOM; identify your target class date before the 36-month mark.

Standards — How to Hit Each

  • Crew Commander (or equivalent position qualification) earned at the MQT timeline the squadron publishes — not late.
    The squadron training section publishes the MQT event timeline on arrival. Your task is to complete every event before its window closes. The bottleneck is usually simulator availability and Mission Commander scheduling for live-event supervision. Book simulator blocks the day you receive your MQT plan; confirm MC availability for live-event qualifications before the scheduling window opens for competing crews. The officer who finishes MQT ahead of the published timeline is the officer the DO assigns to the most challenging contact windows. The officer who finishes late — even by a week — is the officer the DO notes without being asked.
  • DOPMA promotion math: O-2 (1st Lt) at 24 months commissioned; O-3 (Capt) board at approximately 48 months.
    Both are near-automatic for fully-qualified officers in a Space Force officer corps that is still growth-mode. The practical implication: the OPR you write for the O-3 board is the OPR from your first operational assignment, and its quality depends on how seriously you took MQT completion, the post-contact write-up discipline, and the squadron staff billet. Pull the current USSF officer promotion board release from the Space Force Personnel Center (SFPC) for the specific FY rate — do not assume from rumor.
  • Space 200 completion before the O-4 board — published USSF structural gate.
    Space 200 is not an elective. The course is offered at Peterson SFB; STARCOM manages enrollment. Contact your unit training officer at the 30-month mark to identify available class dates. The officer who attends at 36 months commissioned arrives at the course with two operational years of context and gets substantially more out of the curriculum than the officer who scrambles to attend at 47 months before the board convenes.
  • Physical Fitness Assessment under DAFMAN 36-2905 passed every cycle.
    The SF uses the DAF Physical Fitness Assessment (PFA). Failures are tracked and a pattern of failures under DAFMAN 36-2905 can initiate administrative separation. In a service of fewer than 10,000 active personnel, a PFA failure is institutionally visible faster than in the larger Air Force. Build a year-round fitness maintenance program that treats the PFA as a byproduct of fitness, not the target. The officer who barely passes has a harder conversation with the rater than the officer who clearly exceeds.
  • OPR initial counseling documented within 30 days of assignment assumption.
    DAFMAN 36-2406 requires the rater to conduct an initial counseling session within 30 days of a new ratee-rater relationship. The junior officer who arrives at the session with a draft support-form input, a list of near-term MQT milestones, and a question about the rater's priorities is the officer who gets a support form calibrated to actual performance rather than a generic paragraph the rater produced from the position description.

Technical Mistakes — Concrete Consequences

  • Missing an MQT currency event window without a documented rescheduling request.
    Lapsed MQT currency pulls you off the watchbill while a requalification event is scheduled; the watchbill gap is visible to the DO, the CC, and the scheduling NCO simultaneously. If the gap crosses an OPR period, it appears in the rater's notes as 'currency lapse requiring remediation' — a phrase that costs a bullet in the support form. The officer who stays current has the inverse problem: the DO is fighting over who gets the most interesting contact windows.
  • Failing to escalate an anomaly indication to the Mission Commander at the first decision point.
    The off-nominal procedure exists because the Mission Commander has training and experience the trainee crew member does not yet have. The junior officer who exercises independent judgment on an anomaly indication and turns out to be wrong does not recover the reputation from that incident inside one assignment cycle. The MC who was not called and found out about the anomaly at end-of-shift will tell the DO before the shift is over. The cascading consequence is not the anomaly itself — it is the institutional read that your judgment cannot be trusted alone on the ops floor.
  • Submitting a post-contact report with a timeline discrepancy.
    The anomaly database feeds the system engineer's trend analysis; the program office uses the trend data to plan maintenance windows and manage system life. A post-contact report with a wrong timestamp corrupts the database entry. The system engineer finds the discrepancy in the next audit and traces it to the report originator. The correction process generates a formal data-correction request and a notation in the contact-report record that the original was in error — that notation is permanent and is read by every subsequent system audit.
  • Bringing a personal electronic device into the SCIF.
    One visit with an unsecured device initiates a Security Information File (SIF) review with the SSO. The SIF review generates an SF-86 annotation visible at every subsequent personnel security investigation reinvestigation. The officer with a SIF entry is not automatically career-dead, but the clearance holder who has never generated a security incident is the clearance holder the program office puts in front of a sensitive compartment read-on without administrative friction. Unsecured-device incidents also put the SCIF facility accreditation at risk — the SSO is now defending the facility's authorization to the authorizing official, a consequence that extends far beyond the individual officer.
  • Posting any unit-identifying, mission-specific, or assignment-specific information on any public-facing platform.
    Space Force mission sets — SATCOM C2, missile warning, SDA, orbital warfare — are adversary-targeted intelligence collection priorities. The People's Liberation Army Strategic Support Force (restructured as the Aerospace Force in 2024) runs open-source collection against US space operations infrastructure; the FSB and GRU maintain similar programs against US MILSATCOM and missile warning systems. An Instagram post with a squadron patch, a LinkedIn entry mentioning the specific system operated, a Twitter reply that identifies your installation by name — each of these generates a collection thread the adversary continues to develop. AR 530-1 / DAFI 10-701 OPSEC requirements apply; a violation that reaches the J2 or the installation security officer is an OPR-cycle event.

Career Decisions at This Rank

  • IST assignment location preference — and whether to advocate for it.
    The 13S IST pipeline sends officers to Vandenberg SFB for foundational training, but first operational assignments branch across Schriever SFB (SATCOM C2, SDA, GPS), Buckley SFB (Missile Warning), Peterson SFB (SDA, C2, USSPACECOM adjacent), Vandenberg SFB (launch operations support), and Patrick SFB (range). The assignment process runs through SF personnel management; junior officers have limited direct influence but are asked for preferences. The honest analysis: the mission set your first squadron owns shapes the next three years of qualification, the adversary picture you study, and the post-service market language you can speak credibly. Missile Warning is high-operational-tempo, high-stakes, deeply integrated with NORAD/USNORTHCOM — it builds joint-ops instincts faster. SATCOM C2 at Schriever builds the satellite operations credential that commercial space (SpaceX, SES Government Solutions, Viasat, Hughes, the various MILSATCOM contractors) values most directly. SDA in the Delta 2 structure builds the adversary-space-activity analytical credential the IC hires against. All are valid; pick based on where your technical and operational interests genuinely lie, not on which base has the better quality of life.
  • Pace of MQT progression — move fast or build deep?
    Some junior officers push through MQT as fast as the simulator schedule allows, achieving Crew Commander qualification in the minimum window. Others move at the MQT timeline's standard pace, treating each event as a competence consolidation rather than a box to check. The honest analysis: in a small service where reputation propagates fast, quality of qualification matters more than speed of qualification. The MC who signed your Crew Commander card is the MC who gives you the first solo watch — and the solo watch is where the ops-floor reputation gets built. If your simulator events are producing clean debrief notes and the MC is raising the complexity of your assigned training scenarios, you are on the right trajectory. If your debrief notes have recurring gaps and the MC is still babysitting your basic contact execution, more simulator repetitions before the qual event is the right call regardless of what the calendar says.
  • Ground-job billet selection — training, scheduling, evaluations, or weapons/tactics.
    Every junior 13S holds a squadron ground-job billet alongside the watchbill. The standard options are: training (managing the squadron's MQT database and training event scheduling — the most operationally visible ground job because the DO interacts with it daily), scheduling (building the watchbill — the job that puts your name in front of every crew member and every shift lead daily), evaluations (supporting the standardization and evaluation officer — the job with direct visibility to standards enforcement), and weapons/tactics (the squadron weapons shop — the most technically demanding ground job and the one most correlated with the Weapons Officer pipeline downstream). The honest analysis: take the job that develops the specific skill you are weakest in. If your analytical and writing skills are strong, take scheduling and build the interpersonal-network skill. If your technical depth is strong, take evaluations or weapons and build the standards-enforcement skill. The first-assignment ground job is developmental, not career-defining — the only wrong choice is to treat it as an obligation to minimize.
  • Space 200 timing — earliest available class or wait for post-deployment?
    Space 200 is a published structural gate to Major. The course is offered at Peterson SFB and enrollment runs through STARCOM. The honest analysis: attend at 30-36 months commissioned if a class is available. The officer who completes Space 200 at 36 months arrives at the O-4 IPZ board (~48-50 months) with two full operational cycles of context after completing Space 200, which produces better OPR narrative than the officer who completed Space 200 in the last six months before the board. Early completion also means that if your current assignment produces an operational deployment or contingency activation that blocks the original class date, you have a reschedule buffer before the board window.
  • When to initiate the senior mentor / career-development conversation with the squadron CC.
    The Guardian Talent Management framework structures career-development conversations more formally than the legacy AF model. The junior officer who schedules a one-on-one with the squadron CC at the six-month mark — with MQT progress documented, Space 200 class date identified, and a genuine question about the CC's read on development priorities — is the officer the CC remembers when the Delta commander asks who the strong junior officers are. Do not wait for the annual OPR cycle to initiate this conversation. The CC who has never talked to you outside of formal rating events has no affirmative case to make on your behalf when the Delta commander is building the next year's joint-billet slate.

How the Seat Varies by Unit Type

  • SATCOM C2 squadron (Schriever SFB, CO — Space Delta 8)
    The SATCOM C2 squadron operates the MILSATCOM constellation ground infrastructure — Wideband Global SATCOM (WGS), Advanced Extremely High Frequency (AEHF), the various MILSATCOM command-and-control systems. Contact events are forecasted and scheduled against the orbital mechanics of each satellite, producing a predictable but dense watchbill with defined contact windows throughout the day and night cycles. The ground-system software, the command uplink procedures, and the satellite-health monitoring are the technical core. The post-service credential here is the satellite-operations proficiency that commercial SATCOM operators (SES, Intelsat, Viasat, Hughes, the various GEO and MEO commercial satellite operators) and MILSATCOM prime contractors (Boeing, Northrop, Lockheed — all of whom run SATCOM ground operations as part of their contracts) hire against specifically.
  • Missile Warning squadron (Buckley SFB, CO — Space Delta 4)
    The Missile Warning squadrons operate the Space-Based Infrared System (SBIRS) / Next-Generation Overhead Persistent Infrared (Next-Gen OPIR) constellation and the associated missile warning ground systems. The mission runs 24/7 with zero interruption tolerance — the data products feed NORAD, USNORTHCOM, and the National Missile Defense Command and Control architecture in real time. The watch culture is highest-tension in the 13S community because an error or missed indication at this position has the most direct national-security consequence of any 13S billet. The joint integration with NORAD is continuous and direct; junior 13S officers at Buckley interact with NORAD watch team leadership regularly. The technical and operational credential here is the deepest threat-response and sensor-integration experience available in the 13S career field.
  • Space Domain Awareness / GPS squadron (Schriever SFB, CO — Space Delta 2 / Delta 31)
    The SDA squadrons operate ground-based sensors (including the Space Fence on Kwajalein Atoll, operated by the 20th Space Control Squadron), the SSN (Space Surveillance Network) sensor network management, and the space object catalog maintenance that underpins everything from orbital deconfliction to adversary counterspace monitoring. The GPS Master Control Station function (Space Delta 31 at Schriever) runs the operations that maintain the GPS constellation's operational accuracy — a mission whose downstream consequence touches every GPS-dependent system on Earth. The SDA community builds the strongest adversary-space-activity analytical credential in the 13S career field, which maps directly to IC analyst roles (NRO, NGA, DIA — all maintain space intelligence analysis functions that recruit from the SDA community).
  • CCMD joint space billet (USSPACECOM / STRATCOM / INDOPACOM J-space staff)
    Joint space billets at USSPACECOM (Peterson SFB / Cheyenne Mountain Space Force Station), USSTRATCOM (Offutt AFB), INDOPACOM (Camp H.M. Smith), and the other COCOMs put the junior 13S officer in the joint operational planning and operations execution environment early. The work is less hands-on-systems and more integrative: translating space domain conditions and space effects into campaign plan language, supporting J3 operations briefs with space situational awareness products, managing information flow between Space Delta squadrons and the COCOM staff. The joint-billet credential (JDA credit toward JPME-II) and the exposure to COCOM senior leadership and foreign partner liaison officers at the O-1/O-2 tier are real career differentiators. The downside: less hands-on crew qualification time, which means a crew currency re-establishment event when you return to a Delta squadron.
  • STARCOM instructor / training staff billet (Vandenberg SFB, CA)
    Instructor billets at STARCOM — the Space Training and Readiness Command — put the junior 13S into the pipeline that trains the next cohort of 13S officers. The work is primarily instructional: delivering academics, running simulator scenarios, evaluating trainee performance, writing debrief notes. The credential is pedagogical depth and institutional influence — instructors shape how an entire cohort of junior Guardians learns the mission. The downside: you are running other people's training rather than building your own operational depth, and the next assignment back into an operational Delta squadron requires a re-qualification cycle on the specific system the Delta owns. STARCOM instructor billets are generally for officers who have completed at least one full operational crew tour and can translate operational experience into effective instruction.

What Good Looks Like at This Rank

The good junior 13S is immediately recognizable because he achieves Crew Commander qualification before the MQT timeline expires, not because he squeezed under it. His post-contact reports are clean — timeline accurate, system states documented, handoff notes sufficient that the oncoming crew settles in without a phone call. When an anomaly fires on his watch, his first action is the checklist, his second action is the MC call, and his third action is the documentation. He does not problem-solve before he escalates; he escalates and then problem-solves with the MC in the room. The Mission Commander he trains under asks the DO for this officer's watchbill slots first because the trust has been built through precision repetition, not personality. Off the ops floor, this officer has read USSPD 1 in the first 30 days, JP 3-14 before the first joint-cell exposure, and the CFETP before the first counseling session with the rater. The support-form input he hands the rater is calibrated to the rater's stated priorities from the initial counseling and to the actual MQT milestones accomplished. The OPR is written before the rater asks. Space 200 is calendared at the 30-month mark, not the 47-month mark. The SCIF security discipline is absolute — phone in the lockbox before the badge swipe, every visit, no exceptions — because this officer understands that one SIF entry follows every subsequent reinvestigation for the length of a 30-year career. The institutional dimension of the good junior 13S is real in a way that does not apply in a larger service. The Space Force has fewer than 10,000 active members. The 13S officer corps is a fraction of that. The squadron commander and the Delta commander know every junior officer by name, by MQT status, and by the character signal the ops-floor behavior projects. The junior 13S who operates with precision, escalates correctly, writes clean, maintains the clearance, and stays current is the junior 13S whose name the CC uses when the USSPACECOM J3 asks for a sharp LT to support an operational planning event. That referral is the first career-shaping moment, and it belongs to the Guardian who earned it.

Preview — The Next Rank

O-3 (Captain) is when the Space Force stops evaluating whether you can hold a watch and starts evaluating whether you can lead a mission. The Mission Commander qualification is the visible threshold: the MC runs the contact window, makes the escalation-or-continue decision when an anomaly fires, manages the crew's execution under contingency conditions, and writes the post-contact assessment that goes into the operational record. Every senior Guardian in your squadron has an opinion about which junior officers are MC-ready and which are still building the foundational reps. You want to be unambiguously in the first category when the O-3 promotion arrives. The Captain years are also when the institutional calculus of a small service becomes most consequential. The SF officer corps at the O-3/O-4 level is small enough that the Delta commander knows your name, your MQT status, and the character signal your behavior on the ops floor has projected. The joint-billet slate for USSPACECOM, the COCOM J-space staffs, and the emerging Space Force billets at geographic COCOM locations is built by name; the Delta commander who has a strong read on you is the Delta commander who puts your name on the billet request. Start the joint-billet conversation at the 36-month mark, not the 48-month mark. The structural gate that separates the capable Captain from the Major-board competitive Captain is Space 200. There is no quiet workaround, no waiver environment — the course runs at Peterson SFB and the completion date is on your record. Plan the enrollment at the 30-month mark. Beyond Space 200, the field-grade trajectory conversation — DO pipeline, command screen, joint-duty credential — begins in earnest at O-3. The Guardian who has mapped the next three years of development milestones at the O-3 pin-on ceremony is the Guardian whose O-4 board record makes a coherent story. The one who plans it at the O-4 IPZ window is the one whose board narrative has gaps.
FAQ

13S O1-O2 — Frequently Asked Questions

Q01What does a O1-O2 13S (Space Operations Officer) actually do?
You accessed through USAFA, AF ROTC, or OTS, received your 13S designation, and are now working through the 13S Initial Skills Training pipeline at Vandenberg SFB under STARCOM before arriving at your first Space Delta operational squadron.
Q02What's the most important thing to know as a O1-O2 13S?
13S Space Operations Officer was a Cold-War-vintage Air Force AFSC, but the December 2019 Space Force stand-up moved the entire mission to USSF — 2,410 active-duty 13S Airmen transferred to Space Force as Guardians in the first major IST tranche.
Q03What does a typical day look like for a O1-O2 13S?
Time-blocked day at the O1-O2 13S rank tier: 0530 Wake. Check the shift-turnover notes on your personal tablet before heading in — did anything happen on overnight watch that the oncoming briefing will reference? Text the outgoing crew lead if an anomaly is still active, 0600 Arrive at the ops building. Badge in through the outer perimeter — personal phone in the lockbox before entering the SCIF. Every time. No exceptions, 0615-0700 Shift turnover brief. The outgoing Mission Commander walks the crew through system status, any anomalies from the last period, current operational picture,…
Q04What mistakes get O1-O2 13S soldiers fired or relieved?
Treating 13S as a current Air Force track. It's effectively legacy — the operational mission lives in USSF as 62E. Confirm your actual coding before planning your career; Skipping Space 200. It's the structural gate to Major in USSF. There is no other ticket through; Treating OTC as a check-the-box. It is the new institutional baseline for Guardian identity; senior leaders read it carefully
Q05What career decisions matter most at the O1-O2 13S rank tier?
IST assignment location preference — and whether to advocate for it — The 13S IST pipeline sends officers to Vandenberg SFB for foundational training, but first operational assignments branch across Schriever SFB (SATCOM C2, SDA, GPS), Buckley SFB (Missile Warning), Peterson SFB (SDA, C2, USSPACECOM adjacent), Vandenberg SFB (launch operations support), and Patrick SFB (range). The assignment process runs through SF personnel management; junior officers have limited direct influence but are asked for preferences.…
Q06What's next after O1-O2 for a 13S (Space Operations Officer) in the Air Force?
O-3 (Captain) is when the Space Force stops evaluating whether you can hold a watch and starts evaluating whether you can lead a mission.
Q07What manuals and regulations does a O1-O2 13S need to know cold?
USSPD 1 — U.S. Space Force Doctrine Publication 1, "The Spacepower Doctrine." The foundational Space Force operational frame.; JP 3-14 — Space Operations. The joint operational doctrine for space. Read Chapter 3 (Offensive / Defensive Space Operations) before your first mission briefing.; CFETP 13SX — Career Field Education and Training Plan for 13S Space Operations Officers. Your institutional training roadmap.

This playbook has no tips yet. Be the first to share what you know.

Published by the Honest MOS Editorial DeskVerified against DoD/.gov sourcesUpdated May 2026Editorial standards