Attitude Control & Pointing
Contact Window Pointing
Understand how the satellite must point toward the ground station during a contact window.
- Time estimate
- 25–30 min
- Complexity
- developing
- Maturity
- pilot ready
- Simulator readiness
- implemented
- Software available now
- Available now in one-axis simulator — `contact_window_pointing` models schedule-driven target changes; RF link is not simulated.
Student path
- Select a pass geometry and a pointing tolerance.
- Read the tracking error and the pass/warn/fail verdict.
- Try a horizon-grazing pass — notice how hard it is to stay within tolerance.
- Copy/export your evidence — local-only, teaching model, not real RF contact.
Learning outcomes
Student can explain the pointing requirement for a contact window and observe it in the simulator.
- Explain why contact window pointing differs from nadir hold.
- Describe the target angle profile during a pass.
- State what happens if pointing error is too large during a contact window.
Concept primer
Understand how the satellite must point toward the ground station during a contact window.
Run contact_window_pointing experiment; observe target angle change and error during window.
Draw a timeline showing satellite angle target during approach, overhead, and departure.
Interactive lab
Teaching-grade software activity slot — not a flight simulator or certified propagator.
Contact window pointing lab
Tracking the ground station through a pass
Tracking error ≈ 1.5° | Tolerance ±5°
passPass — pointing within tolerance throughout pass
High overhead passes are easiest to track — low angular rate, good link geometry.
Pass timeline
Local self-check
Assessment (practice only)
Use this as a self-check and discussion starter. It is local-only and not a grade.
Optional: attaches a local summary (completed / quick checks / checklist count).
Quick check
Multiple choice self-check
This is a local self-check to support discussion. It is not a grade.
Quick check: During a contact window, the satellite must point toward...
Quick check: A horizon-grazing pass is harder to use for communications because...
Discussion prompt
Short answer (local only)
Write notes for yourself or your group. Nothing is submitted.
Reflection: Describe the three phases of a contact window (acquire, track, handoff) in your own words.
Checklist
Local checklist self-check
Use this to verify you covered key ideas. Nothing is submitted.
Self-check before moving on:
0 / 3 checked
Local summary
Assessment summary (practice only)
Completion
0 / 4 sections complete
Quick checks
0 / 2 correct
Shown only to support self-check.
Checklist
0 / 3 items checked
Reminder
Local-only practice summary. Not a grade and not submitted anywhere.
What this preview is / is not
Assessment engine v0 boundary note
- Student view (local practice): use this as a self-check and discussion starter.
- Local-only preview/practice: your answers are not submitted.
- No backend, no accounts, no roster, and no LMS integration.
- Not a grade. No credential or official scoring is implied.
- Teacher visibility into student answers is not implemented in MVPF8.
- Evidence runtime engine arrives in Phase 9 (not in this preview).
Capture
Evidence capture (local-only)
Capture what you did, what changed, what you observed, and how you explain it. This stays in your browser unless you copy/share it manually.
Selected inputs
- Pass geometry: High overhead pass (85° max elevation)
- Pointing tolerance: ±5°
Generated outputs
- Tracking error: 1.5°
- Pass duration: 9 min
- Verdict: Pass — pointing within tolerance throughout pass
Checklist
Evidence checklist
0/3 checked
Evidence artifact (local-only)
Contact Window Pointing
Captured: 2026-05-16T07:38:33.349Z · Level: high_school · Track: attitude_control
Summary
Copyable class summary
Copy a readable summary for class notes, or copy JSON for a structured record. Local-only: nothing is submitted.
Evidence artifact (v1) Activity: Contact Window Pointing Track: attitude_control Learner level: high_school Captured: 2026-05-16T07:38:33.349Z Mission brief: Pass: High overhead pass (85° max elevation). Tolerance: ±5°. Selected inputs: - Pass geometry: High overhead pass (85° max elevation) - Pointing tolerance: ±5° Generated outputs: - Tracking error: 1.5° - Pass duration: 9 min - Verdict: Pass — pointing within tolerance throughout pass Checklist: - [ ] I can explain why attitude must change during a contact window pass. - [ ] I observed how pass geometry affects tracking error in the lab. - [ ] I can describe the acquire → track → handoff sequence. Observations: (not provided) Reflection: Pass: High overhead pass (85° max elevation). Error: 1.5°. Verdict: Pass — pointing within tolerance throughout pass. Model boundary note: Local-only teaching model — not full 3-axis flight ADCS, not a reaction-wheel safety certification, not remote hardware control, not official attitude determination software. Evidence is not submitted anywhere and is not a grade. Policy reminder: - Local-only capture. Not submitted anywhere. Not a grade.
Evidence capture
Expected outputs learners should be able to show after the lab (Phase 9 evidence engine preview available).
- Telemetry during window showing tracking error
- Replay compare of good vs poor pointing during pass segment
Reflection
Describe the pointing sequence needed before and during a contact window.
Responses are not persisted in this preview unless a specific activity component adds storage later.
Assessment / quick check
Why might operators care about pointing error even if the radio is technically transmitting?
Teacher notes
Emphasize ops story: acquire → track → handoff; relate to download planning.
Teacher use
Emphasise the acquire → track → handoff operations story. A horizon pass is short and mechanically demanding — the antenna must sweep fast as the satellite skims the horizon. This connects back to Track 4 (link margin) and ahead to Track 6 (telemetry evidence). RF link is not simulated here.
Next activity
Suggested progression from the mission learning path. Links avoid missing activity routes.