ABPM Aerospace Medicine common mistakes
ABPM Aerospace Medicine · Understand the traps and how to avoid them.
Writing the aeromedical disposition as a clinical note - "currently asymptomatic, stable on treatment, recommend certify" - without naming the specific regulatory category, the applicable waiver/exception pathway, the required observation interval, and the objective evidence used to judge stability.
Candidates carry over the clinical habit of describing the patient's condition and current status, and treat the regulatory decision as an afterthought. Clinical improvement feels like sufficient justification, so the decision logic is never made explicit.
What to do instead
For every case, draft a four-part disposition sentence before writing anything else: (1) diagnosis and its regulatory class (acute, chronic stable, progressive, disqualifying); (2) the specific standard or guidance text being applied; (3) the waiver/exception route and who grants it; (4) the surveillance plan (interval, tests, restriction). If any part cannot be filled in, mark it as the gap to study rather than guessing.
Clearing a crewmember for duty without systematically reviewing medications and self-treatment - including over-the-counter antihistamines, decongestants, caffeine/energy products, supplements, and grounding intervals after sedating or vestibular-active drugs.
The medication list is treated as background history rather than as a fitness-for-duty variable. Candidates also assume 'prescribed by a physician' equals 'compatible with flying,' and forget that the aeromedical concern is performance effects plus the underlying condition being treated.
What to do instead
Use a standing checklist for any drug question: drug class, desired effect, performance-impairing side effects (sedation, vestibular suppression, visual/accommodation effects), interaction with altitude and hypoxia, acceptable grounding interval, and whether an equivalent non-sedating agent exists. Always state the interval as a number of hours or doses, and note that the underlying condition must also be acceptable independently.
Computing alveolar or arterial oxygenation at altitude with the ambient barometric pressure and dry gas fractions, i.e. using F IO2 × P B directly, or forgetting to subtract water vapour pressure and to apply the respiratory exchange ratio in the alveolar gas equation.
Sea-level intuition makes F IO2 × P B look correct, and the water-vapour correction is a small detail that is easy to drop under time pressure. Candidates also confuse barometric pressure at altitude with cabin altitude in a pressurised aircraft.
What to do instead
Always write the full chain before substituting numbers: inspired P O2 = F IO2 × (P B − 47); alveolar P O2 = inspired P O2 − (P A CO2 / R), with R ≈ 0.8. State explicitly whether you are using ambient or cabin altitude, and sanity-check the answer against a known anchor (e.g. roughly 21 kPa inspired at sea level, about two-thirds of that at 2,400 m cabin altitude).
Explaining G tolerance and G-protection as a single 'the G-suit prevents blood pooling' statement, without separating +Gz from −Gz haemodynamics, the role of the anti-G straining manoeuvre versus the suit, the A-LOC/G-LOC sequence, and the relaxation/recovery phase after the strain is released.
Acceleration physiology is learned as a set of labels rather than a causal sequence, so the answer names the countermeasure but cannot explain when it works, why the suit alone is insufficient, or why the hazard persists in the seconds after the manoeuvre ends.
What to do instead
Rehearse acceleration as a timeline: blood shift and baroreceptor response → cerebral perfusion threshold → visual symptoms (greyout, tunnel vision) → loss of consciousness → myoclonic phase and recovery. Attach each protective measure to the point in the timeline it acts on (straining raises intrathoracic pressure and mean arterial pressure; the suit extends tolerance mainly in the legs; the hook manoeuvre maintains pressure during the transition). Practise drawing this timeline from memory.
Treating noise exposure as a hearing-loss question only, and misapplying the dose arithmetic - using a 5 dB exchange rate for a hearing-conservation assessment, or comparing a measured level directly to a limit without converting short exposures into an equivalent 8-hour time-weighted average.
The audiogram is the memorable outcome, so non-auditory effects and the maths are skipped. The 3 dB versus 5 dB exchange rates coexist in different regulatory contexts and are easily swapped when the standard is not named in the answer.
What to do instead
State the standard and its exchange rate before calculating, then convert every exposure to an 8-hour equivalent and sum with the logarithmic rule. Separately list the non-auditory consequences (communication interference, warning-signal masking, fatigue, cardiovascular associations) as an independent justification for control, not as a footnote to hearing loss.
Mixing radiation dose quantities and effect categories - using gray and sievert interchangeably, comparing an absorbed dose directly with a dose limit, or applying stochastic risk reasoning to a deterministic effect threshold (or vice versa).
The units look like different names for one quantity, and the deterministic/stochastic split is remembered as vocabulary rather than as two different decision rules, so the wrong limit gets quoted.
What to do instead
Anchor four lines: absorbed dose (Gy) describes energy deposition in tissue; equivalent/effective dose (Sv) is risk-weighted for stochastic planning and limits; deterministic effects have thresholds and severity increases with dose; stochastic effects are probabilistic with no threshold. Whenever a number is quoted, name the quantity, the tissue, the population (occupational versus public) and the issuing body.
Writing 'human error' or 'pilot failed to monitor' as a root cause in an accident or incident analysis, without classifying the error type (slip, lapse, mistake, violation) or identifying the systemic preconditions that made the error likely and undetected.
The error is the most visible element of the narrative, and retrospective analysis invites hindsight and blame. Candidates also lack a default taxonomy, so the analysis stops at the individual.
What to do instead
Impose a fixed template: describe the intended action, the actual action, the point of divergence; classify the divergence; then identify the local traps (interface design, workload, ambiguous procedure, ambiguous alerting) and the organisational factors (training, staffing, supervision) that shaped it. Finish with the barrier that failed to catch the error - that sentence is usually where the marks are.
Addressing fatigue with qualitative advice ('ensure adequate rest', 'crew should self-assess') instead of quantifying the exposure: duty and rest periods, sleep opportunity per 24 hours, circadian phase of the duty period, cumulative duty across the pattern, and which validated tool or rule set applies.
Fatigue is taught as a hazard awareness topic rather than as an arithmetic problem, and self-assessment feels like an acceptable control despite being a poor detector of one's own impairment.
What to do instead
For any fatigue scenario, tabulate the timeline hour by hour (report, duty start/end, sleep opportunity, circadian low point, number of sectors or tasks), then state the number of hours of sleep opportunity actually available and whether the duty crosses the window of circadian low. Conclude with a control matched to the mechanism (schedule change, controlled napping, caffeine timing, flight-time limit), not a general exhortation.
Carrying terrestrial reference ranges and clinical decision thresholds unchanged into microgravity and remote settings - for example interpreting fluid shifts, cardiovascular deconditioning, bone mineral loss or a swollen limb using ground-based norms - and assuming telemedicine support is available in real time.
Ground-based clinical training supplies familiar thresholds, and the space environment is treated as a setting rather than as a confounder that shifts physiology and reshapes the resources available for care.
What to do instead
For each clinical problem, ask three questions explicitly: what does the environment change about the physiology and the expected findings; what does it change about the available diagnostics and treatments; and what does the communication/evacuation delay forbid. Answer with a spaceflight-specific standard or an autonomy requirement (onboard capability, crew medical officer training, just-in-time guidance) rather than a terrestrial number.
Quoting a regulatory number or requirement without attributing it to a jurisdiction, issuing body and version - for example a flight-time limit, medical validity period, or alcohol/medication interval stated as if it were universal - or blending military, civil and space-agency frameworks in one answer.
Standards across ICAO, national civil authorities, military services and space agencies overlap in structure but differ in detail, and candidates memorise the number while dropping the citation. Under exam pressure the most recently studied figure is used for every question.
What to do instead
Every regulatory claim gets a prefix: authority + document + edition, then the requirement, then the applicability (class of medical, type of operation, age band). When unsure of the exact figure, state the framework and the principle and flag the number as needing verification - a correctly attributed principle scores better than an unattributed guess.