Engineer Aircraft common mistakes
Engineer Aircraft · Understand the traps and how to avoid them.
When a question describes a hydraulic system schematic in words and asks what happens to actuator speed or system pressure after a pump or relief valve change, the candidate answers from a memorized rule ('relief valve sets pressure, so nothing changes') instead of tracing flow and pressure through the described circuit.
Hydraulic questions reward a mental model of flow, pressure drop, and load. Candidates who learned components in isolation default to single-fact recall and skip the step where they identify what the load or restriction actually does to the quantity asked about.
What to do instead
Before answering any hydraulic scenario, write down the path: pump, relief valve, selector, actuator, return. Then state which quantity the question asks about and whether it depends on flow (speed) or pressure (force/relief setting). Practice with three or four self-made scenarios where one component is changed and predict the effect before checking your reasoning.
Confusing the roles of the pressure relief valve, pressure regulator, and system accumulator, and therefore choosing the wrong component as the cause when a question describes creeping actuators, slow pressure buildup, or pressure spikes.
These components are taught together and share the word 'pressure', so candidates store them as a blur. Exam questions deliberately describe symptoms that distinguish them, and the candidate cannot map symptom to component.
What to do instead
Build a one-page comparison table with columns: component, what it controls, typical symptom when faulty, and where it sits in the circuit. Test yourself by covering the symptom column and generating symptoms from each component, then reversing the exercise.
On airworthiness and documentation questions, the candidate selects the answer that describes what is technically good practice rather than what the regulation or approved document actually requires, for example treating a service bulletin as mandatory or assuming any repair needs a major repair form.
Candidates with hands-on maintenance experience answer from hangar habit. Regulations distinguish mandatory documents (airworthiness directives) from advisory ones (service bulletins, service letters), and the exam tests that distinction precisely.
What to do instead
Make a document hierarchy card: type certificate, airworthiness directive, service bulletin, maintenance manual, approved repair scheme, release document. For each, note who issues it, whether it is mandatory, and what record it generates. Answer documentation questions by first naming the document class the question describes.
When a question describes a corrosion finding, the candidate names the corrosion type from the metal color alone, without using the location, environment, and appearance pattern described in the stem, and so confuses exfoliation with intergranular attack or filiform with crevice corrosion.
Corrosion types are memorized as a list of names with one visual cue each. Real distinguishing features are structural (grain boundary attack, layered lifting, trapped moisture sites), and the stem usually supplies those clues but the candidate does not read for them.
What to do instead
For each common corrosion type, memorize a three-part signature: where it occurs, what it looks like in cross-section, and what drives it (moisture trapping, dissimilar metals, stress, heat). When answering, underline the location and appearance words in the stem and match the signature before choosing.
In non-destructive testing questions, the candidate picks the most sensitive method (such as penetrant or eddy current) when the question specifies the material, defect location, or geometry, ignoring that penetrant only works on surface-breaking defects in non-porous materials and that magnetic particle testing requires ferromagnetic material.
Candidates rank NDT methods by reputation for sensitivity rather than by applicability constraints. The exam tests method selection under constraints, not a sensitivity league table.
What to do instead
Create a selection matrix: method versus material, defect location (surface or subsurface), defect type, and surface condition. Practice by writing the constraint words from a stem first, then eliminating methods that fail any constraint before comparing the survivors.
On electrical and avionics questions, the candidate treats a described fault as a single-component failure and ignores the return path, bonding, shielding, or bus architecture, so a symptom like intermittent radio noise or a gauge reading high is attributed to the sensor rather than to a ground or bonding defect.
Training focuses on components and wiring diagrams; the shared ground, bonding straps, and shield terminations are visually minor on a schematic but are frequent real causes of described symptoms. Candidates underweight what they rarely had to troubleshoot.
What to do instead
For every electrical fault scenario, run a fixed checklist: power source, protection, control, load, return path, bonding and shielding. State the return path explicitly before choosing an answer. Review how bonding and shielding affect noise and stray currents.
On flight control and landing gear questions, the candidate answers about the normal system when the stem describes an alternate or emergency mode, or assumes a described indication means the same thing in both modes, for example treating alternate extension as equivalent to normal hydraulic extension.
Normal operation is studied and practiced most, so it anchors recall. Alternate and emergency systems are learned as a list of steps rather than as a distinct configuration with its own logic, limits, and indications.
What to do instead
For each major system, write a two-column comparison: normal mode versus alternate or emergency mode, covering power source, what is lost, indications, and limitations. Answer by first classifying which mode the stem describes, then reasoning only within that mode.
On human factors questions, the candidate chooses the answer that blames an individual's attitude or carelessness instead of identifying the systemic contributor (task design, supervision, fatigue, communication, procedure quality) that the scenario is built to illustrate.
Everyday explanations of error are person-centered. Human factors frameworks (such as the error chain, Swiss cheese model, and performance-shaping factors) require the candidate to look past the individual, and candidates default to the intuitive attribution.
What to do instead
Practice rewriting incident descriptions twice: once blaming the person, once describing the conditions that made the error likely. Learn the standard categories (fatigue, pressure, distraction, norms, communication, documentation, design) and, for each scenario, name the category before choosing an answer.
On structures questions, the candidate confuses stress, strain, and load, or applies a bending or fatigue concept to the wrong part of the structure, for example treating a fatigue crack question as a static strength question and choosing the answer about ultimate load.
Structural terminology is learned as definitions without being tied to failure scenarios. Fatigue, static overload, and buckling produce different evidence in the stem, and candidates who only know definitions cannot use that evidence.
What to do instead
For each failure mode (static overload, fatigue, buckling, stress corrosion), write the loading condition, the typical origin and appearance of failure, and the inspection implication. When answering, identify the loading regime from the stem first, then select the failure mode that matches it.
On propulsion questions, the candidate answers about the engine core when the stem concerns a system that interacts with it, such as fuel metering, ignition, starting, or bleed air, and misattributes a starting or acceleration fault to a mechanical component rather than to the controlling system.
Engine questions are mentally filed under 'engine mechanical', so system-level causes (fuel control scheduling, ignition energy, bleed valve position) get overlooked even when the stem describes a symptom that is characteristic of them.
What to do instead
For each engine system, list its function, its interface with the core, and two characteristic fault symptoms. Practice classifying symptoms by system (fuel, ignition, air, control) before choosing, and review how starting and acceleration schedules depend on fuel and bleed air.