DSST Astronomy common mistakes
DSST Astronomy · Understand the traps and how to avoid them.
Using the naked-eye formula for angular size (size = distance × angle) without converting arcseconds or arcminutes to radians, so a galaxy 1 arcminute across at 10 Mpc comes out as a nonsense number.
The small-angle relation θ = s/d only holds in radians; candidates plug degrees or arcminutes straight in because the arithmetic looks tidy and the units never get checked.
What to do instead
Before any angular-size or distance calculation, write the angle in radians (1° = 0.01745 rad, 1′ = 2.91×10⁻⁴ rad, 1″ = 4.85×10⁻⁶ rad) and sanity-check the answer against a known object, e.g. the Moon's 0.5° subtends about 3,500 km at 384,000 km.
Treating Kepler's third law as p² = a³ with whatever units are convenient, mixing years with AU, or applying it unchanged to a binary star system without using total mass.
The clean form p² = a³ is only valid for solar masses, AU, and years around the Sun; candidates memorize the shorthand and forget the general form p² = a³/(M₁+M₂).
What to do instead
Always write the general form p² = 4π²a³/[G(M₁+M₂)] and reduce to p² = a³ only after confirming units are years, AU, and solar masses; for binaries use the total mass and remember a is the semi-major axis of the relative orbit.
Confusing sidereal and synodic periods, or assuming a planet's synodic period equals its orbital period when working out when it returns to opposition or conjunction.
Textbook diagrams show one orbit and one alignment, so the Earth's own motion gets ignored; the 1/S = 1/P − 1/E relation for superior planets is easy to forget under time pressure.
What to do instead
Sketch Earth and the planet at two successive alignments before computing; use 1/S = |1/P − 1/E| and check Mars gives S ≈ 780 days and Jupiter ≈ 399 days as a self-test.
Reading a star's colour or spectral class as a direct measure of its distance, or ranking stars by apparent magnitude when the question asks about luminosity.
Bright stars in the sky are often also nearby and blue, so apparent brightness, colour, and proximity get conflated; the inverse-square law and the distance modulus are the missing link.
What to do instead
Separate the three observables explicitly: colour gives temperature, apparent magnitude gives flux, and only with distance (parallax or a standard candle) can you get luminosity via m − M = 5 log₁₀(d/10 pc); practise converting one star (e.g. Sun: M_V = +4.8) both ways.
Assuming a telescope's magnification is the key performance number and choosing the highest-power eyepiece, rather than evaluating aperture for light grasp and resolution.
Consumer marketing stresses magnification, and the eyepiece formula (focal length ratio) is the easiest calculation to remember, so candidates optimise the wrong variable.
What to do instead
State the rule first: aperture sets limiting magnitude and the diffraction limit (θ ≈ 1.22λ/D), and useful magnification tops out near 50× per inch of aperture; when a question asks what improves faint-object detection or resolving power, answer with aperture, not magnification.
Mixing up the terrestrial and Jovian planet families when asked about density, rotation, moons, or atmospheric composition, and treating Pluto as a Jovian or terrestrial planet.
Memorised lists blur together, and the exam often asks about an outlier (Mercury's large core, Venus's retrograde spin, Jupiter's heat source) that breaks the simple dichotomy.
What to do instead
Build a one-page comparison table (size, density, composition, moons, rings, rotation) for each planet and add the exceptions explicitly; classify Pluto as a Kuiper Belt dwarf planet and note it is icy and small.
Describing stellar evolution as a single track for all stars, e.g. saying the Sun will become a supernova or that all stars end as black holes.
The main-sequence lifetime and end state depend on initial mass, and the branching at about 8 and about 20 solar masses is easy to compress into one story.
What to do instead
Memorise the mass thresholds: below about 0.08 M☉ no fusion (brown dwarf), Sun-like stars end as white dwarfs via planetary nebula, above about 8 M☉ core-collapse supernova to neutron star, above about 20 M☉ may leave a black hole; state the threshold in any evolution answer.
Confusing the Milky Way's structural components and the Sun's place in them, e.g. placing the Sun in the galactic bulge or claiming the galaxy is a pure spiral with no bar.
Diagrams are often schematic, and the Sun's 8 kpc distance from the centre, the 26,000 ly scale, and the bar are details that get flattened into a generic spiral picture.
What to do instead
Fix the numbers: Sun about 8 kpc from the centre, galactic radius about 15 kpc, disk thickness about 1 kpc, orbital speed about 220 km/s, orbital period about 230 Myr; describe the Milky Way as a barred spiral (SBbc) and locate the Sun in the Orion arm.
Treating redshift as always a Doppler velocity and using v = cz for large z, or conflating cosmological redshift with gravitational redshift.
The Doppler formula is the first one taught and works for nearby galaxies, so it gets applied to z > 1 where recession velocities exceed c and the linear approximation fails.
What to do instead
Use v = cz only for z ≪ 1; for larger z use the relativistic Doppler or, better, the cosmological relation with a chosen model; check whether the question concerns expansion of space (cosmological) or motion through space (peculiar/Doppler) before answering.
Mistaking a distance indicator for a distance itself, e.g. quoting parallax in parsecs but then using it as a luminosity, or using Cepheid period–luminosity without correcting for extinction.
The rungs of the distance ladder are taught as a list, and the calibration step (parallax → Cepheid → Type Ia supernova → Hubble law) gets collapsed into one number.
What to do instead
State which rung a question is on and what it calibrates: parallax (geometric, to about 1 kpc), Cepheids (period–luminosity, needs extinction correction), Type Ia supernovae (standardisable candles), and Hubble's law for the farthest scales; write the chain explicitly before answering.