Ultra-light Aeroplane (ULTRA) common mistakes
Ultra-light Aeroplane (ULTRA) · Understand the traps and how to avoid them.
Treating the ultra-light category limits as a single number and applying one maximum take-off weight to every situation, instead of separating empty weight, maximum all-up weight, wing loading and stall speed into distinct limits and checking each one.
Candidates memorise one headline figure from a summary table and never build a mental model of how the individual limits interact, so they substitute the remembered number for whichever limit the question actually asks about.
What to do instead
Build a one-page limit sheet listing each parameter separately (empty weight, maximum all-up weight, wing loading, stall speed, fuel capacity, seating) with the unit and the regulation source beside it. Before answering, underline the parameter in the question and read the value from that line only. Rehearse by writing the sheet from memory weekly until it is exact.
Answering airspace and clearance questions from general flying experience rather than from the specific class, control-zone and radio requirements that apply to ultra-light operations, for example assuming an ultra-light may enter controlled airspace whenever the pilot holds a radio licence.
Ultra-lights are often flown from farm strips and uncontrolled fields, so pilots rarely encounter controlled airspace in training and fill the gap with assumptions carried over from general aviation reading or from what other pilots say at the club.
What to do instead
Work through the airspace classification table line by line and, for each class, write the ultra-light-specific entry conditions: clearance, radio, transponder, visibility and cloud distance. Then answer practice questions by naming the airspace class first and the entry condition second before looking at the options.
Confusing the documents that must be carried on board with those that must be held but kept elsewhere, and mixing aircraft documents with pilot documents, so the answer lists the certificate of registration as a pilot-held item or omits the permit to fly.
The lists look similar and are usually studied as one block of text, so items migrate between categories in memory; candidates also study from checklists that group everything under 'documents' without separating who holds what.
What to do instead
Draw a three-column table: carried on the aircraft, held by the pilot, held by the owner or operator. Place each document once and only once, and annotate any validity or renewal period in the margin. Test yourself by covering a column and reconstructing it, not by rereading the full list.
Reading a terminal aerodrome forecast as if it were a current observation, and therefore treating a forecast temporary or becoming group as the actual weather at the time of flight.
The coded formats share the same abbreviations and the candidate learns the decode table without learning the difference in meaning between a METAR, a TAF, a TREND and a SIGMET, so the decode is correct but the interpretation is wrong.
What to do instead
For every coded report, first state aloud what kind of product it is, its validity period and its issue time, then decode the body. Practise with paired examples of the same aerodrome at the same hour so the contrast between observed and forecast conditions is concrete.
Judging wind strength at the surface by the forecast upper-level wind, and planning crosswind take-offs and landings from the forecast surface wind without checking the actual reported surface wind and its gusts at the departure or destination field.
Ultra-lights are light and slow, so surface wind and gust spread matter far more than for heavier types, but candidates apply the same rough planning habit they use for general weather appreciation and never convert forecast wind to a crosswind component for the specific runway.
What to do instead
For each planned flight, compute the crosswind component for the intended runway from the reported surface wind and compare it with the aircraft's demonstrated limit, including the gust factor. Do this on paper during study so the arithmetic and the decision threshold become automatic.
Ignoring density altitude and treating a high-elevation or hot-day departure as equivalent to a sea-level standard day, then being surprised by the longer ground roll and reduced climb.
Density altitude is an abstract number until it is tied to aircraft performance, and many candidates learn the definition without ever applying it to a take-off distance or rate-of-climb figure for a light aircraft.
What to do instead
Work numerical examples: given field elevation, temperature and pressure, compute density altitude and then read the take-off distance and climb rate from a representative performance table. Repeat across a grid of temperatures and elevations so the sensitivity of a light, high-drag airframe becomes intuitive.
Computing a navigation leg with a single mental track-and-distance estimate and no written drift or heading calculation, so the answer reflects the planned track rather than the heading actually to be flown.
Ultra-light navigation is often low-level map reading with short legs, which encourages rough estimation; the candidate then answers a question about heading, ground speed or time en route using the track value because the two were never separated in practice.
What to do instead
Adopt a fixed written format for every leg: true track, wind velocity, drift angle, true heading, variation, magnetic heading, then ground speed and time. Fill every box even when the answer seems obvious, and check the result by asking whether the wind should push the heading left or right of track.
Mixing magnetic and true directions, or applying variation with the wrong sign, when converting between chart track and compass heading.
The two systems are learned together and the sign rule is memorised as a phrase rather than understood as a physical relationship, so it collapses under exam pressure, especially when the question supplies deviation as well as variation.
What to do instead
Draw a small compass rose for each question with true north and magnetic north marked and the variation arrow drawn in the correct direction. Convert step by step on paper, and sanity-check by asking whether magnetic north lies east or west of true north at that location.
Explaining a stall or a spin in terms of airspeed alone, and so concluding that a stall cannot occur at high speed or in a steep turn, or that adding power prevents a stall.
Introductory teaching often anchors stall to a single published speed, and the candidate never internalises that the stall depends on the angle of attack exceeding the critical value regardless of speed, attitude or power setting.
What to do instead
Restate the mechanism in terms of angle of attack and load factor, then work through the cases explicitly: level stall, stall in a steep turn, accelerated stall at high speed, and the effect of a gust. For each, state what happens to the angle of attack and why the airspeed at which it occurs changes.
Treating the effect of controls and of thrust as independent of airspeed, for example assuming full back pressure always produces the same pitch response, or that a slow ultra-light responds to control input the same way at low and high speed.
Control effectiveness scales with airflow over the surface, and the candidate learns control functions as a static list rather than as responses that vary with airspeed, slipstream and angle of attack.
What to do instead
For each control, write a short note on how its effectiveness changes with airspeed and with propeller slipstream, then link it to a specific handling situation such as a slow approach, a crosswind landing or a recovery from a low-speed upset.
Answering human-factors questions by naming a general concept such as fatigue or complacency without identifying the specific mechanism, the cues that reveal it and the countermeasure that removes it.
Human factors is studied as vocabulary rather than as a set of recognisable scenarios, so the candidate recognises the topic of the question but cannot discriminate between options that are all plausible-sounding descriptions of the same phenomenon.
What to do instead
Build a table with one row per factor: the mechanism, the in-flight cues, the typical accident sequence, and one concrete countermeasure that can be applied before flight. Answer questions by matching the scenario to the cues column first, then choosing the option that names the countermeasure.
Applying decision-making models only after an emergency has developed, rather than using a pre-flight go/no-go assessment with explicit personal minima for wind, visibility and crosswind.
Training emphasises in-flight emergency drills because they are easy to examine, while the pre-flight decision that prevents the emergency is treated as common sense and never practised as a procedure.
What to do instead
Write personal minima for crosswind, gust spread, visibility and cloudbase, and rehearse a short pre-flight decision script: state the conditions, compare them with the minima, state the decision and the reason. Use the same script in study scenarios so the habit transfers to the aircraft.